# CVE-2026-98506: mm/hugetlb: do not dissolve gigantic pages without runtime support

> A local attacker can corrupt the hugetlb free list by dissolving gigantic pages without runtime support, potentially causing a system crash or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109293, BELL-CVE-2026-98506, DEBIAN-CVE-2026-98506, GHSA-rgpg-w634-4pfv, UBUNTU-CVE-2026-98506

## What is CVE-2026-98506?

CVE-2026-98506 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. 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/hugetlb: do not dissolve gigantic pages without runtime support

dissolve_free_hugetlb_folio() doesn't check
hstate_is_gigantic_no_runtime(h) though remove_hugetlb_folio()/
update_and_free_hugetlb_folio() silently bail for such folios, so it frees
a still-listed folio and, on vmemmap restore failure, the
add_hugetlb_folio() rollback corrupts the free list.

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


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

Apply the vendor's patch.

## Is CVE-2026-98506 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98506 and fix it if it is affected.

What it is: CVE-2026-98506 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. 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-2026-98506 in the wild and no public exploit code.

Affected product: Linux. 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-2026-98506/ (Markdown: https://insights.sbomify.com/CVE-2026-98506/index.md)
```

## Sources

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

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