Kernel memory corruption via unsynchronized trigger removal
Published Feb 26, 2025 · Updated May 11, 2026
Use-after-free in Linux kernel IIO sysfs triggers allows local users to corrupt kernel memory during trigger removal. The iio_sysfs_trigger_remove function frees the trigger without first synchronizing queued irq_work, allowing irq_work_run_list to access the released object. Exploitation requires low-privilege local sysfs access and can crash the kernel or compromise kernel confidentiality and integrity.
Summary
What happened
Use-after-free in Linux kernel IIO sysfs triggers allows local users to corrupt kernel memory during trigger removal. The iio_sysfs_trigger_remove function frees the trigger without first synchronizing queued irq_work, allowing irq_work_run_list to access the released object. Exploitation requires low-privilege local sysfs access and can crash the kernel or compromise kernel confidentiality and integrity.
The record
- CVE
- CVE-2022-49685
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- 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.7
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <31ff3309b47d98313c61b8301bf595820cc3cc33
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <4687c3f955240ca2a576bdc3f742d4d915b6272d
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <4ef1e521be610b720daeb7cf899fedc7db0274c4
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <5e39397d60dacc7f5d81d442c1c958eaaaf31128
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <78601726d4a59a291acc5a52da1d3a0a6831e4e8
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <b07a30a774b3c3e584a68dc91779c68ea2da4813
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <d6111e7bdb8ec27eb43d01c4cd4ff1620a75f7f2
- Affected versionversion=f38bc926d022ebd67baad6ac7fc22c95fbc6238c <fd5d8fb298a2866c337da635c79d63c3afabcaf7
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