CVE-2026-80913selinux: require every boolean value to be defined
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4d0ece18e648bd4362704fd087249ac697f2b7fb
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4dfb997c60f7951011d3dcbee926e3a7f80d8a76
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 740012aebdb8311332bf66e2aabf453ba73c2c45
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 42a7107f99d86a7524c37f108047dfa3db096ab5
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ed901e88aa3fb3d5d7b0b52c2ee3073209df9bec
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a93d37a09b863810653f93d371fb197457d59deb
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.266 – ≤ 5.10.*
- unaffected 5.15.217 – ≤ 5.15.*
- unaffected 6.1.184 – ≤ 6.1.*
- unaffected 6.6.153 – ≤ 6.6.*
- unaffected 6.12.105 – ≤ 6.12.*
- unaffected 6.18.46 – ≤ 6.18.*
- unaffected 7.1.10 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/4d0ece18e648bd4362704fd087249ac697f2b7fb (opens in a new tab)
- https://git.kernel.org/stable/c/3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8 (opens in a new tab)
- https://git.kernel.org/stable/c/4dfb997c60f7951011d3dcbee926e3a7f80d8a76 (opens in a new tab)
- https://git.kernel.org/stable/c/3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40 (opens in a new tab)
- https://git.kernel.org/stable/c/740012aebdb8311332bf66e2aabf453ba73c2c45 (opens in a new tab)
- https://git.kernel.org/stable/c/42a7107f99d86a7524c37f108047dfa3db096ab5 (opens in a new tab)
- https://git.kernel.org/stable/c/ed901e88aa3fb3d5d7b0b52c2ee3073209df9bec (opens in a new tab)
- https://git.kernel.org/stable/c/a93d37a09b863810653f93d371fb197457d59deb (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71616 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80913)Record last updated .