<?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>Fri, 20 Nov 2026 16:27:36 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38236</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38236</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-2025-38236</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38236</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38236</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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: af_unix: Don&amp;#39;t leave consecutive consumed OOB skbs. Jann Horn reported a use-after-free in unix_stream_read_generic(). The following sequences reproduce the issue:   $ python3   from socket import *   s1, s2 = socketpair(AF_UNIX, SOCK_STREAM)   s1.send(b&amp;#39;x&amp;#39;, MSG_OOB)   s2.recv(1, MSG_OOB)     # leave a consumed OOB skb   s1.send(b&amp;#39;y&amp;#39;, MSG_OOB)   s2.recv(1, MSG_OOB)     # leave a consumed OOB skb   s1.send(b&amp;#39;z&amp;#39;, MSG_OOB)   s2.recv(1)              # recv &amp;#39;z&amp;#39; illegally   s2.recv(1, MSG_OOB)     # access &amp;#39;z&amp;#39; skb (use-after-free) Even though a user reads OOB data, the skb holding the data stays on the recv queue to mark the OOB boundary and break the next recv(). After the last send() in the scenario above, the sk2&amp;#39;s recv queue has 2 leading consumed OOB skbs and 1 real OOB skb. Then, the following happens during the next recv() without MSG_OOB   1. unix_stream_read_generic() peeks the first consumed OOB skb   2. manage_oob() returns the next consumed OOB skb   3. unix_stream_read_generic() fetches the next not-yet-consumed OOB skb   4. unix_stream_read_generic() reads and frees the OOB skb , and the last recv(MSG_OOB) triggers KASAN splat. The 3. above occurs because of the SO_PEEK_OFF code, which does not expect unix_skb_len(skb) to be 0, but this is true for such consumed OOB skbs.   while (skip &amp;gt;= unix_skb_len(skb)) {     skip -= unix_skb_len(skb);     skb = skb_peek_next(skb, &amp;amp;sk-&amp;gt;sk_receive_queue);     ...…&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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: af_unix: Don&amp;#39;t leave consecutive consumed OOB skbs. Jann Horn reported a use-after-free in unix_stream_read_generic(). The following sequences reproduce the issue:   $ python3   from socket import *   s1, s2 = socketpair(AF_UNIX, SOCK_STREAM)   s1.send(b&amp;#39;x&amp;#39;, MSG_OOB)   s2.recv(1, MSG_OOB)     # leave a consumed OOB skb   s1.send(b&amp;#39;y&amp;#39;, MSG_OOB)   s2.recv(1, MSG_OOB)     # leave a consumed OOB skb   s1.send(b&amp;#39;z&amp;#39;, MSG_OOB)   s2.recv(1)              # recv &amp;#39;z&amp;#39; illegally   s2.recv(1, MSG_OOB)     # access &amp;#39;z&amp;#39; skb (use-after-free) Even though a user reads OOB data, the skb holding the data stays on the recv queue to mark the OOB boundary and break the next recv(). After the last send() in the scenario above, the sk2&amp;#39;s recv queue has 2 leading consumed OOB skbs and 1 real OOB skb. Then, the following happens during the next recv() without MSG_OOB   1. unix_stream_read_generic() peeks the first consumed OOB skb   2. manage_oob() returns the next consumed OOB skb   3. unix_stream_read_generic() fetches the next not-yet-consumed OOB skb   4. unix_stream_read_generic() reads and frees the OOB skb , and the last recv(MSG_OOB) triggers KASAN splat. The 3. above occurs because of the SO_PEEK_OFF code, which does not expect unix_skb_len(skb) to be 0, but this is true for such consumed OOB skbs.   while (skip &amp;gt;= unix_skb_len(skb)) {     skip -= unix_skb_len(skb);     skb = skb_peek_next(skb, &amp;amp;sk-&amp;gt;sk_receive_queue);     ...…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38236</guid>
    </item>
  </channel>
</rss>
