CVE-2024-47659: linux
Vulnerability summary
CVE-2024-47659 is a critical (CVSS 9.1) vulnerability in linux. EPSS estimates a 0.78% chance of exploitation in the next 30 days, higher than 54.9% of scored vulnerabilities.
Advisory lineage
Upstream 0 · Downstream 18 · Related 24Timeline
- 09-10-2024PublishedVulnerability first disclosed.
- 05-08-2026Last modifiedVulnerability information updated.
Description
In the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated9.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- OSV · DebianEcosystem advisory · calculated8.8HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HDiffers
- NVDNIST8.8HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HDiffers
EPSS trend
Probability
0.78%
Chance of exploitation in the next 30 days
Percentile
55%
Versus all other CVEs
30-day change
0.00 pp
From 0.78% on 19-09-2026
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Ubuntu130 products
- linuxAll versions (No fix recorded) | < 4.4.0-278.312 | < 4.15.0-247.259 | < 5.4.0-200.220 | < 5.15.0-125.135 | < 6.8.0-50.51
- linux-allwinner-5.19All versions (No fix recorded)
- linux-aws< 4.4.0-1152.158 | < 4.4.0-1190.205 | < 4.15.0-1189.202 | < 5.4.0-1135.145 | < 5.15.0-1072.78 | < 6.8.0-1020.22
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Linux2 products
- linux≥ 07feee8f812f7327a46186f7604df312c8c81962, < d3f56c653c65f170b172d3c23120bc64ada645d8 | ≥ 07feee8f812f7327a46186f7604df312c8c81962, < 5b4b304f196c070342e32a4752e1fa2e22fc0671 | ≥ 07feee8f812f7327a46186f7604df312c8c81962, < a948ec993541db4ef392b555c37a1186f4d61670 | ≥ 07feee8f812f7327a46186f7604df312c8c81962, < 0aea09e82eafa50a373fc8a4b84c1d4734751e2c | ≥ 07feee8f812f7327a46186f7604df312c8c81962, < 0776bcf9cb6de46fdd94d10118de1cf9b05f83b9 | ≥ 07feee8f812f7327a46186f7604df312c8c81962, < 4be9fd15c3c88775bdf6fa37acabe6de85beebff | ≥ 07feee8f812f7327a46186f7604df312c8c81962, < d3703fa94116fed91f64c7d1c7d284fb4369070f | ≥ 07feee8f812f7327a46186f7604df312c8c81962, < 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550 | 2.6.30
- linux_kernel< 4.19.322 | ≥ 4.20, < 5.4.284 | ≥ 5.5, < 5.10.226 | ≥ 5.11, < 5.15.167 | ≥ 5.16, < 6.1.109 | ≥ 6.2, < 6.6.50 | ≥ 6.7, < 6.10.9
Debian1 product
- linux< 6.1.112-1 | < 6.10.9-1
3 vendors · 133 products
