CVE-2024-36489: tls: fix missing memory barrier in tls_init
First published: Fri Jun 21 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <5.10.219 | 5.10.219 |
| redhat/kernel | <5.15.161 | 5.15.161 |
| redhat/kernel | <6.1.93 | 6.1.93 |
| redhat/kernel | <6.6.33 | 6.6.33 |
| redhat/kernel | <6.9.4 | 6.9.4 |
| redhat/kernel | <6.10 | 6.10 |
| Linux Kernel | >=5.7<5.10.219 | |
| Linux Kernel | >=5.11<5.15.161 | |
| Linux Kernel | >=5.16<6.1.93 | |
| Linux Kernel | >=6.2<6.6.33 | |
| Linux Kernel | >=6.7<6.9.4 | |
| debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 | |
| IBM Security Verify Governance - Identity Manager | <=ISVG 10.0.2 | |
| IBM Security Verify Governance, Identity Manager Software Stack | <=ISVG 10.0.2 | |
| IBM Security Verify Governance, Identity Manager Virtual Appliance | <=ISVG 10.0.2 | |
| IBM Security Verify Governance Identity Manager Container | <=ISVG 10.0.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/2c260a24cf1c4d30ea3646124f766ee46169280b
- https://git.kernel.org/stable/c/335c8f1566d8e44c384d16b450a18554896d4e8b
- https://git.kernel.org/stable/c/91e61dd7a0af660408e87372d8330ceb218be302
- https://git.kernel.org/stable/c/ab67c2fd3d070a21914d0c31319d3858ab4e199c
- https://git.kernel.org/stable/c/d72e126e9a36d3d33889829df8fc90100bb0e071
- https://git.kernel.org/stable/c/ef21007a7b581c7fe64d5a10c320880a033c837b
- https://launchpad.net/bugs/cve/CVE-2024-36489
- https://access.redhat.com/security/cve/CVE-2024-36489
- https://lore.kernel.org/linux-cve-announce/2024062136-CVE-2024-36489-7213@gregkh/T
- https://access.redhat.com/errata/RHSA-2024:4823
- https://access.redhat.com/errata/RHSA-2024:4831
- https://access.redhat.com/errata/RHSA-2024:5065
- https://access.redhat.com/errata/RHSA-2024:5102
- https://access.redhat.com/errata/RHSA-2024:5101
- https://access.redhat.com/errata/RHSA-2024:5363
- https://access.redhat.com/errata/RHSA-2024:6206
- https://bugzilla.redhat.com/show_bug.cgi?id=2293687
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36489
- https://nvd.nist.gov/vuln/detail/CVE-2024-36489
- https://security-tracker.debian.org/tracker/CVE-2024-36489
- https://ubuntu.com/security/CVE-2024-36489
- https://git.kernel.org/linus/91e61dd7a0af660408e87372d8330ceb218be302
- https://www.ibm.com/support/pages/node/7230443 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2024-36489?
CVE-2024-36489 is rated as a high severity vulnerability due to the potential for NULL dereference in specific TLS operations.
How do I fix CVE-2024-36489?
To fix CVE-2024-36489, upgrade your Linux kernel to version 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.13-1 as recommended.
Which Linux kernel versions are affected by CVE-2024-36489?
CVE-2024-36489 affects Linux kernel versions prior to 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.4, and 6.10.
What are the specific operations that may lead to a vulnerability in CVE-2024-36489?
The vulnerability in CVE-2024-36489 may cause NULL dereference during tls_{setsockopt, getsockopt} due to missing memory barriers.
Is there a workaround for CVE-2024-36489?
There are no known workarounds for CVE-2024-36489; the recommended action is to apply the necessary kernel updates.
- agent/title
- agent/type
- agent/severity
- agent/weakness
- collector/launchpad-cve
- source/Launchpad
- agent/author
- agent/remedy
- agent/first-publish-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-36489
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/trending
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-cve
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- agent/last-modified-date
- agent/references
- agent/source
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- collector/ibm-support
- source/IBM
- package-manager/redhat
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.7
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- package-manager/debian
- vendor/ibm
- canonical/ibm security verify governance - identity manager
- version/ibm security verify governance - identity manager/isvg 10.0.2
- canonical/ibm security verify governance, identity manager software stack
- version/ibm security verify governance, identity manager software stack/isvg 10.0.2
- canonical/ibm security verify governance, identity manager virtual appliance
- version/ibm security verify governance, identity manager virtual appliance/isvg 10.0.2
- canonical/ibm security verify governance identity manager container
- version/ibm security verify governance identity manager container/isvg 10.0.2