UBUNTU-CVE-2024-47659: Medium severity ubuntu/linux vulnerability

Q: Which deployments are exposed to this issue?

The issue affects systems using active Smack with TCP over IPv4. The described scenario uses two machines with Smack in its default state, no configured settings, rules, or labeled hosts beyond the built-in labels, plus a server-side rule permitting 'foo' to write to 'bar'.

Q: What conditions are needed to trigger the incorrect labeling?

A process labeled 'bar' must listen for TCP/IPv4 connections on one machine, and a process labeled 'foo' on another machine must connect to it. After data is exchanged in both directions, returned IPv4 packets can carry the CIPSO label for 'foo' rather than 'bar'.

Q: How can I determine whether a connection is exhibiting the problem?

Capture the network traffic for a TCP/IPv4 connection between differently labeled Smack processes. In the affected scenario, packets in both directions are labeled with the CIPSO label of the connecting 'foo' process, including packets sent by the 'bar' listener.

Published Oct 9, 2024

Updated

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 Software

196 affected componentsFixes available

ubuntu/linux*

ubuntu/linux-aws<4.4.0-1152.158

4.4.0-1152.158

ubuntu/linux-azure<4.15.0-1197.212~14.04.1

4.15.0-1197.212~14.04.1

ubuntu/linux-lts-xenial<4.4.0-278.312~14.04.1

4.4.0-278.312~14.04.1

ubuntu/linux<4.4.0-278.312

4.4.0-278.312

ubuntu/linux-aws<4.4.0-1190.205

4.4.0-1190.205

ubuntu/linux-aws-hwe<4.15.0-1189.202~16.04.1

4.15.0-1189.202~16.04.1

ubuntu/linux-azure<4.15.0-1197.212~16.04.1

4.15.0-1197.212~16.04.1

ubuntu/linux-gcp<4.15.0-1182.199~16.04.1

4.15.0-1182.199~16.04.1

ubuntu/linux-hwe<4.15.0-247.259~16.04.1

4.15.0-247.259~16.04.1

ubuntu/linux-kvm<4.4.0-1153.164

4.4.0-1153.164

ubuntu/linux-oracle<4.15.0-1151.162~16.04.1

4.15.0-1151.162~16.04.1

ubuntu/linux-hwe-edge*

ubuntu/linux-fips<4.4.0-1122.129

4.4.0-1122.129

ubuntu/linux-fips*

ubuntu/linux<4.15.0-247.259

4.15.0-247.259

ubuntu/linux-aws<4.15.0-1189.202

4.15.0-1189.202

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-aws-5.4<5.4.0-1135.145~18.04.1

5.4.0-1135.145~18.04.1

ubuntu/linux-azure*

ubuntu/linux-azure-4.15<4.15.0-1197.212

4.15.0-1197.212

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-5.4<5.4.0-1140.147~18.04.1

5.4.0-1140.147~18.04.1

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-4.15<4.15.0-1182.199

4.15.0-1182.199

ubuntu/linux-gcp-5.3*

ubuntu/linux-gcp-5.4<5.4.0-1139.148~18.04.1

5.4.0-1139.148~18.04.1

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-5.4<5.4.0-200.220~18.04.1

5.4.0-200.220~18.04.1

ubuntu/linux-hwe-edge*

ubuntu/linux-ibm-5.4<5.4.0-1082.87~18.04.1

5.4.0-1082.87~18.04.1

ubuntu/linux-kvm<4.15.0-1171.176

4.15.0-1171.176

ubuntu/linux-oem*

ubuntu/linux-oracle<4.15.0-1151.162

4.15.0-1151.162

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-oracle-5.4<5.4.0-1134.143~18.04.1

5.4.0-1134.143~18.04.1

ubuntu/linux-raspi-5.4<5.4.0-1119.131~18.04.1

5.4.0-1119.131~18.04.1

ubuntu/linux-aws-fips<4.15.0-2127.133

4.15.0-2127.133

ubuntu/linux-azure-fips<4.15.0-2106.112

4.15.0-2106.112

ubuntu/linux-fips<4.15.0-1144.156

4.15.0-1144.156

ubuntu/linux-gcp-fips<4.15.0-2090.96

4.15.0-2090.96

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux<5.4.0-200.220

5.4.0-200.220

ubuntu/linux-aws<5.4.0-1135.145

5.4.0-1135.145

ubuntu/linux-aws-5.15<5.15.0-1072.78~20.04.1

