CVE-2026-46302

Currently there can only be a single open of /sys/fs/selinux/policy at any time. This allows any process to block any other process from reading the kernel policy. The original motivation seems to have been a mix of preventing an inconsistent view of the policy size and preventing userspace from allocating kernel memory without bound, but this is arguably equally bad. Eliminate the policy_opened flag and shrink the critical section that the policy mutex is held. While we are making changes here, drop a couple of extraneous BUG_ONs.

Database specific

{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46302.json"
}

References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type: GIT
Repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events: Introduced

cee74f47a6baba0ac457e87687fdcf0abd599f0a

Fixed

d8cafd0226d5df682d1f4ea978a4318fe3a11210

Fixed

0ed712134a3db0075bfe9a0f8536c48728ec745e

Fixed

c24d2e190b955baf3a95e05d34b192f61bd201b3

Fixed

714362f3779dfa453a78ced32396a72726962a41

Fixed

a02cd6805562305f936e807da83e253b719dd965

Database specific

source

"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46302.json"

Linux / Kernel

Package

Name: Kernel

Affected ranges

Type: ECOSYSTEM
Events: Introduced

2.6.37

Fixed

6.6.160

Type: ECOSYSTEM
Events: Introduced

6.7.0

Fixed

6.12.114

Type: ECOSYSTEM
Events: Introduced

6.13.0

Fixed

6.18.58

Type: ECOSYSTEM
Events: Introduced

6.19.0

Fixed

7.0.7

Database specific

source

"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46302.json"