data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-46302 in the interactive tracker

CVE-2026-46302

selinux: allow multiple opens of /sys/fs/selinux/policy

EPSS 0.1%

Published 2026-06-08 (4 months ago) by the Linux kernel CNA. Subsystem security/selinux. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-46302 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed7.0.7-1Update the kernel and reboot. Fixed in 7.0.7-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.0.7-1Update the kernel and reboot. Fixed in 7.0.7-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

security/selinux/selinuxfs.c

What this is
SELINUX SECURITY MODULEMAINTAINERS section matched on security/selinux/ · selinux@vger.kernel.org · Supported

Check it on the machine

grep -w CONFIG_SECURITY_SELINUX /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

  • bookwormy
  • trixieYnot built on armel/rpi
  • forky, sidy
y
built into the kernel image on every flavour - only a patch removes it
Y
built in where it is built at all; some flavours do not build it
Build switch
CONFIG_SECURITY_SELINUX

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-06-08 (4 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.10%, higher than 0.8% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
security/selinux

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
2.6.377.0.7714362f3779d
2.6.377.1a02cd6805562

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-46302, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.