CVE-2026-43231
What it is
In the Linux kernel, the following vulnerability has been resolved: media: radio-keene: fix memory leak in error path Fix a memory leak in usb_keene_probe(). The v4l2 control handler is initialized and controls are added, but if v4l2_device_register() or video_register_device() fails afterward, the handler was never freed, leaking memory. Add v4l2_ctrl_handler_free() call in the err_v4l2 error path to ensure the control handler is properly freed for all error paths after it is initialized.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-401
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.252
- Linux Kernel < 5.15.202
- Linux Kernel < 6.1.165
- Linux Kernel < 6.6.128
- Linux Kernel < 6.12.75
- Linux Kernel < 6.18.16
- Linux Kernel < 6.19.6
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43231.md and follow it. Check whether this project is affected by CVE-2026-43231. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1d8558a232ecb187e8e0328d6347a125f437a0fc
- https://git.kernel.org/stable/c/242b0aabb1866024a7995a767ac330c158b39aa4
- https://git.kernel.org/stable/c/27c508f61963013fdf29097578284099ee7a85a4
- https://git.kernel.org/stable/c/2fe28a63d598235595a9601e0d8fdc7c8f4fd575
- https://git.kernel.org/stable/c/7fa9754f48cb8eefa566156be341e63d313247e5
- https://git.kernel.org/stable/c/ad85bb5623079a35bd400f51de2e2fbc2170bdb2
- https://git.kernel.org/stable/c/b8bf939d77c0cd01118e953bbf554e0fa15e9006
- https://git.kernel.org/stable/c/de204d87e7d61859937272fe30cbdd46a4cfb10a
References
- https://git.kernel.org/stable/c/1d8558a232ecb187e8e0328d6347a125f437a0fc
- https://git.kernel.org/stable/c/242b0aabb1866024a7995a767ac330c158b39aa4
- https://git.kernel.org/stable/c/27c508f61963013fdf29097578284099ee7a85a4
- https://git.kernel.org/stable/c/2fe28a63d598235595a9601e0d8fdc7c8f4fd575
- https://git.kernel.org/stable/c/7fa9754f48cb8eefa566156be341e63d313247e5
- https://git.kernel.org/stable/c/ad85bb5623079a35bd400f51de2e2fbc2170bdb2
- https://git.kernel.org/stable/c/b8bf939d77c0cd01118e953bbf554e0fa15e9006
- https://git.kernel.org/stable/c/de204d87e7d61859937272fe30cbdd46a4cfb10a