ftrace initialization failure via incorrect module PLT handling
Published Oct 22, 2025 · Updated Oct 22, 2025
Incorrect callsite handling in Linux arm64 ftrace allows local users to make ftrace initialization fail by loading a distant module. ftrace_make_nop assumes each mcount callsite targets the special ftrace trampoline PLT, so ftrace_find_callable_addr rejects an out-of-range _mcount stub reached through an ordinary module PLT. Reaching the flaw requires module-loading privileges, mcount-based ftrace, module PLTs, and a module placed sufficiently far from the kernel; the observed consequence is a kernel warning and failure to modify the callsite.
Summary
What happened
Incorrect callsite handling in Linux arm64 ftrace allows local users to make ftrace initialization fail by loading a distant module. ftrace_make_nop assumes each mcount callsite targets the special ftrace trampoline PLT, so ftrace_find_callable_addr rejects an out-of-range _mcount stub reached through an ordinary module PLT. Reaching the flaw requires module-loading privileges, mcount-based ftrace, module PLTs, and a module placed sufficiently far from the kernel; the observed consequence is a kernel warning and failure to modify the callsite.
The record
- CVE
- CVE-2022-50579
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record 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=5.19
- Affected versionversion=a6253579977e4c6f7818eeb05bf2bc65678a7187 <0f77b6b2ba70d7c9d69ef39694e283ded9f8b5f2
- Affected versionversion=a6253579977e4c6f7818eeb05bf2bc65678a7187 <8cfb08575c6d4585f1ce0deeb189e5c824776b04
- Affected versionversion=a6253579977e4c6f7818eeb05bf2bc65678a7187 <985432303cf7d4804fb2c2fdfbf0466a796d68c3
- Affected versionversion=bc28fde90937a920f7714ec4408269cac744f796 <657de36c72f57fa172a66b06f826b3f5bc56f42e
- Affected versionversion=db73aa9466338ec821ed2a0b01721fe4d06876b1 <6c93b683cedaef745884cb9d554d02ed6266b897
- Affected versionversion=dcecc96ed16f73417de5550f384e348c9d56f279
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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