<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://127.0.0.1:10001</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 14:33:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53292</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53292</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-53292</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53292</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53292</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind syzbot reported a kernel BUG triggered from pn_socket_sendmsg() via pn_socket_autobind():   kernel BUG at net/phonet/socket.c:213!   RIP: 0010:pn_socket_autobind net/phonet/socket.c:213 [inline]   RIP: 0010:pn_socket_sendmsg+0x240/0x250 net/phonet/socket.c:421   Call Trace:    sock_sendmsg_nosec+0x112/0x150 net/socket.c:797    __sock_sendmsg net/socket.c:812 [inline]    __sys_sendto+0x402/0x590 net/socket.c:2280    ... pn_socket_autobind() calls pn_socket_bind() with port 0 and, on -EINVAL, assumes the socket was already bound and asserts that the port is non-zero:   err = pn_socket_bind(sock, ..., sizeof(struct sockaddr_pn));   if (err != -EINVAL)           return err;   BUG_ON(!pn_port(pn_sk(sock-&amp;gt;sk)-&amp;gt;sobject));   return 0; /* socket was already bound */ However pn_socket_bind() also returns -EINVAL when sk-&amp;gt;sk_state is not TCP_CLOSE, even when the socket has never been bound and pn_port() is still 0.  In that case the BUG_ON() fires and panics the kernel from a user-triggerable path. Treat the &amp;#34;bind returned -EINVAL but pn_port() is still 0&amp;#34; case as a regular error and propagate -EINVAL to the caller instead of crashing. Existing callers already translate a non-zero return from pn_socket_autobind() into -ENOBUFS/-EAGAIN, so returning -EINVAL here only changes behaviour from panic to a normal errno.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: phonet: do not BUG_ON() in pn_socket_autobind() on failed bind syzbot reported a kernel BUG triggered from pn_socket_sendmsg() via pn_socket_autobind():   kernel BUG at net/phonet/socket.c:213!   RIP: 0010:pn_socket_autobind net/phonet/socket.c:213 [inline]   RIP: 0010:pn_socket_sendmsg+0x240/0x250 net/phonet/socket.c:421   Call Trace:    sock_sendmsg_nosec+0x112/0x150 net/socket.c:797    __sock_sendmsg net/socket.c:812 [inline]    __sys_sendto+0x402/0x590 net/socket.c:2280    ... pn_socket_autobind() calls pn_socket_bind() with port 0 and, on -EINVAL, assumes the socket was already bound and asserts that the port is non-zero:   err = pn_socket_bind(sock, ..., sizeof(struct sockaddr_pn));   if (err != -EINVAL)           return err;   BUG_ON(!pn_port(pn_sk(sock-&amp;gt;sk)-&amp;gt;sobject));   return 0; /* socket was already bound */ However pn_socket_bind() also returns -EINVAL when sk-&amp;gt;sk_state is not TCP_CLOSE, even when the socket has never been bound and pn_port() is still 0.  In that case the BUG_ON() fires and panics the kernel from a user-triggerable path. Treat the &amp;#34;bind returned -EINVAL but pn_port() is still 0&amp;#34; case as a regular error and propagate -EINVAL to the caller instead of crashing. Existing callers already translate a non-zero return from pn_socket_autobind() into -ENOBUFS/-EAGAIN, so returning -EINVAL here only changes behaviour from panic to a normal errno.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53292</guid>
    </item>
  </channel>
</rss>
