Local denial of service via unreleased USB anchor
Published Apr 24, 2026 · Updated Apr 24, 2026
Memory leak in the rt2x00usb driver in the Linux kernel allows local users to reduce availability during repeated driver unbinds. The rt2x00usb_probe function allocates its USB anchor against the parent USB device instead of the bound USB interface, so interface-managed cleanup does not release it on unbind. Exposure requires an rt2x00 USB device and an unbind without physical disconnection, such as during probe deferral or configuration changes; each occurrence leaves kernel memory unavailable.
Summary
What happened
Memory leak in the rt2x00usb driver in the Linux kernel allows local users to reduce availability during repeated driver unbinds. The rt2x00usb_probe function allocates its USB anchor against the parent USB device instead of the bound USB interface, so interface-managed cleanup does not release it on unbind. Exposure requires an rt2x00 USB device and an unbind without physical disconnection, such as during probe deferral or configuration changes; each occurrence leaves kernel memory unavailable.
The record
- CVE
- CVE-2026-31672
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 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=4.7
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <15b233e33b35b927bd8d0044c15325564ea1ba24
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <1de5c76bf40e9cdeebf54662f63011fb10fa452f
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <25369b22223d1c56e42a0cd4ac9137349d5a898e
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <64a457f6afbf15f984d95201a9a1e71eed3f9dd1
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <65518a6965d527c53013947031f26754f6a4f6af
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <b245db719bc7e57abf48bd5701662b270c3880f7
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <c99f198841b41735796e2ddfcd573783fb552eb9
- Affected versionversion=8b4c0009313f3d42e2540e3e1f776097dd0db73d <e360d15fcb1e819eef49e3d4434d8050542eed16
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