Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-36489tls: fix missing memory barrier in tls_init

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-36489, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d5bee7374b68de3c44586d46e9e61ffc97a1e886 – < d72e126e9a36d3d33889829df8fc90100bb0e071
    • affected d5bee7374b68de3c44586d46e9e61ffc97a1e886 – < 2c260a24cf1c4d30ea3646124f766ee46169280b
    • affected d5bee7374b68de3c44586d46e9e61ffc97a1e886 – < 335c8f1566d8e44c384d16b450a18554896d4e8b
    • affected d5bee7374b68de3c44586d46e9e61ffc97a1e886 – < ab67c2fd3d070a21914d0c31319d3858ab4e199c
    • affected d5bee7374b68de3c44586d46e9e61ffc97a1e886 – < ef21007a7b581c7fe64d5a10c320880a033c837b
    • affected d5bee7374b68de3c44586d46e9e61ffc97a1e886 – < 91e61dd7a0af660408e87372d8330ceb218be302
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.219 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.9.4 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-36489 badge
[![CVE-2024-36489](https://cveledger.app/badge/CVE-2024-36489.svg)](https://cveledger.app/cve/CVE-2024-36489)

Record last updated .