DMA-memory exhaustion via unreleased RX URBs
Published Feb 26, 2025 · Updated May 11, 2026
Memory leak in the Linux kernel gs_usb CAN driver allows local users to exhaust DMA memory by repeatedly opening and closing an interface. gs_can_open allocates RX URBs and coherent DMA buffers, but gs_can_close only kills the anchored URBs instead of releasing them with usb_free_coherent. The path requires a compatible USB CAN adapter and permission to cycle its interface; continued repetition depletes DMA memory without reading or changing data.
Summary
What happened
Memory leak in the Linux kernel gs_usb CAN driver allows local users to exhaust DMA memory by repeatedly opening and closing an interface. gs_can_open allocates RX URBs and coherent DMA buffers, but gs_can_close only kills the anchored URBs instead of releasing them with usb_free_coherent. The path requires a compatible USB CAN adapter and permission to cycle its interface; continued repetition depletes DMA memory without reading or changing data.
The record
- CVE
- CVE-2022-49661
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.001
- 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.16
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <0e60230bc64355c80abe993d1719fdb318094e20
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <2bda24ef95c0311ab93bda00db40486acf30bd0a
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <339fa9f80d3b94177a7a459c6d115d3b56007d5a
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <6f655b5e13fa4b27e915b6c209ac0da74fd75963
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <c1d806bc29ff7ffe0e2a023583c8720ed96cb0b0
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <d0b8e223998866b3e7b2895927d4e9689b0a80d8
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <d91492638b054f4a359621ef216242be5973ed6b
- Affected versionversion=d08e973a77d128b25e01a08c34d89593fdf222da <ffb6cc6601ec7c8fa963dcf76025df4a02f2cf5c
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