Kernel memory corruption via kprobe registration race
Published May 20, 2024 · Updated May 23, 2026
Use-after-free in Linux kernel kprobes allows attackers to corrupt kernel memory during concurrent module unloading and probe registration. check_kprobe_address_safe() separately checks a module-text address and looks up its module, allowing the module to reach MODULE_STATE_UNFORMED between operations. The race makes arm_kprobe() modify freed module text, which can crash the kernel or compromise its execution state.
Summary
What happened
Use-after-free in Linux kernel kprobes allows attackers to corrupt kernel memory during concurrent module unloading and probe registration. check_kprobe_address_safe() separately checks a module-text address and looks up its module, allowing the module to reach MODULE_STATE_UNFORMED between operations. The race makes arm_kprobe() modify freed module text, which can crash the kernel or compromise its execution state.
The record
- CVE
- CVE-2024-35955
- Published
- May 20, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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