Local kernel memory corruption via skipped RCU synchronization
Published May 1, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel ftrace allows local users with tracing access to crash the kernel or corrupt kernel memory. ftrace_shutdown() can leave its command value at zero when a second matching dynamic ftrace_ops is unregistered, skipping RCU synchronization before freeing the operation. Local access to perf function tracing or writable tracefs is required; a concurrent ftrace callback can then read freed memory, causing a kernel panic or enabling kernel-memory corruption.
Summary
What happened
Use-after-free in Linux kernel ftrace allows local users with tracing access to crash the kernel or corrupt kernel memory. ftrace_shutdown() can leave its command value at zero when a second matching dynamic ftrace_ops is unregistered, skipping RCU synchronization before freeing the operation. Local access to perf function tracing or writable tracefs is required; a concurrent ftrace callback can then read freed memory, causing a kernel panic or enabling kernel-memory corruption.
The record
- CVE
- CVE-2022-49892
- Published
- May 1, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=100553e197e2c41eccf9fa04b2be9cd11ae21215
- Affected versionversion=30d3c1c9c9dd31b3c3a5aa0f4f40f1e321c6c791
- Affected versionversion=4.13.4 <4.14
- Affected versionversion=4.14
- Affected versionversion=4.1.45 <4.2
- Affected versionversion=4.4.89 <4.5
- Affected versionversion=4.9.52 <4.10
- Affected versionversion=a60e407b961e818541ff7924afa8e51fbdb21a61
- Affected versionversion=ed1bf4397d2219d4b9ec2d5517416ba102186650
- Affected versionversion=edb096e00724f02db5f6ec7900f3bbd465c6c76f <0e792b89e6800cd9cb4757a76a96f7ef3e8b6294
- Affected versionversion=edb096e00724f02db5f6ec7900f3bbd465c6c76f <88561a66777e7a2fe06638c6dcb22a9fae0b6733
- Affected versionversion=edb096e00724f02db5f6ec7900f3bbd465c6c76f <cc1b9961a0ceb70f6ca4e2f4b8bb71c87c7a495c
- Affected versionversion=edb096e00724f02db5f6ec7900f3bbd465c6c76f <ea5f2fd4640ecbb9df969bf8bb27733ae2183169
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.
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