5.15.0-1072.78~20.04.1

ubuntu/linux-azure<5.4.0-1140.147

5.4.0-1140.147

ubuntu/linux-azure-5.15<5.15.0-1078.87~20.04.1

5.15.0-1078.87~20.04.1

ubuntu/linux-bluefield<5.4.0-1095.102

5.4.0-1095.102

ubuntu/linux-gcp<5.4.0-1139.148

5.4.0-1139.148

ubuntu/linux-gcp-5.15<5.15.0-1071.79~20.04.1

5.15.0-1071.79~20.04.1

ubuntu/linux-gkeop<5.4.0-1102.106

5.4.0-1102.106

ubuntu/linux-gkeop-5.15<5.15.0-1055.62~20.04.1

5.15.0-1055.62~20.04.1

ubuntu/linux-hwe-5.15<5.15.0-125.135~20.04.1

5.15.0-125.135~20.04.1

ubuntu/linux-ibm<5.4.0-1082.87

5.4.0-1082.87

ubuntu/linux-ibm-5.15<5.15.0-1065.68~20.04.1

5.15.0-1065.68~20.04.1

ubuntu/linux-intel-iotg-5.15<5.15.0-1067.73~20.04.1

5.15.0-1067.73~20.04.1

ubuntu/linux-iot<5.4.0-1044.45

5.4.0-1044.45

ubuntu/linux-kvm<5.4.0-1123.131

5.4.0-1123.131

ubuntu/linux-lowlatency-hwe-5.15<5.15.0-125.135~20.04.1

5.15.0-125.135~20.04.1

ubuntu/linux-nvidia-tegra-5.15<5.15.0-1032.32~20.04.1

5.15.0-1032.32~20.04.1

ubuntu/linux-oracle<5.4.0-1134.143

5.4.0-1134.143

ubuntu/linux-oracle-5.15<5.15.0-1070.76~20.04.1

5.15.0-1070.76~20.04.1

ubuntu/linux-raspi<5.4.0-1119.131

5.4.0-1119.131

ubuntu/linux-riscv-5.15<5.15.0-1068.72~20.04.1

5.15.0-1068.72~20.04.1

ubuntu/linux-xilinx-zynqmp<5.4.0-1054.58

5.4.0-1054.58

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-aws-fips<5.4.0-1135.145+fips1

5.4.0-1135.145+fips1

ubuntu/linux-azure-fips<5.4.0-1140.147+fips1

5.4.0-1140.147+fips1

ubuntu/linux-fips<5.4.0-1109.119

5.4.0-1109.119

ubuntu/linux-gcp-fips<5.4.0-1139.148+fips1

5.4.0-1139.148+fips1

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux<5.15.0-125.135

5.15.0-125.135

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1072.78

5.15.0-1072.78

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1020.22~22.04.1

6.8.0-1020.22~22.04.1

ubuntu/linux-azure<5.15.0-1075.84

5.15.0-1075.84

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1020.23~22.04.1

6.8.0-1020.23~22.04.1

ubuntu/linux-azure-fde<5.15.0-1076.85.1

5.15.0-1076.85.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1071.79

5.15.0-1071.79

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1019.21~22.04.1

6.8.0-1019.21~22.04.1

ubuntu/linux-gke<5.15.0-1069.75

5.15.0-1069.75

ubuntu/linux-gkeop<5.15.0-1055.62

5.15.0-1055.62

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-hwe-6.8<6.8.0-50.51~22.04.1

6.8.0-50.51~22.04.1

ubuntu/linux-ibm<5.15.0-1065.68

5.15.0-1065.68

ubuntu/linux-ibm-6.8<6.8.0-1017.17~22.04.1

6.8.0-1017.17~22.04.1

ubuntu/linux-intel-iotg<5.15.0-1067.73

5.15.0-1067.73

ubuntu/linux-kvm<5.15.0-1069.74

5.15.0-1069.74

ubuntu/linux-lowlatency<5.15.0-125.135

5.15.0-125.135

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-50.51.1~22.04.1

6.8.0-50.51.1~22.04.1

ubuntu/linux-nvidia<5.15.0-1067.68

5.15.0-1067.68

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1019.21~22.04.1

6.8.0-1019.21~22.04.1

ubuntu/linux-nvidia-tegra<5.15.0-1032.32

5.15.0-1032.32

ubuntu/linux-nvidia-tegra-igx<5.15.0-1020.20

