# CVE-2024-50017: x86/mm/ident_map: Use gbpages only where full GB page should be mapped.

> A flaw in Linux kernel identity mapping allows processor speculation into reserved regions, potentially causing system halts on UV systems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Oct 2024
- **Updated:** 14 Sep 2026
- **Also known as:** AZL-51342, AZL-51497, BELL-CVE-2024-50017, DEBIAN-CVE-2024-50017, GHSA-h8wp-xf43-pm3w, ROOT-OS-DEBIAN-11-CVE-2024-50017, ROOT-OS-DEBIAN-12-CVE-2024-50017, ROOT-OS-UBUNTU-2204-CVE-2024-50017, UBUNTU-CVE-2024-50017

## What is CVE-2024-50017?

CVE-2024-50017 is a medium-severity denial of service vulnerability in Linux kernel, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2024-50017?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-50017?

Apply the vendor's patch.

## Is CVE-2024-50017 being exploited?

There is no known exploitation of CVE-2024-50017 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50017 and fix it if it is affected.

What it is: CVE-2024-50017 is a medium-severity denial of service vulnerability in Linux kernel, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50017 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50017/ (Markdown: https://insights.sbomify.com/CVE-2024-50017/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50017
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50017
- OSV: https://osv.dev/vulnerability/CVE-2024-50017

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50017/
Summaries are generated and may contain mistakes; the official description above is the record.