Answer in brief
CVE-2024-36489 records a Unknown severity vulnerability in tls: fix missing memory barrier in tls_init. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d5bee7374b68de3c44586d46e9e61ffc97a1e886 <d72e126e9a36d3d33889829df8fc90100bb0e071 || >=d5bee7374b68de3c44586d46e9e61ffc97a1e886 <2c260a24cf1c4d30ea3646124f766ee46169280b || >=d5bee7374b68de3c44586d46e9e61ffc97a1e886 <335c8f1566d8e44c384d16b450a18554896d4e8b || >=d5bee7374b68de3c44586d46e9e61ffc97a1e886 <ab67c2fd3d070a21914d0c31319d3858ab4e199c || >=d5bee7374b68de3c44586d46e9e61ffc97a1e886 <ef21007a7b581c7fe64d5a10c320880a033c837b || >=d5bee7374b68de3c44586d46e9e61ffc97a1e886 <91e61dd7a0af660408e87372d8330ceb218be302 | d72e126e9a36d3d33889829df8fc90100bb0e071, 2c260a24cf1c4d30ea3646124f766ee46169280b, 335c8f1566d8e44c384d16b450a18554896d4e8b, ab67c2fd3d070a21914d0c31319d3858ab4e199c, ef21007a7b581c7fe64d5a10c320880a033c837b, 91e61dd7a0af660408e87372d8330ceb218be302 |
| Linux/Linuxgeneric | 5.7 | Not reported |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.1 | V3.1 |
| Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric | >=0 <V3.1 | V3.1 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <V1.1.1 | V1.1.1 |
Published upstream
Jun 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: tls: fix missing memory barrier in tls_init In tls_init(), a write memory barrier is missing, and store-store reordering may cause NULL dereference in tls_{setsockopt,getsockopt}. CPU0 CPU1 ----- ----- // In tls_init() // In tls_ctx_create() ctx = kzalloc() ctx->sk_proto = READ_ONCE(sk->sk_prot) -(1) // In update_sk_prot() WRITE_ONCE(sk->sk_prot, tls_prots) -(2) // In sock_common_setsockopt() READ_ONCE(sk->sk_prot)->setsockopt() // In tls_{setsockopt,getsockopt}() ctx->sk_proto->setsockopt() -(3) In the above scenario, when (1) and (2) are reordered, (3) can observe the NULL value of ctx->sk_proto, causing NULL dereference. To fix it, we rely on rcu_assign_pointer() which implies the release barrier semantic. By moving rcu_assign_pointer() after ctx->sk_proto is initialized, we can ensure that ctx->sk_proto are visible when changing sk->sk_prot.
Quoted source text, attributed separately from HOL analysis.