CVE-2026-46302: Linux kernel · selinux: allow multiple opens of /sys/fs/selinux/policy
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d8cafd0226d5df682d1f4ea978a4318fe3a11210 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d8cafd0226d5df682d1f4ea978a4318fe3a11210, c24d2e190b955baf3a95e05d34b192f61bd201b3, a02cd6805562305f936e807da83e253b719dd965 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: selinux: allow multiple opens of /sys/fs/selinux/policy 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.
References
- git.kernel.org/stable/c/d8cafd0226d5df682d1f4ea978a4318fe3a11210 (opens in a new tab)
- git.kernel.org/stable/c/0ed712134a3db0075bfe9a0f8536c48728ec745e (opens in a new tab)
- git.kernel.org/stable/c/c24d2e190b955baf3a95e05d34b192f61bd201b3 (opens in a new tab)
- git.kernel.org/stable/c/714362f3779dfa453a78ced32396a72726962a41 (opens in a new tab)
- git.kernel.org/stable/c/a02cd6805562305f936e807da83e253b719dd965 (opens in a new tab)