CVE-2026-80913

selinux: require every boolean value to be defined

N/A
Published: September 4, 2026 at 05:19 PM UTC
Updated: September 4, 2026 at 06:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2662.6.12 ≤ v < 5.15.2172.6.12 ≤ v < 6.1.1842.6.12 ≤ v < 6.12.1052.6.12 ≤ v < 6.18.462.6.12 ≤ v < 6.6.1532.6.12 ≤ v < 7.1.102.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40 (fixed)
Vendor states this is fixed in 3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8 (fixed)
Vendor states this is fixed in 42a7107f99d86a7524c37f108047dfa3db096ab5 (fixed)
Vendor states this is fixed in 4d0ece18e648bd4362704fd087249ac697f2b7fb (fixed)
Vendor states this is fixed in 4dfb997c60f7951011d3dcbee926e3a7f80d8a76 (fixed)
Vendor states this is fixed in 740012aebdb8311332bf66e2aabf453ba73c2c45 (fixed)
Vendor states this is fixed in a93d37a09b863810653f93d371fb197457d59deb (fixed)
Vendor states this is fixed in ed901e88aa3fb3d5d7b0b52c2ee3073209df9bec (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card