https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 22:42:17 +0000 https://vulnerability.circl.lu/vuln/cve-2026-46104 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>selinux: use sk blob accessor in socket permission helpers</p> <p>SELinux socket state lives in the composite LSM socket blob.</p> <p>sock_has_perm() and nlmsg_sock_has_extended_perms() currently dereference sk-&gt;sk_security directly, which assumes the SELinux socket blob is at offset zero.</p> <p>In stacked configurations that assumption does not hold. If another LSM allocates socket blob storage before SELinux, these helpers may read the wrong blob and feed invalid SID and class values into AVC checks.</p> <p>Use selinux_sock() instead of accessing sk-&gt;sk_security directly.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>selinux: use sk blob accessor in socket permission helpers</p> <p>SELinux socket state lives in the composite LSM socket blob.</p> <p>sock_has_perm() and nlmsg_sock_has_extended_perms() currently dereference sk-&gt;sk_security directly, which assumes the SELinux socket blob is at offset zero.</p> <p>In stacked configurations that assumption does not hold. If another LSM allocates socket blob storage before SELinux, these helpers may read the wrong blob and feed invalid SID and class values into AVC checks.</p> <p>Use selinux_sock() instead of accessing sk-&gt;sk_security directly.</p> https://vulnerability.circl.lu/vuln/cve-2026-46104