Invalid memory access via stale BPF program arrays
Published Nov 19, 2026 · Updated Nov 19, 2026
Use-after-free in Linux LIRC BPF handling allows local users to access stale kernel memory through operations on an unregistered device. In drivers/media/rc/bpf-lirc.c, attach, detach, and query operations access raw->progs after unregister without checking device registration, while teardown leaves the freed array pointer uncleared. Reachability requires access to the relevant LIRC BPF operations and device teardown; published evidence does not establish the required privileges or a crash, disclosure, or code-execution outcome.
Summary
What happened
Use-after-free in Linux LIRC BPF handling allows local users to access stale kernel memory through operations on an unregistered device. In drivers/media/rc/bpf-lirc.c, attach, detach, and query operations access raw->progs after unregister without checking device registration, while teardown leaves the freed array pointer uncleared. Reachability requires access to the relevant LIRC BPF operations and device teardown; published evidence does not establish the required privileges or a crash, disclosure, or code-execution outcome.
The record
- CVE
- CVE-2026-99435
- Published
- Nov 19, 2026
- Updated
- Nov 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 19, 2026CVE publishedPublication date reported by the CVE source.
- Nov 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.12.93 <6.12.117
- Affected versionversion=6.18.35 <6.18.61
- Affected versionversion=6.6.143 <6.7
- Affected versionversion=7.1
- Affected versionversion=75977f5f5c4974c72bbedefbf09ad33ebbaa36f1 <52efde6424420e0cf33df2ba23a8495cc141581f
- Affected versionversion=a7becb58f6b8a3a3efe5d3acfd52e2c107de6772
- Affected versionversion=dccc0c3ddf8f16071736f98a7d6dd46a2d43e037 <341e2ba83d23b169808b8ccf29d41aee899148fd
- Affected versionversion=dccc0c3ddf8f16071736f98a7d6dd46a2d43e037 <f95a9f8472f97c30106513fc7494b7abad243949
- Affected versionversion=e250b672d40a9e0d97a8895cbb301248bea0fce6 <4528f92222e7b90b2ea634338657888f63887d7a
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us