tls: fix missing memory barrier in tls_init
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From d5bee7374b68de3c44586d46e9e61ffc97a1e886 · fixed in d72e126e9a36d3d33889829df8fc90100bb0e071; From d5bee7374b68de3c44586d46e9e61ffc97a1e886 · fixed in 2c260a24cf1c4d30ea3646124f766ee46169280b; From d5bee7374b68de3c44586d46e9e61ffc97a1e886 · fixed in 335c8f1566d8e44c384d16b450a18554896d4e8b; From d5bee7374b68de3c44586d46e9e61ffc97a1e886 · fixed in ab67c2fd3d070a21914d0c31319d3858ab4e199c; From d5bee7374b68de3c44586d46e9e61ffc97a1e886 · fixed in ef21007a7b581c7fe64d5a10c320880a033c837b; From d5bee7374b68de3c44586d46e9e61ffc97a1e886 · fixed in 91e61dd7a0af660408e87372d8330ceb218be302
- Linux Linux
5.7
- KernelLinux
From 5.7.0 · fixed in 5.10.219; From 5.11.0 · fixed in 5.15.161; From 5.16.0 · fixed in 6.1.93; From 6.2.0 · fixed in 6.6.33; From 6.7.0 · fixed in 6.9.4