CVE-2024-50072

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-10-29. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

October 29, 2024

Last Modified

November 3, 2025

References (8)

Patch Availability(29)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-nolpae (5.15.0.1072.70) @ jammy2026-05-23ubuntu
ubuntulinux-virtual (6.8.0-56.58) @ noble2026-05-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1073.79~20.04.2) @ focal2026-05-23ubuntu
ubuntulinux-tools-ibm (5.15.0.1070.66) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1078.80) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.134.145~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.133.143~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.133.132) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1075.81~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1075.71) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1075.74) @ jammy2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-05-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-05-23ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1018.19) @ noble2026-05-23ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-23ubuntu
linuxKernel @ 5.10.229—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)5.10.234-1—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u16.1.119-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (31 versions)6.1.119-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.5-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.5-1—

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-09-20 20:14 UTCEPSS rescore
  2. 2026-09-20 20:14 UTCEPSS rescore
  3. 2026-09-20 20:03 UTCOSV refresh
  4. 2026-09-19 15:40 UTCEPSS rescore
  5. 2026-09-18 19:26 UTCEPSS rescore
  6. 2026-09-17 19:27 UTCEPSS rescore
  7. 2026-09-16 14:06 UTCEPSS rescore
  8. 2026-09-16 05:12 UTCEPSS rescore
  9. 2026-09-15 03:08 UTCEPSS rescore
  10. 2026-09-15 03:08 UTCEPSS rescore
  11. 2026-09-13 16:45 UTCEPSS rescore
  12. 2026-09-12 14:59 UTCEPSS rescore
  13. 2026-09-11 14:51 UTCEPSS rescore
  14. 2026-09-11 09:35 UTCEPSS rescore
  15. 2026-09-10 09:33 UTCEPSS rescore
  16. 2026-09-08 21:58 UTCEPSS rescore
  17. 2026-09-07 16:00 UTCEPSS rescore
  18. 2026-09-06 13:46 UTCEPSS rescore
  19. 2026-09-06 13:46 UTCEPSS rescore
  20. 2026-09-04 13:59 UTCEPSS rescore
  21. 2026-09-04 05:05 UTCEPSS rescore
  22. 2026-09-02 14:10 UTCEPSS rescore
  23. 2026-09-01 19:43 UTCOSV refresh
  24. 2026-09-01 13:52 UTCEPSS rescore
  25. 2026-09-01 13:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-01 04:37 UTCEPSS rescore
  2. 2026-08-30 19:16 UTCEPSS rescore
  3. 2026-08-30 01:20 UTCEPSS rescore
  4. 2026-08-28 21:39 UTCEPSS rescore
  5. 2026-08-27 14:23 UTCEPSS rescore
  6. 2026-08-26 14:44 UTCEPSS rescore
  7. 2026-08-25 13:47 UTCEPSS rescore
  8. 2026-08-24 14:15 UTCEPSS rescore
  9. 2026-08-23 00:18 UTCEPSS rescore
  10. 2026-08-21 23:47 UTCEPSS rescore
  11. 2026-08-20 22:54 UTCEPSS rescore
  12. 2026-08-19 17:02 UTCEPSS rescore
  13. 2026-08-19 17:02 UTCEPSS rescore
  14. 2026-08-18 13:46 UTCEPSS rescore
  15. 2026-08-17 13:45 UTCEPSS rescore
  16. 2026-08-16 14:54 UTCEPSS rescore
  17. 2026-08-16 02:13 UTCEPSS rescore
  18. 2026-08-15 21:37 UTCOSV refresh
  19. 2026-08-15 01:29 UTCEPSS rescore
  20. 2026-08-13 21:59 UTCEPSS rescore
  21. 2026-08-12 13:49 UTCEPSS rescore
  22. 2026-08-11 13:40 UTCEPSS rescore
  23. 2026-08-10 23:58 UTCEPSS rescore
  24. 2026-08-09 13:45 UTCEPSS rescore
  25. 2026-08-08 16:35 UTCEPSS rescore
  26. 2026-08-07 16:25 UTCEPSS rescore
  27. 2026-08-06 13:45 UTCEPSS rescore
  28. 2026-08-05 19:16 UTCEPSS rescore
  29. 2026-08-04 15:08 UTCEPSS rescore
  30. 2026-08-04 10:36 UTCEPSS rescore
  31. 2026-08-03 10:34 UTCEPSS rescore
  32. 2026-08-02 02:25 UTCEPSS rescore
  33. 2026-08-01 04:14 UTCEPSS rescore
  34. 2026-08-01 04:14 UTCEPSS rescore
  35. 2026-07-31 14:42 UTCOSV refresh
  36. 2026-07-30 16:26 UTCEPSS rescore
  37. 2026-07-30 01:29 UTCEPSS rescore
  38. 2026-07-28 15:35 UTCEPSS rescore
  39. 2026-07-27 14:11 UTCEPSS rescore
  40. 2026-07-26 14:53 UTCEPSS rescore
  41. 2026-07-26 14:53 UTCEPSS rescore
  42. 2026-07-25 14:17 UTCEPSS rescore
  43. 2026-07-25 14:16 UTCEPSS rescore
  44. 2026-07-24 14:16 UTCEPSS rescore
  45. 2026-07-23 14:17 UTCEPSS rescore
  46. 2026-07-23 14:17 UTCEPSS rescore
  47. 2026-07-23 02:42 UTCEG score recompute
  48. 2026-07-22 14:07 UTCEPSS rescore
  49. 2026-07-22 14:07 UTCEPSS rescore
  50. 2026-07-21 15:23 UTCEPSS rescore
  51. 2026-07-20 17:06 UTCEPSS rescore
  52. 2026-07-19 14:30 UTCEPSS rescore
  53. 2026-07-19 14:30 UTCEPSS rescore
  54. 2026-07-19 02:28 UTCEPSS rescore
  55. 2026-07-19 02:28 UTCEPSS rescore
  56. 2026-07-18 10:03 UTCEPSS rescore
  57. 2026-07-18 10:03 UTCEPSS rescore
  58. 2026-07-16 17:02 UTCEPSS rescore
  59. 2026-07-15 16:57 UTCEPSS rescore
  60. 2026-07-15 16:56 UTCEPSS rescore
  61. 2026-07-15 01:59 UTCEPSS rescore
  62. 2026-07-15 01:59 UTCEPSS rescore
  63. 2026-07-13 22:29 UTCEPSS rescore
  64. 2026-07-13 22:07 UTCOSV refresh
  65. 2026-07-13 06:12 UTCEPSS rescore
  66. 2026-07-12 05:45 UTCEPSS rescore
  67. 2026-07-12 05:45 UTCEPSS rescore
  68. 2026-07-11 08:26 UTCEPSS rescore
  69. 2026-07-09 19:09 UTCEPSS rescore
  70. 2026-07-09 19:09 UTCEPSS rescore
  71. 2026-07-08 15:14 UTCEPSS rescore
  72. 2026-07-07 13:45 UTCEPSS rescore
  73. 2026-07-06 16:26 UTCEPSS rescore
  74. 2026-07-06 02:22 UTCEPSS rescore
  75. 2026-07-05 02:29 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2024-50072?
CVE-2024-50072 is a medium vulnerability published on October 29, 2024. 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:…
When was CVE-2024-50072 disclosed?
CVE-2024-50072 was first published in the National Vulnerability Database on October 29, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-50072 actively exploited?
CVE-2024-50072 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.7% of all scored CVEs.
What is the CVSS score of CVE-2024-50072?
CVE-2024-50072 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-50072?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-50072, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-50072

Explore →

Is Your Infrastructure Affected by CVE-2024-50072?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs