<?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 00:00:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21875</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21875</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-21875</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0333 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0333</link>
      <description>certfr-2025-avi-0333</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0333</guid>
    </item>
    <item>
      <title>OESA-2025-1869 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1869</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pfifo_tail_enqueue: Drop new packet when sch-&amp;amp;gt;limit == 0&lt;/p&gt;
&lt;p&gt;Expected behaviour:
In case we reach scheduler&amp;amp;apos;s limit, pfifo_tail_enqueue() will drop a
packet in scheduler&amp;amp;apos;s queue and decrease scheduler&amp;amp;apos;s qlen by one.
Then, pfifo_tail_enqueue() enqueue new packet and increase
scheduler&amp;amp;apos;s qlen by one. Finally, pfifo_tail_enqueue() return
`NET_XMIT_CN` status code.&lt;/p&gt;
&lt;p&gt;Weird behaviour:
In case we set `sch-&amp;amp;gt;limit == 0` and trigger pfifo_tail_enqueue() on a
scheduler that has no packet, the &amp;amp;apos;drop a packet&amp;amp;apos; step will do nothing.
This means the scheduler&amp;amp;apos;s qlen still has value equal 0.
Then, we continue to enqueue new packet and increase scheduler&amp;amp;apos;s qlen by
one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by
one and return `NET_XMIT_CN` status code.&lt;/p&gt;
&lt;p&gt;The problem is:
Let&amp;amp;apos;s say we have two qdiscs: Qdisc_A and Qdisc_B.
 - Qdisc_A&amp;amp;apos;s type must have &amp;amp;apos;-&amp;amp;gt;graft()&amp;amp;apos; function to create parent/child relationship.
   Let&amp;amp;apos;s say Qdisc_A&amp;amp;apos;s type is `hfsc`. Enqueue packet to this qdisc will trigger `hfsc_enqueue`.
 - Qdisc_B&amp;amp;apos;s type is pfifo_head_drop. Enqueue packet to this qdisc will trigger `pfifo_tail_enqueue`.
 - Qdisc_B is configured to have `sch-&amp;amp;gt;limit == 0`.
 - Qdisc_A is configured to route the enqueued&amp;amp;apos;s packet to Qdisc_B.&lt;/p&gt;
&lt;p&gt;Enqueue packet through…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pfifo_tail_enqueue: Drop new packet when sch-&amp;amp;gt;limit == 0&lt;/p&gt;
&lt;p&gt;Expected behaviour:
In case we reach scheduler&amp;amp;apos;s limit, pfifo_tail_enqueue() will drop a
packet in scheduler&amp;amp;apos;s queue and decrease scheduler&amp;amp;apos;s qlen by one.
Then, pfifo_tail_enqueue() enqueue new packet and increase
scheduler&amp;amp;apos;s qlen by one. Finally, pfifo_tail_enqueue() return
`NET_XMIT_CN` status code.&lt;/p&gt;
&lt;p&gt;Weird behaviour:
In case we set `sch-&amp;amp;gt;limit == 0` and trigger pfifo_tail_enqueue() on a
scheduler that has no packet, the &amp;amp;apos;drop a packet&amp;amp;apos; step will do nothing.
This means the scheduler&amp;amp;apos;s qlen still has value equal 0.
Then, we continue to enqueue new packet and increase scheduler&amp;amp;apos;s qlen by
one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by
one and return `NET_XMIT_CN` status code.&lt;/p&gt;
&lt;p&gt;The problem is:
Let&amp;amp;apos;s say we have two qdiscs: Qdisc_A and Qdisc_B.
 - Qdisc_A&amp;amp;apos;s type must have &amp;amp;apos;-&amp;amp;gt;graft()&amp;amp;apos; function to create parent/child relationship.
   Let&amp;amp;apos;s say Qdisc_A&amp;amp;apos;s type is `hfsc`. Enqueue packet to this qdisc will trigger `hfsc_enqueue`.
 - Qdisc_B&amp;amp;apos;s type is pfifo_head_drop. Enqueue packet to this qdisc will trigger `pfifo_tail_enqueue`.
 - Qdisc_B is configured to have `sch-&amp;amp;gt;limit == 0`.
 - Qdisc_A is configured to route the enqueued&amp;amp;apos;s packet to Qdisc_B.&lt;/p&gt;
&lt;p&gt;Enqueue packet through…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1869</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21875</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21875</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 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mptcp: always handle address removal under msk socket lock Syzkaller reported a lockdep splat in the PM control path:   WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 sock_owned_by_me include/net/sock.h:1711 [inline]   WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 msk_owned_by_me net/mptcp/protocol.h:363 [inline]   WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788   Modules linked in:   CPU: 0 UID: 0 PID: 6693 Comm: syz.0.205 Not tainted 6.14.0-rc2-syzkaller-00303-gad1b832bf1cf #0   Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024   RIP: 0010:sock_owned_by_me include/net/sock.h:1711 [inline]   RIP: 0010:msk_owned_by_me net/mptcp/protocol.h:363 [inline]   RIP: 0010:mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788   Code: 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 ca 7b d3 f5 eb b9 e8 c3 7b d3 f5 90 0f 0b 90 e9 dd fb ff ff e8 b5 7b d3 f5 90 &amp;lt;0f&amp;gt; 0b 90 e9 3e fb ff ff 44 89 f1 80 e1 07 38 c1 0f 8c eb fb ff ff   RSP: 0000:ffffc900034f6f60 EFLAGS: 00010283   RAX: ffffffff8bee3c2b RBX: 0000000000000001 RCX: 0000000000080000   RDX: ffffc90004d42000 RSI: 000000000000a407 RDI: 000000000000a408   RBP: ffffc900034f7030 R08: ffffffff8bee37f6 R09: 0100000000000000   R10: dffffc0000000000 R11: ffffed100bcc62e4 R12: ffff88805e6316e0   R13: ffff88805e630c00 R14: dffffc0000000000 R15: f…&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 148 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mptcp: always handle address removal under msk socket lock Syzkaller reported a lockdep splat in the PM control path:   WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 sock_owned_by_me include/net/sock.h:1711 [inline]   WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 msk_owned_by_me net/mptcp/protocol.h:363 [inline]   WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788   Modules linked in:   CPU: 0 UID: 0 PID: 6693 Comm: syz.0.205 Not tainted 6.14.0-rc2-syzkaller-00303-gad1b832bf1cf #0   Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024   RIP: 0010:sock_owned_by_me include/net/sock.h:1711 [inline]   RIP: 0010:msk_owned_by_me net/mptcp/protocol.h:363 [inline]   RIP: 0010:mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788   Code: 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 ca 7b d3 f5 eb b9 e8 c3 7b d3 f5 90 0f 0b 90 e9 dd fb ff ff e8 b5 7b d3 f5 90 &amp;lt;0f&amp;gt; 0b 90 e9 3e fb ff ff 44 89 f1 80 e1 07 38 c1 0f 8c eb fb ff ff   RSP: 0000:ffffc900034f6f60 EFLAGS: 00010283   RAX: ffffffff8bee3c2b RBX: 0000000000000001 RCX: 0000000000080000   RDX: ffffc90004d42000 RSI: 000000000000a407 RDI: 000000000000a408   RBP: ffffc900034f7030 R08: ffffffff8bee37f6 R09: 0100000000000000   R10: dffffc0000000000 R11: ffffed100bcc62e4 R12: ffff88805e6316e0   R13: ffff88805e630c00 R14: dffffc0000000000 R15: f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21875</guid>
    </item>
  </channel>
</rss>
