CVE-2024-50017

x86/mm/ident_map: Use gbpages only where full GB page should be mapped.

MEDIUM
5.5
CVSS Score
Published: October 21, 2024 at 06:54 PM UTC
Updated: September 14, 2026 at 12:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: x86/mm/ident_map: Use gbpages only where full GB page should be mapped. When ident_pud_init() uses only GB pages to create identity maps, large ranges of addresses not actually requested can be included in the resulting table; a 4K request will map a full GB. This can include a lot of extra address space past that requested, including areas marked reserved by the BIOS. That allows processor speculation into reserved regions, that on UV systems can cause system halts. Only use GB pages when map creation requests include the full GB page of space. Fall back to using smaller 2M pages when only portions of a GB page are included in the request. No attempt is made to coalesce mapping requests. If a request requires a map entry at the 2M (pmd) level, subsequent mapping requests within the same 1G region will also be at the pmd level, even if adjacent or overlapping such requests could have been combined to map a full GB page. Existing usage starts with larger regions and then adds smaller regions, so this should not have any great consequence.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.10.144.12 ≤ v < 5.15.2214.12 ≤ v < 6.1.1884.12 ≤ v < 6.10.144.12 ≤ v < 6.11.34.12 ≤ v < 6.124.12 ≤ v < 6.6.786.11 ≤ v < 6.11.34.1266aad4fdf2bf0af29c7decb4433dc5ec6c7c5451
Vendor states this is fixed in a23823098ab2c277c14fc110b97d8d5c83597195 (fixed)
Vendor states this is fixed in cb2555fb0223edac9e7820f16de17ae04a39ad39 (fixed)
Vendor states this is fixed in cc31744a294584a36bf764a0ffa3255a8e69f036 (fixed)
Vendor states this is fixed in d113f9723f2bfd9c6feeb899b8ddbee6b8a6e01f (fixed)
Vendor states this is fixed in d80a99892f7a992d103138fa4636b2c33abd6740 (fixed)
Vendor states this is fixed in fe9bab1d6441ed49dc3dd0acce4c2215e8d85447 (fixed)
Vendor states this is fixed in 4.12 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.10.14 (unaffected)
Vendor states this is fixed in 6.11.3 (unaffected)
Vendor states this is fixed in 6.12 (unaffected)
Vendor states this is fixed in 6.6.78 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card