CVE-2026-80913 json
selinux: require every boolean value to be defined
published 2026-09-04 2 mo ago modified 2026-11-06 2 d ago also EUVD-2026-71616
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.105-1
- linux Debian 14 7.1.10-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-80913
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-80913
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/4d0ece18e648bd4362704fd087249ac697f2b7fb commit
- git.kernel.org/stable/c/3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8 commit
- git.kernel.org/stable/c/4dfb997c60f7951011d3dcbee926e3a7f80d8a76 commit
- git.kernel.org/stable/c/3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40 commit
- git.kernel.org/stable/c/740012aebdb8311332bf66e2aabf453ba73c2c45 commit
- git.kernel.org/stable/c/42a7107f99d86a7524c37f108047dfa3db096ab5 commit
- git.kernel.org/stable/c/ed901e88aa3fb3d5d7b0b52c2ee3073209df9bec commit
- git.kernel.org/stable/c/a93d37a09b863810653f93d371fb197457d59deb commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80913 updated cvss 5.5
kernel: selinux: require every boolean value to be defined
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/4d0ece18e648bd4362704fd087249ac697f2b7fb
- git.kernel.org /stable/c/3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8
- git.kernel.org /stable/c/4dfb997c60f7951011d3dcbee926e3a7f80d8a76
- git.kernel.org /stable/c/3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40
- git.kernel.org /stable/c/740012aebdb8311332bf66e2aabf453ba73c2c45
- git.kernel.org /stable/c/42a7107f99d86a7524c37f108047dfa3db096ab5
- git.kernel.org /stable/c/ed901e88aa3fb3d5d7b0b52c2ee3073209df9bec
- git.kernel.org /stable/c/a93d37a09b863810653f93d371fb197457d59deb
Sources
- CVE List CVE-2026-80913
- NVD CVE-2026-80913
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.