Service interruption via leaked usbnet control buffers
Published Feb 26, 2025 · Updated May 11, 2026
Memory leak in affected Linux kernel branches allows local users to interrupt service through failed asynchronous USB control requests. The usbnet_write_cmd_async() error cleanup confuses ownership of the control request and transfer buffer, leaving allocated memory unreleased when setup or submission fails. Low-privilege local access and a reachable USB-network driver path are required; repeated failures can exhaust kernel memory and disrupt availability.
Summary
What happened
Memory leak in affected Linux kernel branches allows local users to interrupt service through failed asynchronous USB control requests. The usbnet_write_cmd_async() error cleanup confuses ownership of the control request and transfer buffer, leaving allocated memory unreleased when setup or submission fails. Low-privilege local access and a reachable USB-network driver path are required; repeated failures can exhaust kernel memory and disrupt availability.
The record
- CVE
- CVE-2022-49657
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.8
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <0085da9df3dced730027923a6b48f58e9016af91
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <04894ab34faf40ab72a8a5ab5b404bb0606bbbff
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <3eed421ca5c809da93456f69203d164d5220be3d
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <5269209f54dd8dfd15f9383f3a3a1fe8370764f8
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <b55a21b764c1e182014630fa5486d717484ac58f
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <d5165e657987ff4ba0ace896d4376a3718a9fbc3
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <db89582ff330556188da856e01382ccbf3a5e706
- Affected versionversion=877bd862f32b815d54ab5fc10a4fd903d7bf3012 <e7b4f69946a38209b4a4f660bf0e4cbed94f9b4b
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