5.15.0-1020.20

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle<5.15.0-1070.76

5.15.0-1070.76

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8<6.8.0-1017.18~22.04.1

6.8.0-1017.18~22.04.1

ubuntu/linux-raspi<5.15.0-1065.68

5.15.0-1065.68

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-50.51.1~22.04.1

6.8.0-50.51.1~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-xilinx-zynqmp<5.15.0-1038.42

5.15.0-1038.42

ubuntu/linux-bluefield<5.15.0-1056.58

5.15.0-1056.58

ubuntu/linux-intel-iot-realtime<5.15.0-1066.68

5.15.0-1066.68

ubuntu/linux-realtime<5.15.0-1073.81

5.15.0-1073.81

ubuntu/linux-realtime-6.8<6.8.1-1013.14~22.04.1

6.8.1-1013.14~22.04.1

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux-aws-fips<5.15.0-1072.78+fips1

5.15.0-1072.78+fips1

ubuntu/linux-azure-fips<5.15.0-1075.84+fips1

5.15.0-1075.84+fips1

ubuntu/linux-fips<5.15.0-125.135+fips1

5.15.0-125.135+fips1

ubuntu/linux-gcp-fips<5.15.0-1071.79+fips1

5.15.0-1071.79+fips1

ubuntu/linux<6.8.0-50.51

6.8.0-50.51

ubuntu/linux-aws<6.8.0-1020.22

6.8.0-1020.22

ubuntu/linux-azure<6.8.0-1020.23

6.8.0-1020.23

ubuntu/linux-gcp<6.8.0-1019.21

6.8.0-1019.21

ubuntu/linux-gke<6.8.0-1015.19

6.8.0-1015.19

ubuntu/linux-gkeop<6.8.0-1002.4

6.8.0-1002.4

ubuntu/linux-ibm<6.8.0-1017.17

6.8.0-1017.17

ubuntu/linux-lowlatency<6.8.0-50.51.1

6.8.0-50.51.1

ubuntu/linux-nvidia<6.8.0-1019.21

6.8.0-1019.21

ubuntu/linux-nvidia-lowlatency<6.8.0-1019.21.1

6.8.0-1019.21.1

ubuntu/linux-oem-6.8<6.8.0-1018.18

6.8.0-1018.18

ubuntu/linux-oracle<6.8.0-1017.18

6.8.0-1017.18

ubuntu/linux-raspi<6.8.0-1016.18

6.8.0-1016.18

ubuntu/linux-riscv<6.8.0-50.51.1

6.8.0-50.51.1

ubuntu/linux-xilinx<6.8.0-1017.18

6.8.0-1017.18

ubuntu/linux-raspi-realtime<6.8.0-2015.16

6.8.0-2015.16

ubuntu/linux-realtime<6.8.1-1013.14

6.8.1-1013.14

ubuntu/linux-fips<6.8.0-78.78+fips1

