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.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
>= 2.6.37, < 7.0.7CPE matchmatch criteria | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | ||
7.1CPE matchmatch criteria | cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | ||
7.1CPE matchmatch criteria | cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
No social media mentions found for this CVE.
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.0 Bluesky, 0.0 Mastodon, and 0.1 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Linux kernel (Azure) vulnerabilities
Jul 24, 2026Linux kernel vulnerabilities
Jul 23, 2026Linux kernel (HWE) vulnerabilities
Jul 20, 2026Linux kernel (OEM) vulnerabilities
Jul 20, 2026Linux kernel vulnerabilities
Jul 20, 2026selinux: allow multiple opens of /sys/fs/selinux/policy
Jun 9, 2026