# CVE-2026-90283: hugetlbfs: release subpool on fill_super failure

> A local attacker can cause a memory leak and potential denial of service by triggering a failure during hugetlbfs mount with specific options.

- **Severity:** Not scored
- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102600, BELL-CVE-2026-90283, DEBIAN-CVE-2026-90283, GHSA-j4hm-6c8x-4hfr, UBUNTU-CVE-2026-90283

## What is CVE-2026-90283?

CVE-2026-90283 is a memory corruption vulnerability in Linux, published on 17 Sep 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:

hugetlbfs: release subpool on fill_super failure

hugetlbfs_fill_super() allocates a hugepage subpool when size or min_size
mount options are specified.  hugepage_new_subpool() may also reserve huge
pages for min_size.

If root dentry creation fails after the subpool is created, the failure
path frees the subpool with kfree().  This bypasses hugepage_put_subpool()
and can leave min_size reservations charged.

Use hugepage_put_subpool() on the failure path, matching the normal
put_super path.

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


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

Apply the vendor's patch.

## Is CVE-2026-90283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90283 is a memory corruption vulnerability in Linux, published on 17 Sep 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-90283 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-90283/ (Markdown: https://insights.sbomify.com/CVE-2026-90283/index.md)
```

## Sources

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

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