<?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 08:29:15 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-35970</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-35970</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-2024-35970</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0611 — 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-2024-avi-0611</link>
      <description>certfr-2024-avi-0611</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0611</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35970</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35970</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: af_unix: Clear stale u-&amp;gt;oob_skb. syzkaller started to report deadlock of unix_gc_lock after commit 4090fa373f0e (&amp;#34;af_unix: Replace garbage collection algorithm.&amp;#34;), but it just uncovers the bug that has been there since commit 314001f0bf92 (&amp;#34;af_unix: Add OOB support&amp;#34;). The repro basically does the following.   from socket import *   from array import array   c1, c2 = socketpair(AF_UNIX, SOCK_STREAM)   c1.sendmsg([b&amp;#39;a&amp;#39;], [(SOL_SOCKET, SCM_RIGHTS, array(&amp;#34;i&amp;#34;, [c2.fileno()]))], MSG_OOB)   c2.recv(1)  # blocked as no normal data in recv queue   c2.close()  # done async and unblock recv()   c1.close()  # done async and trigger GC A socket sends its file descriptor to itself as OOB data and tries to receive normal data, but finally recv() fails due to async close(). The problem here is wrong handling of OOB skb in manage_oob().  When recvmsg() is called without MSG_OOB, manage_oob() is called to check if the peeked skb is OOB skb.  In such a case, manage_oob() pops it out of the receive queue but does not clear unix_sock(sk)-&amp;gt;oob_skb. This is wrong in terms of uAPI. Let&amp;#39;s say we send &amp;#34;hello&amp;#34; with MSG_OOB, and &amp;#34;world&amp;#34; without MSG_OOB. The &amp;#39;o&amp;#39; is handled as OOB data.  When recv() is called twice without MSG_OOB, the OOB data should be lost.   &amp;gt;&amp;gt;&amp;gt; from socket import *   &amp;gt;&amp;gt;&amp;gt; c1, c2 = socketpair(AF_UNIX, SOCK_STREAM, 0)   &amp;gt;&amp;gt;&amp;gt; c1.send(b&amp;#39;hello&amp;#39;, MSG_OOB)  # &amp;#39;o&amp;#39; is OOB data   5   &amp;gt;&amp;gt;&amp;gt; c1.send(b&amp;#39;world&amp;#39;)   5   &amp;gt;&amp;gt;&amp;gt; c2.recv(5)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: af_unix: Clear stale u-&amp;gt;oob_skb. syzkaller started to report deadlock of unix_gc_lock after commit 4090fa373f0e (&amp;#34;af_unix: Replace garbage collection algorithm.&amp;#34;), but it just uncovers the bug that has been there since commit 314001f0bf92 (&amp;#34;af_unix: Add OOB support&amp;#34;). The repro basically does the following.   from socket import *   from array import array   c1, c2 = socketpair(AF_UNIX, SOCK_STREAM)   c1.sendmsg([b&amp;#39;a&amp;#39;], [(SOL_SOCKET, SCM_RIGHTS, array(&amp;#34;i&amp;#34;, [c2.fileno()]))], MSG_OOB)   c2.recv(1)  # blocked as no normal data in recv queue   c2.close()  # done async and unblock recv()   c1.close()  # done async and trigger GC A socket sends its file descriptor to itself as OOB data and tries to receive normal data, but finally recv() fails due to async close(). The problem here is wrong handling of OOB skb in manage_oob().  When recvmsg() is called without MSG_OOB, manage_oob() is called to check if the peeked skb is OOB skb.  In such a case, manage_oob() pops it out of the receive queue but does not clear unix_sock(sk)-&amp;gt;oob_skb. This is wrong in terms of uAPI. Let&amp;#39;s say we send &amp;#34;hello&amp;#34; with MSG_OOB, and &amp;#34;world&amp;#34; without MSG_OOB. The &amp;#39;o&amp;#39; is handled as OOB data.  When recv() is called twice without MSG_OOB, the OOB data should be lost.   &amp;gt;&amp;gt;&amp;gt; from socket import *   &amp;gt;&amp;gt;&amp;gt; c1, c2 = socketpair(AF_UNIX, SOCK_STREAM, 0)   &amp;gt;&amp;gt;&amp;gt; c1.send(b&amp;#39;hello&amp;#39;, MSG_OOB)  # &amp;#39;o&amp;#39; is OOB data   5   &amp;gt;&amp;gt;&amp;gt; c1.send(b&amp;#39;world&amp;#39;)   5   &amp;gt;&amp;gt;&amp;gt; c2.recv(5)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35970</guid>
    </item>
  </channel>
</rss>
