<?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:45:13 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38280</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38280</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-38280</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>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-38280</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38280</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 202 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Avoid __bpf_prog_ret0_warn when jit fails syzkaller reported an issue: WARNING: CPU: 3 PID: 217 at kernel/bpf/core.c:2357 __bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Modules linked in: CPU: 3 UID: 0 PID: 217 Comm: kworker/u32:6 Not tainted 6.15.0-rc4-syzkaller-00040-g8bac8898fe39 RIP: 0010:__bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Call Trace:  &amp;lt;TASK&amp;gt;  bpf_dispatcher_nop_func include/linux/bpf.h:1316 [inline]  __bpf_prog_run include/linux/filter.h:718 [inline]  bpf_prog_run include/linux/filter.h:725 [inline]  cls_bpf_classify+0x74a/0x1110 net/sched/cls_bpf.c:105  ... When creating bpf program, &amp;#39;fp-&amp;gt;jit_requested&amp;#39; depends on bpf_jit_enable. This issue is triggered because of CONFIG_BPF_JIT_ALWAYS_ON is not set and bpf_jit_enable is set to 1, causing the arch to attempt JIT the prog, but jit failed due to FAULT_INJECTION. As a result, incorrectly treats the program as valid, when the program runs it calls `__bpf_prog_ret0_warn` and triggers the WARN_ON_ONCE(1).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 202 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Avoid __bpf_prog_ret0_warn when jit fails syzkaller reported an issue: WARNING: CPU: 3 PID: 217 at kernel/bpf/core.c:2357 __bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Modules linked in: CPU: 3 UID: 0 PID: 217 Comm: kworker/u32:6 Not tainted 6.15.0-rc4-syzkaller-00040-g8bac8898fe39 RIP: 0010:__bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Call Trace:  &amp;lt;TASK&amp;gt;  bpf_dispatcher_nop_func include/linux/bpf.h:1316 [inline]  __bpf_prog_run include/linux/filter.h:718 [inline]  bpf_prog_run include/linux/filter.h:725 [inline]  cls_bpf_classify+0x74a/0x1110 net/sched/cls_bpf.c:105  ... When creating bpf program, &amp;#39;fp-&amp;gt;jit_requested&amp;#39; depends on bpf_jit_enable. This issue is triggered because of CONFIG_BPF_JIT_ALWAYS_ON is not set and bpf_jit_enable is set to 1, causing the arch to attempt JIT the prog, but jit failed due to FAULT_INJECTION. As a result, incorrectly treats the program as valid, when the program runs it calls `__bpf_prog_ret0_warn` and triggers the WARN_ON_ONCE(1).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38280</guid>
    </item>
  </channel>
</rss>
