Kernel memory corruption via unterminated trace event name
Published Nov 5, 2024 · Updated Aug 5, 2026
Buffer overflow in affected Linux kernel tracing allows local users to corrupt kernel memory through an exactly 64-character event name. traceprobe_parse_event_name in kernel/trace/trace_probe.c accepts a name whose strlen equals MAX_EVENT_NAME_LEN, leaving no room for the terminating null byte. Reachability requires local write access to tracefs probe-event controls; no network-facing path or user interaction is involved.
Summary
What happened
Buffer overflow in affected Linux kernel tracing allows local users to corrupt kernel memory through an exactly 64-character event name. traceprobe_parse_event_name in kernel/trace/trace_probe.c accepts a name whose strlen equals MAX_EVENT_NAME_LEN, leaving no room for the terminating null byte. Reachability requires local write access to tracefs probe-event controls; no network-facing path or user interaction is involved.
The record
- CVE
- CVE-2024-50131
- Published
- Nov 5, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-120, T1068
- 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=0 <*
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