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

Published Sep 4, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

selinux: require every boolean value to be defined

pbools.nprim comes from the policy image independently of how many booleans follow it, and condindexbool() fills boolvaltostruct[] 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: condevaluateexpr() on the access-vector path, securitygetbools() and securitygetboolvalue() behind selinuxfs, and securitysetbools(). A sparse class value is absorbed by policydbclassisvalid() 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 Software

1 affected component
The Linux Kernel Project Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update/align SELinux policy handling so that every boolean value encountered is rejected unless it is defined (i.e., ensure no undefined boolean values are accepted during cond_evaluate_expr() evaluation on the access-vector path).

    SELinux require every boolean value to be defined = true

Event History

Sep 4, 2026
CVE Published
via MITRE·05:19 PM
Data Sourced
via MITRE·05:19 PM
Description

Frequently Asked Questions

1

What policy condition is required to trigger the issue?

The loaded SELinux policy must declare more boolean values in p_bools.nprim than are actually defined. This leaves NULL entries in the boolean value lookup array.

2

Which kernel paths can dereference the missing boolean entries?

The access-vector path can reach them through cond_evaluate_expr(). SELinux filesystem operations using security_get_bools(), security_get_bool_value(), or security_set_bools() can also dereference the entries.

3

Are normal SELinux policies affected?

Conforming policies that define every boolean they declare are unaffected. The fix rejects a boolean value that has no corresponding boolean definition while building the array.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203