CVE-2026-80913: selinux: require every boolean value to be defined
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40, 3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8, 42a7107f99d86a7524c37f108047dfa3db096ab5; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40, 3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8, 42a7107f99d86a7524c37f108047dfa3db096ab5; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4d0ece18e648bd4362704fd087249ac697f2b7fbaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4dfb997c60f7951011d3dcbee926e3a7f80d8a76affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 740012aebdb8311332bf66e2aabf453ba73c2c45affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 42a7107f99d86a7524c37f108047dfa3db096ab5affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ed901e88aa3fb3d5d7b0b52c2ee3073209df9becaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a93d37a09b863810653f93d371fb197457d59debaffected · git
- before 2.6.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.10-1 | 7.1.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80911Sep 4, 2026 · ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked()0Monitor
- ← EarlierCVE-2026-80912Sep 4, 2026 · selinux: reject an unclaimed class value in security_get_classes()0Monitor
- Later →CVE-2026-80758Sep 4, 2026 · futex: Avoid private hash use-after-free on final put0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3161daa3f1e3ca68f8b2b8fa01720b5a8dcc6b40 | Vendor (CNA) |
| Linux Linux | 3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8 | Vendor (CNA) |
| Linux Linux | 42a7107f99d86a7524c37f108047dfa3db096ab5 | Vendor (CNA) |
| Linux Linux | 4d0ece18e648bd4362704fd087249ac697f2b7fb | Vendor (CNA) |
| Linux Linux | 4dfb997c60f7951011d3dcbee926e3a7f80d8a76 | Vendor (CNA) |
| Linux Linux | 740012aebdb8311332bf66e2aabf453ba73c2c45 | Vendor (CNA) |
| Linux Linux | a93d37a09b863810653f93d371fb197457d59deb | Vendor (CNA) |
| Linux Linux | ed901e88aa3fb3d5d7b0b52c2ee3073209df9bec | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1015 · Sep 7, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3938c8494d3c5d84a53fd7d1966ae9dde46cb5f8
- git.kernel.org/stable/c/42a7107f99d86a7524c37f108047dfa3db096ab5
- git.kernel.org/stable/c/4d0ece18e648bd4362704fd087249ac697f2b7fb
- git.kernel.org/stable/c/4dfb997c60f7951011d3dcbee926e3a7f80d8a76
- git.kernel.org/stable/c/740012aebdb8311332bf66e2aabf453ba73c2c45
- git.kernel.org/stable/c/a93d37a09b863810653f93d371fb197457d59deb
- git.kernel.org/stable/c/ed901e88aa3fb3d5d7b0b52c2ee3073209df9bec
Vendor advisories and official records. Exploit/PoC links are deliberately left out.