Service interruption via unreleased probe allocations
Published May 6, 2026 · Updated May 6, 2026
Memory leakage in the tw9906 media driver in affected Linux Kernel releases allows local users to exhaust memory via failed device probes. In tw9906_probe(), an error path after v4l2_ctrl_handler_init() and v4l2_ctrl_new_std() returns without calling v4l2_ctrl_handler_free(), leaving control-handler allocations live. Exploitation requires local low-privilege access and repeated reachability of the driver probe failure path; sustained triggering can interrupt service through kernel-memory exhaustion.
Summary
What happened
Memory leakage in the tw9906 media driver in affected Linux Kernel releases allows local users to exhaust memory via failed device probes. In tw9906_probe(), an error path after v4l2_ctrl_handler_init() and v4l2_ctrl_new_std() returns without calling v4l2_ctrl_handler_free(), leaving control-handler allocations live. Exploitation requires local low-privilege access and repeated reachability of the driver probe failure path; sustained triggering can interrupt service through kernel-memory exhaustion.
The record
- CVE
- CVE-2026-43246
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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=3.10
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <0c33338514d8246280533a77091e6b6ee548c606
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <377a7756914364d72550fc86ca0f404ef1d96141
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <59420d5d9c46b084e21f9ea6ce79fc79ae9e414c
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <9548a8bbf511a252a9848f96220c6b95c9a3b918
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <cad237b6c875fbee5d353a2b289e98d240d17ec8
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <ccb92def042a3636ed47f25a30bd553788e5191e
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <e9a490937942f18205dac7b6b192975ef1369ae1
- Affected versionversion=a000e9a02b5885b1b69f691c80e346d102f94a88 <fb09d8b80046216646f1a344410cfa9cfa6c6c7c
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo