Local system crash via TLS initialization race
Published Jun 21, 2024 · Updated May 12, 2026
NULL pointer dereference in the Linux kernel allows local users to crash the system through concurrent TLS socket operations. In tls_init, sk->sk_prot can be published before ctx->sk_proto is initialized because a write memory barrier is missing, so tls_setsockopt or tls_getsockopt can dereference NULL. A low-privileged local user must win the store-ordering race; the demonstrated consequence is a kernel crash, with no reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in the Linux kernel allows local users to crash the system through concurrent TLS socket operations. In tls_init, sk->sk_prot can be published before ctx->sk_proto is initialized because a write memory barrier is missing, so tls_setsockopt or tls_getsockopt can dereference NULL. A low-privileged local user must win the store-ordering race; the demonstrated consequence is a kernel crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2024-36489
- Published
- Jun 21, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-20, CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 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