<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T22:42:17.872896+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-46104</id>
    <title>CVE-2026-46104 — selinux: use sk blob accessor in socket permission helpers</title>
    <updated>2026-10-04T22:42:17.875102+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-46104"/>
  </entry>
</feed>
