tls: fix missing memory barrier in tls_init
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.
CVE-2024-36489
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2024-36489
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "d5bee7374b68de3c44586d46e9e61ffc97a1e886",
"lessThan": "d72e126e9a36d3d33889829df8fc90100bb0e071",
"versionType": "git"
},
{
"status": "affected",
"version": "d5bee7374b68de3c44586d46e9e61ffc97a1e886",
"lessThan": "2c260a24cf1c4d30ea3646124f766ee46169280b",
"versionType": "git"
},
{
"status": "affected",
"version": "d5bee7374b68de3c44586d46e9e61ffc97a1e886",
"lessThan": "335c8f1566d8e44c384d16b450a18554896d4e8b",
"versionType": "git"
},
{
"status": "affected",
"version": "d5bee7374b68de3c44586d46e9e61ffc97a1e886",
"lessThan": "ab67c2fd3d070a21914d0c31319d3858ab4e199c",
"versionType": "git"
},
{
"status": "affected",
"version": "d5bee7374b68de3c44586d46e9e61ffc97a1e886",
"lessThan": "ef21007a7b581c7fe64d5a10c320880a033c837b",
"versionType": "git"
},
{
"status": "affected",
"version": "d5bee7374b68de3c44586d46e9e61ffc97a1e886",
"lessThan": "91e61dd7a0af660408e87372d8330ceb218be302",
"versionType": "git"
}
],
"programFiles": [
"net/tls/tls_main.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "5.7"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "5.7",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.10.219",
"versionType": "semver",
"lessThanOrEqual": "5.10.*"
},
{
"status": "unaffected",
"version": "5.15.161",
"versionType": "semver",
"lessThanOrEqual": "5.15.*"
},
{
"status": "unaffected",
"version": "6.1.93",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.33",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.9.4",
"versionType": "semver",
"lessThanOrEqual": "6.9.*"
},
{
"status": "unaffected",
"version": "6.10",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"net/tls/tls_main.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2024-36489
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #26584 · Revision 1
- Added to Heist Feed
- Publisher date