Service interruption via leaked I2C probe client
Published Feb 26, 2025 · Updated May 11, 2026
Memory leak in the Linux kernel's go7007 Sensoray 2250/2251 driver allows local users to interrupt service through failed probes. The s2250_probe error path returns after control-handler setup fails without unregistering the previously created audio I2C client, leaving its allocation alive. Reachability requires the affected driver and hardware plus local access capable of retriggering the failing probe; accumulated leaks can exhaust kernel memory.
Summary
What happened
Memory leak in the Linux kernel's go7007 Sensoray 2250/2251 driver allows local users to interrupt service through failed probes. The s2250_probe error path returns after control-handler setup fails without unregistering the previously created audio I2C client, leaving its allocation alive. Reachability requires the affected driver and hardware plus local access capable of retriggering the failing probe; accumulated leaks can exhaust kernel memory.
The record
- CVE
- CVE-2022-49253
- 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.10
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <14cd5a8e61c654828a1f1056d56f0b0a524d2c69
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <44973633b0064c46083833b55dd0a45e6235f8ca
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <67e4550ecd6164bfbdff54c169e5bbf9ccfaf14d
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <895364fa97e60749855f789bc4568883fc7a8b39
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <948ad5e5624487079c24cb5c81c74ddd02832440
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <a97130cd5b0c00eec169b10a16d922b9ea67324a
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <b5470f3efa530b10296257bb578ce4b1769e9a04
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <b7dd177225355da55f8d80d8e568928e0eec3608
- Affected versionversion=d3b2ccd9e307eae80b4b4eeb0ede46cb02212df2 <bbdd0e15738336e6b1208304ae98525117877bbd
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