CVE Catalog

CVE-2026-80913

Low risk· EPSS 6%
Published: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.17%

6th percentile - higher than 6% of all known CVEs

Summary

In the Linux kernel, a vulnerability in SELinux has been fixed: every boolean value must be defined. The number of booleans (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 walks it by index and dereferences each entry, which can lead to issues. The fix rejects a boolean value that no boolean defines, once, where the array is built.

Risk Assessment

Undefined boolean values can lead to errors in SELinux operation, potentially weakening the security policy and allowing unauthorized access.

Recommendation

Update the Linux kernel to a version containing the fix and ensure SELinux policies are compliant.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS