{"schema_version":"1.9.0","id":"CVE-2024-36489","published":"2024-06-21T10:18:10.327Z","modified":"2026-08-12T03:51:34.370203849Z","related":["ALSA-2024:5363","SUSE-SU-2024:3190-1","SUSE-SU-2024:3194-1","SUSE-SU-2024:3195-1","SUSE-SU-2024:3209-1","SUSE-SU-2024:3383-1","SUSE-SU-2024:3483-1","SUSE-SU-2025:20044-1","SUSE-SU-2025:20047-1"],"summary":"tls: fix missing memory barrier in tls_init","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix missing memory barrier in tls_init\n\nIn tls_init(), a write memory barrier is missing, and store-store\nreordering may cause NULL dereference in tls_{setsockopt,getsockopt}.\n\nCPU0                               CPU1\n-----                              -----\n// In tls_init()\n// In tls_ctx_create()\nctx = kzalloc()\nctx->sk_proto = READ_ONCE(sk->sk_prot) -(1)\n\n// In update_sk_prot()\nWRITE_ONCE(sk->sk_prot, tls_prots)     -(2)\n\n                                   // In sock_common_setsockopt()\n                                   READ_ONCE(sk->sk_prot)->setsockopt()\n\n                                   // In tls_{setsockopt,getsockopt}()\n                                   ctx->sk_proto->setsockopt()    -(3)\n\nIn the above scenario, when (1) and (2) are reordered, (3) can observe\nthe NULL value of ctx->sk_proto, causing NULL dereference.\n\nTo fix it, we rely on rcu_assign_pointer() which implies the release\nbarrier semantic. By moving rcu_assign_pointer() after ctx->sk_proto is\ninitialized, we can ensure that ctx->sk_proto are visible when\nchanging sk->sk_prot.","affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"d5bee7374b68de3c44586d46e9e61ffc97a1e886"},{"fixed":"d72e126e9a36d3d33889829df8fc90100bb0e071"},{"fixed":"2c260a24cf1c4d30ea3646124f766ee46169280b"},{"fixed":"335c8f1566d8e44c384d16b450a18554896d4e8b"},{"fixed":"ab67c2fd3d070a21914d0c31319d3858ab4e199c"},{"fixed":"ef21007a7b581c7fe64d5a10c320880a033c837b"},{"fixed":"91e61dd7a0af660408e87372d8330ceb218be302"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-36489.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.7.0"},{"fixed":"5.10.219"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.161"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.93"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.33"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.9.4"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-36489.json"}}],"references":[{"type":"WEB","url":"https://cert-portal.siemens.com/productcert/html/ssa-265688.html"},{"type":"WEB","url":"https://cert-portal.siemens.com/productcert/html/ssa-613116.html"},{"type":"WEB","url":"https://git.kernel.org/stable/c/2c260a24cf1c4d30ea3646124f766ee46169280b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/335c8f1566d8e44c384d16b450a18554896d4e8b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/91e61dd7a0af660408e87372d8330ceb218be302"},{"type":"WEB","url":"https://git.kernel.org/stable/c/ab67c2fd3d070a21914d0c31319d3858ab4e199c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d72e126e9a36d3d33889829df8fc90100bb0e071"},{"type":"WEB","url":"https://git.kernel.org/stable/c/ef21007a7b581c7fe64d5a10c320880a033c837b"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/36xxx/CVE-2024-36489.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36489"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/36xxx/CVE-2024-36489.json"}}