6.8.0-78.78+fips1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 4.4.0-1152.158
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 4.15.0-1197.212~14.04.1
Upgrade
Upgrade ubuntu/linux-lts-xenial to a version that resolves this vulnerability.
Fixed in 4.4.0-278.312~14.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 4.4.0-278.312
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 4.4.0-1190.205
Upgrade
Upgrade ubuntu/linux-aws-hwe to a version that resolves this vulnerability.
Fixed in 4.15.0-1189.202~16.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 4.15.0-1197.212~16.04.1
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 4.15.0-1182.199~16.04.1
Upgrade
Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.
Fixed in 4.15.0-247.259~16.04.1
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 4.4.0-1153.164
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 4.15.0-1151.162~16.04.1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 4.4.0-1122.129
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 4.15.0-247.259
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 4.15.0-1189.202
Upgrade
Upgrade ubuntu/linux-aws-5.4 to a version that resolves this vulnerability.
Fixed in 5.4.0-1135.145~18.04.1
Upgrade
Upgrade ubuntu/linux-azure-4.15 to a version that resolves this vulnerability.
Fixed in 4.15.0-1197.212
Upgrade
Upgrade ubuntu/linux-azure-5.4 to a version that resolves this vulnerability.
Fixed in 5.4.0-1140.147~18.04.1
Upgrade
Upgrade ubuntu/linux-gcp-4.15 to a version that resolves this vulnerability.
Fixed in 4.15.0-1182.199
Upgrade
Upgrade ubuntu/linux-gcp-5.4 to a version that resolves this vulnerability.
Fixed in 5.4.0-1139.148~18.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.4 to a version that resolves this vulnerability.
Fixed in 5.4.0-200.220~18.04.1
Upgrade
Upgrade ubuntu/linux-ibm-5.4 to a version that resolves this vulnerability.
Fixed in 5.4.0-1082.87~18.04.1
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 4.15.0-1171.176
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 4.15.0-1151.162
Upgrade
Upgrade ubuntu/linux-oracle-5.4 to a version that resolves this vulnerability.
Fixed in 5.4.0-1134.143~18.04.1
Upgrade
Upgrade ubuntu/linux-raspi-5.4 to a version that resolves this vulnerability.
Fixed in 5.4.0-1119.131~18.04.1
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 4.15.0-2127.133
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 4.15.0-2106.112
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 4.15.0-1144.156
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 4.15.0-2090.96
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.4.0-200.220
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.4.0-1135.145
Upgrade
Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1072.78~20.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.4.0-1140.147
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1078.87~20.04.1
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.4.0-1095.102
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.4.0-1139.148
Upgrade
Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1071.79~20.04.1
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.4.0-1102.106
Upgrade
Upgrade ubuntu/linux-gkeop-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1055.62~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-125.135~20.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.4.0-1082.87
Upgrade
Upgrade ubuntu/linux-ibm-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1065.68~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1067.73~20.04.1
Upgrade
Upgrade ubuntu/linux-iot to a version that resolves this vulnerability.
Fixed in 5.4.0-1044.45
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.4.0-1123.131
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-125.135~20.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1032.32~20.04.1
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.4.0-1134.143
Upgrade
Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1070.76~20.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.4.0-1119.131
Upgrade
Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1068.72~20.04.1
Upgrade
Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.
Fixed in 5.4.0-1054.58
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 5.4.0-1135.145+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 5.4.0-1140.147+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 5.4.0-1109.119
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 5.4.0-1139.148+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-125.135
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1072.78
Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1020.22~22.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1075.84
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1020.23~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 5.15.0-1076.85.1
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1071.79
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1019.21~22.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1069.75
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.15.0-1055.62
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-50.51~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1065.68
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.17~22.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1067.73
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1069.74
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-125.135
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-50.51.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 5.15.0-1067.68
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1019.21~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 5.15.0-1032.32
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-igx to a version that resolves this vulnerability.
Fixed in 5.15.0-1020.20
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1070.76
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.18~22.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1065.68
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-50.51.1~22.04.1
Upgrade
Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.
Fixed in 5.15.0-1038.42
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.15.0-1056.58
Upgrade
Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1066.68
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1073.81
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1013.14~22.04.1
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1072.78+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1075.84+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-125.135+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1071.79+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-50.51
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1020.22
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1020.23
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1019.21
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1015.19
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1002.4
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.17
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-50.51.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1019.21
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1019.21.1
Upgrade
Upgrade ubuntu/linux-oem-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1018.18
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.18
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1016.18
Upgrade
Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.
Fixed in 6.8.0-50.51.1
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.18
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2015.16
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1013.14
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-78.78+fips1

Event History

Oct 9, 2024

CVE Published

via OSV·02:15 PM

Data Sourced

via OSV·02:15 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which deployments are exposed to this issue?

The issue affects systems using active Smack with TCP over IPv4. The described scenario uses two machines with Smack in its default state, no configured settings, rules, or labeled hosts beyond the built-in labels, plus a server-side rule permitting 'foo' to write to 'bar'.

What conditions are needed to trigger the incorrect labeling?

A process labeled 'bar' must listen for TCP/IPv4 connections on one machine, and a process labeled 'foo' on another machine must connect to it. After data is exchanged in both directions, returned IPv4 packets can carry the CIPSO label for 'foo' rather than 'bar'.

How can I determine whether a connection is exhibiting the problem?

Capture the network traffic for a TCP/IPv4 connection between differently labeled Smack processes. In the affected scenario, packets in both directions are labeled with the CIPSO label of the connecting 'foo' process, including packets sent by the 'bar' listener.

UBUNTU-CVE-2024-47659: Medium severity ubuntu/linux vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed to this issue?

What conditions are needed to trigger the incorrect labeling?

How can I determine whether a connection is exhibiting the problem?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed to this issue?

What conditions are needed to trigger the incorrect labeling?

How can I determine whether a connection is exhibiting the problem?