CVE-2024-50017None▾ SunlitIn 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Sep 14.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
5.5 → —
medium → none
0.2% → 0.2%
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.
Linux >= 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 < cb2555fb0223edac9e7820f16de17ae04a39ad39Linux >= 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 < fe9bab1d6441ed49dc3dd0acce4c2215e8d85447Linux >= 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 < d113f9723f2bfd9c6feeb899b8ddbee6b8a6e01fLinux >= 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 < d80a99892f7a992d103138fa4636b2c33abd6740Linux >= 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 < a23823098ab2c277c14fc110b97d8d5c83597195Linux >= 66aad4fdf2bf0af29c7decb4433dc5ec6c7c5451 < cc31744a294584a36bf764a0ffa3255a8e69f036Linux 4.12Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets