Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2024-50017

In the Linux kernel, the following vulnerability has been resolved: x86/mm/ident_map: Use gbpages…

Risk score
51/100
CVSS
5.5 v3.1
Exploit chance (30 days)
0.2%
Published
21 Oct 2024

Open in the live forecast Today's forecast

What to know

What it is
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 …
Affected
Linux kernel
Fix
Apply the vendor's security update; see the linked advisory.
Exploitation
No known exploitation

Story map

Story map: Linux kernelTHE FLAWSTHE FIXCVE-2024-50017In the Linux kernel, thefollowing vulnerability has beenresolved: x86/mm/ident_map…CVSS 5.5 · EPSS 0%CVE-2026-98096Out-of-bounds writeCVSS 7.4 · EPSS 1%CVE-2026-98115Race conditionCVSS 8.8 · EPSS 0%CVE-2026-98117Use-after-freeCVSS 7.8 · EPSS 0%FixApply the vendor's securityupdate; see the linked advisory.Who is exposedLinux kernelAMBER · PATCH THIS WEEKLinux kernelIn the Linux kernel, thefollowing vulnerability has beenresolved: ipv6: sr: restorenetwork header before routingand forwarding ipv6_srh_rcv()runs with skb->data at theSegment Routing Header (SRH)…Where it standsNo known exploitationHOW IT UNFOLDEDOfficial record on the left, the press on the right, oldest first.3 Nov · Ubuntu security noticesUSN-8962-1: Linux kernel (Azure CVM)vulnerabilities3 Nov · Ubuntu security noticesUSN-8963-1: Linux kernel (NVIDIA Tegra)vulnerabilities3 Nov · Ubuntu security noticesUSN-8961-1: Linux kernel vulnerabilitiesCONNECTS TOSame weaknessOut-of-bounds write (CWE-787)365 other warnings in 30 days →Same productEarlier Linux kernel warnings105 in the last 90 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

Linux kernel: Amber, patch this week. In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: restore network header before routing and forwarding ipv6_srh_rcv() runs with skb->data at the Segment Routing Header (SRH) while skb_network_header() points at the IPv6 header. When segments_left > 0, ipv6_srh_rcv() previously restored the …

The flaws

  • CVE-2024-50017: In the Linux kernel, the following vulnerability has been resolved: x86/mm/ident_map: Use gbpages… (CVSS 5.5 · EPSS 0%)
  • CVE-2026-98096: Out-of-bounds write (CVSS 7.4 · EPSS 1%)
  • CVE-2026-98115: Race condition (CVSS 8.8 · EPSS 0%)
  • CVE-2026-98117: Use-after-free (CVSS 7.8 · EPSS 0%)

The fix

Fix: Apply the vendor's security update; see the linked advisory.

Who is exposed: Linux kernel

Where it stands

  • No known exploitation

How it unfolded

  1. 3 Nov, Ubuntu security notices (official): USN-8962-1: Linux kernel (Azure CVM) vulnerabilities
  2. 3 Nov, Ubuntu security notices (official): USN-8963-1: Linux kernel (NVIDIA Tegra) vulnerabilities
  3. 3 Nov, Ubuntu security notices (official): USN-8961-1: Linux kernel vulnerabilities

Connects to

Why it is Yellow

  • CVSS 5.5 medium
  • On your watchlist: linux kernel
  • Named in a government or vendor bulletin

Government and vendor bulletins

References

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

Last activity 3 Nov 2026. Patch Forecast updates every hour.