Service interruption via leaked V4L2 control handler
Published May 6, 2026 · Updated May 6, 2026
Memory leak in the Linux Kernel radio-keene driver allows local users to consume kernel memory by triggering device-probe failures. In usb_keene_probe(), the err_v4l2 path returns after v4l2_device_register() or video_register_device() fails without freeing the initialized V4L2 control handler. Exploitation requires local access and repeated probe failures for the Keene FM radio USB device, eventually causing a service interrupt through memory exhaustion.
Summary
What happened
Memory leak in the Linux Kernel radio-keene driver allows local users to consume kernel memory by triggering device-probe failures. In usb_keene_probe(), the err_v4l2 path returns after v4l2_device_register() or video_register_device() fails without freeing the initialized V4L2 control handler. Exploitation requires local access and repeated probe failures for the Keene FM radio USB device, eventually causing a service interrupt through memory exhaustion.
The record
- CVE
- CVE-2026-43231
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499
- 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=1bf20c3a0c616f44359c573b533d06bae960ee45 <1d8558a232ecb187e8e0328d6347a125f437a0fc
- Affected versionversion=1bf20c3a0c616f44359c573b533d06bae960ee45 <242b0aabb1866024a7995a767ac330c158b39aa4
- Affected versionversion=1bf20c3a0c616f44359c573b533d06bae960ee45 <27c508f61963013fdf29097578284099ee7a85a4
- Affected versionversion=1bf20c3a0c616f44359c573b533d06bae960ee45 <2fe28a63d598235595a9601e0d8fdc7c8f4fd575
- Affected versionversion=1bf20c3a0c616f44359c573b533d06bae960ee45 <7fa9754f48cb8eefa566156be341e63d313247e5
- Affected versionversion=1bf20c3a0c616f44359c573b533d06bae960ee45 <ad85bb5623079a35bd400f51de2e2fbc2170bdb2
- Affected versionversion=1bf20c3a0c616f44359c573b533d06bae960ee45 <b8bf939d77c0cd01118e953bbf554e0fa15e9006
- Affected versionversion=1bf20c3a0c616f44359c573b533d06bae960ee45 <de204d87e7d61859937272fe30cbdd46a4cfb10a
- Affected versionversion=3.4
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