# CVE-2026-80912: selinux: reject an unclaimed class value in security_get_classes()

> A null pointer dereference in the Linux kernel SELinux subsystem allows local attackers to cause a denial of service.

- **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:** 4 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** AZL-99443, BELL-CVE-2026-80912, DEBIAN-CVE-2026-80912, GHSA-5v22-vqg5-vrr8, UBUNTU-CVE-2026-80912

## What is CVE-2026-80912?

CVE-2026-80912 is a vulnerability in Linux, published on 4 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:

selinux: reject an unclaimed class value in security_get_classes()

security_get_classes() sizes an array by p_classes.nprim and fills it at
value - 1, so a class value the policy never defines leaves a NULL.
sel_make_classes() passes every entry to sel_make_dir(), reaching the same
d_alloc_name() dereference as the permission array. The class symbol table
is allowed to be sparse (policydb_class_isvalid() exists to absorb that),
but this getter builds its own array straight from the hash table and has
no such predicate.

Fail the lookup when a value went unclaimed instead of handing out the
NULL. Conforming policies define every class they declare and are
unaffected.

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


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

Apply the vendor's patch.

## Is CVE-2026-80912 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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