# CVE-2024-42258: mm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines

> A logic error in huge page alignment on 32-bit Linux kernels can lead to resource exhaustion and denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 12 Aug 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-42258, DEBIAN-CVE-2024-42258, GHSA-762q-jqwq-g847, UBUNTU-CVE-2024-42258

## What is CVE-2024-42258?

CVE-2024-42258 is a high-severity denial of service vulnerability in Linux kernel, published on 12 Aug 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:

mm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines

Yves-Alexis Perez reported commit 4ef9ad19e176 ("mm: huge_memory: don't
force huge page alignment on 32 bit") didn't work for x86_32 [1].  It is
because x86_32 uses CONFIG_X86_32 instead of CONFIG_32BIT.

!CONFIG_64BIT should cover all 32 bit machines.

[1] https://lore.kernel.org/linux-mm/CAHbLzkr1LwH3pcTgM+aGQ31ip2bKqiqEQ8=FQB+t2c3dhNKNHA@mail.gmail.com/

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-42258 being exploited?

There is no known exploitation of CVE-2024-42258 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-42258 and fix it if it is affected.

What it is: CVE-2024-42258 is a high-severity denial of service vulnerability in Linux kernel, published on 12 Aug 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-42258 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-42258/ (Markdown: https://insights.sbomify.com/CVE-2024-42258/index.md)
```

## Sources

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

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