<?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:41:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-57946</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-57946</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-57946</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0133 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0133</link>
      <description>certfr-2025-avi-0133</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0133</guid>
    </item>
    <item>
      <title>OESA-2025-1204 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1204</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;bpf: Prevent tailcall infinite loop caused by freplace&lt;/p&gt;
&lt;p&gt;There is a potential infinite loop issue that can occur when using a
combination of tail calls and freplace.&lt;/p&gt;
&lt;p&gt;In an upcoming selftest, the attach target for entry_freplace of
tailcall_freplace.c is subprog_tc of tc_bpf2bpf.c, while the tail call in
entry_freplace leads to entry_tc. This results in an infinite loop:&lt;/p&gt;
&lt;p&gt;entry_tc -&amp;amp;gt; subprog_tc -&amp;amp;gt; entry_freplace --tailcall-&amp;amp;gt; entry_tc.&lt;/p&gt;
&lt;p&gt;The problem arises because the tail_call_cnt in entry_freplace resets to
zero each time entry_freplace is executed, causing the tail call mechanism
to never terminate, eventually leading to a kernel panic.&lt;/p&gt;
&lt;p&gt;To fix this issue, the solution is twofold:&lt;/p&gt;
&lt;p&gt;1. Prevent updating a program extended by an freplace program to a
   prog_array map.
2. Prevent extending a program that is already part of a prog_array map
   with an freplace program.&lt;/p&gt;
&lt;p&gt;This ensures that:&lt;/p&gt;
&lt;p&gt;* If a program or its subprogram has been extended by an freplace program,
  it can no longer be updated to a prog_array map.
* If a program has been added to a prog_array map, neither it nor its
  subprograms can be extended by an freplace program.&lt;/p&gt;
&lt;p&gt;Moreover, an extension program should not be tailcalled. As such, return
-EINVAL if the program has a type of BPF_PROG_TYPE_EXT when adding it to a
prog_array map.&lt;/p&gt;
&lt;p&gt;Additionally, fix a minor code s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;bpf: Prevent tailcall infinite loop caused by freplace&lt;/p&gt;
&lt;p&gt;There is a potential infinite loop issue that can occur when using a
combination of tail calls and freplace.&lt;/p&gt;
&lt;p&gt;In an upcoming selftest, the attach target for entry_freplace of
tailcall_freplace.c is subprog_tc of tc_bpf2bpf.c, while the tail call in
entry_freplace leads to entry_tc. This results in an infinite loop:&lt;/p&gt;
&lt;p&gt;entry_tc -&amp;amp;gt; subprog_tc -&amp;amp;gt; entry_freplace --tailcall-&amp;amp;gt; entry_tc.&lt;/p&gt;
&lt;p&gt;The problem arises because the tail_call_cnt in entry_freplace resets to
zero each time entry_freplace is executed, causing the tail call mechanism
to never terminate, eventually leading to a kernel panic.&lt;/p&gt;
&lt;p&gt;To fix this issue, the solution is twofold:&lt;/p&gt;
&lt;p&gt;1. Prevent updating a program extended by an freplace program to a
   prog_array map.
2. Prevent extending a program that is already part of a prog_array map
   with an freplace program.&lt;/p&gt;
&lt;p&gt;This ensures that:&lt;/p&gt;
&lt;p&gt;* If a program or its subprogram has been extended by an freplace program,
  it can no longer be updated to a prog_array map.
* If a program has been added to a prog_array map, neither it nor its
  subprograms can be extended by an freplace program.&lt;/p&gt;
&lt;p&gt;Moreover, an extension program should not be tailcalled. As such, return
-EINVAL if the program has a type of BPF_PROG_TYPE_EXT when adding it to a
prog_array map.&lt;/p&gt;
&lt;p&gt;Additionally, fix a minor code s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1204</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-57946</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-57946</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio-blk: don&amp;#39;t keep queue frozen during system suspend Commit 4ce6e2db00de (&amp;#34;virtio-blk: Ensure no requests in virtqueues before deleting vqs.&amp;#34;) replaces queue quiesce with queue freeze in virtio-blk&amp;#39;s PM callbacks. And the motivation is to drain inflight IOs before suspending. block layer&amp;#39;s queue freeze looks very handy, but it is also easy to cause deadlock, such as, any attempt to call into bio_queue_enter() may run into deadlock if the queue is frozen in current context. There are all kinds of -&amp;gt;suspend() called in suspend context, so keeping queue frozen in the whole suspend context isn&amp;#39;t one good idea. And Marek reported lockdep warning[1] caused by virtio-blk&amp;#39;s freeze queue in virtblk_freeze(). [1] https://lore.kernel.org/linux-block/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/ Given the motivation is to drain in-flight IOs, it can be done by calling freeze &amp;amp; unfreeze, meantime restore to previous behavior by keeping queue quiesced during suspend.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio-blk: don&amp;#39;t keep queue frozen during system suspend Commit 4ce6e2db00de (&amp;#34;virtio-blk: Ensure no requests in virtqueues before deleting vqs.&amp;#34;) replaces queue quiesce with queue freeze in virtio-blk&amp;#39;s PM callbacks. And the motivation is to drain inflight IOs before suspending. block layer&amp;#39;s queue freeze looks very handy, but it is also easy to cause deadlock, such as, any attempt to call into bio_queue_enter() may run into deadlock if the queue is frozen in current context. There are all kinds of -&amp;gt;suspend() called in suspend context, so keeping queue frozen in the whole suspend context isn&amp;#39;t one good idea. And Marek reported lockdep warning[1] caused by virtio-blk&amp;#39;s freeze queue in virtblk_freeze(). [1] https://lore.kernel.org/linux-block/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/ Given the motivation is to drain in-flight IOs, it can be done by calling freeze &amp;amp; unfreeze, meantime restore to previous behavior by keeping queue quiesced during suspend.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-57946</guid>
    </item>
  </channel>
</rss>
