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

Published Oct 29, 2024
·
Updated

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: restoreallswitchstack+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: showregs+0x70/0x78 dieaddr+0x29/0x70 excgeneralprotection+0x13c/0x348 excbounds+0x98/0x98 handleexception+0x14d/0x14d excbounds+0x98/0x98 restoreallswitchstack+0xbe/0xcf excbounds+0x98/0x98 restoreallswitchstack+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.

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

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

16 affected componentsFixes available
Linux Linux kernel>=5.10.215<5.11
Linux Linux kernel>=5.15.154<5.16
Linux Linux kernel>=6.1.81<6.2
Linux Linux kernel>=6.6.21<6.6.58
Linux Linux kernel>=6.7<6.11.5
Linux Linux kernel>=6.7.9<6.8
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
Linux Linux kernel=6.12-rc3
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.180.1-1
Microsoft cbl2 kernel 5.15.180.1-1
Microsoft azl3 kernel 6.6.64.2-1
Microsoft azl3 kernel 6.6.57.1-7
Microsoft cbl2 kernel 5.15.176.3-1

Event History

Oct 29, 2024
CVE Published
via MITRE·12:50 AM
Data Sourced
via MITRE·12:50 AM
Description
Data Sourced
via NVD·01:15 AM
RemedyDescriptionSeverityAffected Software
Jan 29, 2025
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Description
Updated
via Microsoft·08:00 AM
DescriptionSeverity
Feb 24, 2025
Data Sourced
via Launchpad·12:45 AM
Description
May 3, 2025
Data Sourced
via Ubuntu·12:55 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-50072?

The severity of CVE-2024-50072 is classified as high due to potential system crashes causing disruption.

2

How do I fix CVE-2024-50072?

To fix CVE-2024-50072, it is recommended to update the Linux kernel to a version that is not affected by this vulnerability.

3

Which versions of the Linux kernel are affected by CVE-2024-50072?

CVE-2024-50072 affects Linux kernel versions from 5.10.215 to 5.11, from 5.15.154 to 5.16, from 6.1.81 to 6.2, from 6.6.21 to 6.6.58, and from 6.7 to 6.11.5.

4

What does CVE-2024-50072 impact?

CVE-2024-50072 impacts the stability of the Linux kernel, specifically leading to general protection faults in 32-bit mode during execution of VM86 system calls.

5

Who reported CVE-2024-50072?

CVE-2024-50072 was reported by Robert Gill.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203