Kernel crash via trace-probe argument miscount
Published Nov 5, 2024 · Updated Aug 5, 2026
NULL pointer dereference in Linux kernel 6.9 through 6.11.5 allows local users to crash the kernel via oversized trace-probe arguments. Trace-probe creation records nr_args before truncating fetch arguments to MAX_TRACE_ARGS, so __set_print_fmt reads uninitialized entries beyond the 128 initialized slots. A local low-privileged user must be able to configure a trace probe; successful triggering causes a kernel oops and service interruption.
Summary
What happened
NULL pointer dereference in Linux kernel 6.9 through 6.11.5 allows local users to crash the kernel via oversized trace-probe arguments. Trace-probe creation records nr_args before truncating fetch arguments to MAX_TRACE_ARGS, so __set_print_fmt reads uninitialized entries beyond the 128 initialized slots. A local low-privileged user must be able to configure a trace probe; successful triggering causes a kernel oops and service interruption.
The record
- CVE
- CVE-2024-50132
- Published
- Nov 5, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 2024CVE 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=035ba76014c096316fa809a46ce0a1b9af1cde0d <08ccd1a57c4d3882e9a877eb2dcc66e50a3b0279
- Affected versionversion=035ba76014c096316fa809a46ce0a1b9af1cde0d <73f35080477e893aa6f4c8d388352b871b288fbc
- Affected versionversion=6.9
- Affected versionversion=e96b42d22f66982b84e31b6935a59d74d9a2d848 <6bc24db74fe4788cc7c2f30a113fc6aafba225a3
What conditions does exploitation require?
What is affected?
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