# CVE-2026-80913: selinux: require every boolean value to be defined

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

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** AZL-99455, BELL-CVE-2026-80913, DEBIAN-CVE-2026-80913, GHSA-97qf-47rv-vfvf, UBUNTU-CVE-2026-80913

## What is CVE-2026-80913?

CVE-2026-80913 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: require every boolean value to be defined

p_bools.nprim comes from the policy image independently of how many
booleans follow it, and cond_index_bool() fills bool_val_to_struct[] at
value - 1, so a count larger than the values present leaves NULL entries.
Every user of that array then walks it by index and dereferences each
entry: cond_evaluate_expr() on the access-vector path,
security_get_bools() and security_get_bool_value() behind selinuxfs, and
security_set_bools(). A sparse class value is absorbed by
policydb_class_isvalid() and its siblings; booleans have no such
predicate, and no consumer that could use one.

Reject a boolean value that no boolean defines, once, where the array is
built. Conforming policies define every boolean they declare and are
unaffected.

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


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

Apply the vendor's patch.

## Is CVE-2026-80913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80913 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-80913 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-80913/ (Markdown: https://insights.sbomify.com/CVE-2026-80913/index.md)
```

## Sources

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

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