Vulnerability · Published Oct 9, 2024 · Assigned by Linux

CVE-2024-47659smack: tcp: ipv4, fix incorrect labeling

Critical 9.1

In plain English

A critical-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.8% (higher than 56% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.1Critical
Exploit odds (30 days)0.8%top 44.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.112-1DEBIAN-CVE-2024-47659
Debian:13linux6.10.9-1DEBIAN-CVE-2024-47659
Debian:14linux6.10.9-1DEBIAN-CVE-2024-47659
Ubuntu:22.04:LTSlinux5.15.0-125.135UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux6.8.0-50.51UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-aws5.15.0-1072.78UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-aws6.8.0-1020.22UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1020.22~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure5.15.0-1075.84UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-azure6.8.0-1020.23UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1020.23~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1076.85.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-gcp5.15.0-1071.79UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-gcp6.8.0-1019.21UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1019.21~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-gke5.15.0-1069.75UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-gke6.8.0-1015.19UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1055.62UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1002.4UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-50.51~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-ibm5.15.0-1065.68UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-ibm6.8.0-1017.17UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1017.17~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1067.73UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-kvm5.15.0-1069.74UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-125.135UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-50.51.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-50.51.1~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1067.68UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1019.21UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1019.21~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1019.21.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1032.32UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1020.20UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-oem-6.86.8.0-1018.18UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-oracle5.15.0-1070.76UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-oracle6.8.0-1017.18UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1017.18~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-raspi5.15.0-1065.68UBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-raspi6.8.0-1016.18UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-riscv6.8.0-50.51.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-50.51.1~22.04.1UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2024-47659
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1017.18UBUNTU-CVE-2024-47659
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1038.42UBUNTU-CVE-2024-47659

Affected products (as reported)

VendorProductVersions
Linux Linux 07feee8f812f7327a46186f7604df312c8c81962 – before d3f56c653c65f170b172d3c23120bc64ada645d807feee8f812f7327a46186f7604df312c8c81962 – before 5b4b304f196c070342e32a4752e1fa2e22fc067107feee8f812f7327a46186f7604df312c8c81962 – before a948ec993541db4ef392b555c37a1186f4d6167007feee8f812f7327a46186f7604df312c8c81962 – before 0aea09e82eafa50a373fc8a4b84c1d4734751e2c07feee8f812f7327a46186f7604df312c8c81962 – before 0776bcf9cb6de46fdd94d10118de1cf9b05f83b907feee8f812f7327a46186f7604df312c8c81962 – before 4be9fd15c3c88775bdf6fa37acabe6de85beebff07feee8f812f7327a46186f7604df312c8c81962 – before d3703fa94116fed91f64c7d1c7d284fb4369070f07feee8f812f7327a46186f7604df312c8c81962 – before 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550
Linux Linux 2.6.30

References