<?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-09-30T03:44:19.640605+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-52928</id>
    <title>CVE-2026-52928 — af_unix: Reject SIOCATMARK on non-stream sockets</title>
    <updated>2026-09-30T03:44:19.641821+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>af_unix: Reject SIOCATMARK on non-stream sockets</p>
<p>SIOCATMARK reports whether the receive queue is at the urgent mark for
MSG_OOB.</p>
<p>In AF_UNIX, MSG_OOB is supported only for SOCK_STREAM sockets.
SOCK_DGRAM and SOCK_SEQPACKET reject MSG_OOB in sendmsg() and recvmsg(),
so they should not support SIOCATMARK either.</p>
<p>Return -EOPNOTSUPP for non-stream sockets before checking the receive
queue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-52928"/>
  </entry>
</feed>
