# CVE-2024-51729: mm: use aligned address in copy_user_gigantic_page()

> An attacker can trigger memory corruption or information leaks in the Linux kernel by exploiting unaligned address handling in huge page copying.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 11 Jan 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-51729, DEBIAN-CVE-2024-51729, GHSA-8vm3-pfrg-f6xg, UBUNTU-CVE-2024-51729

## What is CVE-2024-51729?

CVE-2024-51729 is a high-severity memory corruption vulnerability in Linux kernel, published on 11 Jan 2025. 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: use aligned address in copy_user_gigantic_page()

In current kernel, hugetlb_wp() calls copy_user_large_folio() with the
fault address.  Where the fault address may be not aligned with the huge
page size.  Then, copy_user_large_folio() may call
copy_user_gigantic_page() with the address, while
copy_user_gigantic_page() requires the address to be huge page size
aligned.  So, this may cause memory corruption or information leak,
addtional, use more obvious naming 'addr_hint' instead of 'addr' for
copy_user_gigantic_page().

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-51729 being exploited?

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

What it is: CVE-2024-51729 is a high-severity memory corruption vulnerability in Linux kernel, published on 11 Jan 2025. 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-51729 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-51729/ (Markdown: https://insights.sbomify.com/CVE-2024-51729/index.md)
```

## Sources

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

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