Vulnerability · Published Oct 29, 2024 · Assigned by Linux
CVE-2024-50072x86/bugs: Use code segment selector for VERW operand
Medium 5.5
In plain English
A medium-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.2% (higher than 14% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: x86/bugs: Use code segment selector for VERW operand Robert Gill reported below #GP in 32-bit mode when dosemu software was executing vm86() system call: general protection fault: 0000 [#1] PREEMPT SMP CPU: 4 PID: 4610 Comm: dosemu.bin Not tainted 6.6.21-gentoo-x86 #1 Hardware name: Dell Inc. PowerEdge 1950/0H723K, BIOS 2.7.0 10/30/2010 EIP: restore_all_switch_stack+0xbe/0xcf EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000 ESI: 00000000 EDI: 00000000 EBP: 00000000 ESP: ff8affdc DS: 0000 ES: 0000 FS: 0000 GS: 0033 SS: 0068 EFLAGS: 00010046 CR0: 80050033 CR2: 00c2101c CR3: 04b6d000 CR4: 000406d0 Call Trace: show_regs+0x70/0x78 die_addr+0x29/0x70 exc_general_protection+0x13c/0x348 exc_bounds+0x98/0x98 handle_exception+0x14d/0x14d exc_bounds+0x98/0x98 restore_all_switch_stack+0xbe/0xcf exc_bounds+0x98/0x98 restore_all_switch_stack+0xbe/0xcf This only happens in 32-bit mode when VERW based mitigations like MDS/RFDS are enabled. This is because segment registers with an arbitrary user value can result in #GP when executing VERW. Intel SDM vol. 2C documents the following behavior for VERW instruction: #GP(0) - If a memory operand effective address is outside the CS, DS, ES, FS, or GS segment limit. CLEAR_CPU_BUFFERS macro executes VERW instruction before returning to user space. Use %cs selector to reference VERW operand. This ensures VERW will not #GP for an arbitrary user %ds. [ mingo: Fixed the SOB chain. ]
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.119-1 | DSA-5818-1 |
| Debian:12 | linux | 6.1.119-1 | DEBIAN-CVE-2024-50072 |
| Debian:13 | linux | 6.11.5-1 | DEBIAN-CVE-2024-50072 |
| Debian:14 | linux | 6.11.5-1 | DEBIAN-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux | 5.15.0-133.144 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux | 5.15.0-133.144 | USN-7288-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-56.58 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1078.85 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1078.85 | USN-7308-1 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1025.27 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1027.29~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1081.90 | USN-7289-1 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1081.90 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1025.30 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1012.12~24.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1025.30~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1081.90.1 | USN-7289-1 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1081.90.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1014.15 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1077.86 | USN-7291-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1077.86 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1026.28 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1011.11~24.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1026.28~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1075.81 | USN-7291-1 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1075.81 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1021.25 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1060.68 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1060.68 | USN-7289-1 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1008.10 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-57.59~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1070.73 | USN-7289-3 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1070.73 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1022.22 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1023.23~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1073.79 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1073.79 | USN-7289-4 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1076.81 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1076.81 | USN-7388-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-133.143 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-133.143 | USN-7288-1 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-56.58.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-56.58.1~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1072.73 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1072.73 | USN-7289-1 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1024.27 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1007.7 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1024.27~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1024.27.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1033.33 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1033.33 | USN-7389-1 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1004.4 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1021.21 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1021.21 | USN-7389-1 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1015.15 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1024.24 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1075.81 | USN-7289-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1075.81 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1022.23 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1022.23~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1072.75 | USN-7305-1 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1072.75 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1028.32 | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-56.58.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-56.58.1~22.04.1 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-50072 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1017.18 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1044.48 | UBUNTU-CVE-2024-50072 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1044.48 | USN-7390-1 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 50f021f0b985629accf10481a6e89af8b9700583 – before bfd1d223d80cb29a210caa1bd5e21f0816d58f02d54de9f2a127090f2017184e8257795b487d5312 – before ada431c6c31a2c8c37991c46089af5caa23a9c6e2e3087505ddb8ba2d3d4c81306cca11e868fcdb9 – before 38c5fe74f3bef98f75d16effa49836d50c9b6097ca13d8cd8dac25558da4ee8df4dc70e8e7f9d762 – before 481b477ab63c7245715a3e57ba79eb87c2dc0d02a0e2dab44d22b913b4c228c8b52b2a104434b0b3 – before bc576fbaf82deded606e69a00efe9752136bf91da0e2dab44d22b913b4c228c8b52b2a104434b0b3 – before e4d2102018542e3ae5e297bc6e229303abff8a0f51eca9f1fd047b500137d021f882d93f032801185.10.215 – before 5.10.229 |
| Linux | Linux | 6.8 |
References
- https://git.kernel.org/stable/c/bfd1d223d80cb29a210caa1bd5e21f0816d58f02
- https://git.kernel.org/stable/c/ada431c6c31a2c8c37991c46089af5caa23a9c6e
- https://git.kernel.org/stable/c/38c5fe74f3bef98f75d16effa49836d50c9b6097
- https://git.kernel.org/stable/c/481b477ab63c7245715a3e57ba79eb87c2dc0d02
- https://git.kernel.org/stable/c/bc576fbaf82deded606e69a00efe9752136bf91d
- https://git.kernel.org/stable/c/e4d2102018542e3ae5e297bc6e229303abff8a0f
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html