<?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 04:25:00 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-57996</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-57996</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-57996</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>OESA-2025-1408 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1408</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;nfc: nci: add flush_workqueue to prevent uaf&lt;/p&gt;
&lt;p&gt;Our detector found a concurrent use-after-free bug when detaching an
NCI device. The main reason for this bug is the unexpected scheduling
between the used delayed mechanism (timer and workqueue).&lt;/p&gt;
&lt;p&gt;The race can be demonstrated below:&lt;/p&gt;
&lt;p&gt;Thread-1                           Thread-2
                                 | nci_dev_up()
                                 |   nci_open_device()
                                 |     __nci_request(nci_reset_req)
                                 |       nci_send_cmd
                                 |         queue_work(cmd_work)
nci_unregister_device()          |
  nci_close_device()             | ...
    del_timer_sync(cmd_timer)[1] |
...                              | Worker
nci_free_device()                | nci_cmd_work()
  kfree(ndev)[3]                 |   mod_timer(cmd_timer)[2]&lt;/p&gt;
&lt;p&gt;In short, the cleanup routine thought that the cmd_timer has already
been detached by [1] but the mod_timer can re-attach the timer [2], even
it is already released [3], resulting in UAF.&lt;/p&gt;
&lt;p&gt;This UAF is easy to trigger, crash trace by POC is like below&lt;/p&gt;
&lt;p&gt;[   66.703713] ==================================================================
[   66.703974] BUG: KASAN: use-after-free in enqueue_timer+0x448/0x490
[   66.703974] Write of size 8 at addr ffff888009fb7058 by task kworker/u4…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;nfc: nci: add flush_workqueue to prevent uaf&lt;/p&gt;
&lt;p&gt;Our detector found a concurrent use-after-free bug when detaching an
NCI device. The main reason for this bug is the unexpected scheduling
between the used delayed mechanism (timer and workqueue).&lt;/p&gt;
&lt;p&gt;The race can be demonstrated below:&lt;/p&gt;
&lt;p&gt;Thread-1                           Thread-2
                                 | nci_dev_up()
                                 |   nci_open_device()
                                 |     __nci_request(nci_reset_req)
                                 |       nci_send_cmd
                                 |         queue_work(cmd_work)
nci_unregister_device()          |
  nci_close_device()             | ...
    del_timer_sync(cmd_timer)[1] |
...                              | Worker
nci_free_device()                | nci_cmd_work()
  kfree(ndev)[3]                 |   mod_timer(cmd_timer)[2]&lt;/p&gt;
&lt;p&gt;In short, the cleanup routine thought that the cmd_timer has already
been detached by [1] but the mod_timer can re-attach the timer [2], even
it is already released [3], resulting in UAF.&lt;/p&gt;
&lt;p&gt;This UAF is easy to trigger, crash trace by POC is like below&lt;/p&gt;
&lt;p&gt;[   66.703713] ==================================================================
[   66.703974] BUG: KASAN: use-after-free in enqueue_timer+0x448/0x490
[   66.703974] Write of size 8 at addr ffff888009fb7058 by task kworker/u4…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1408</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-57996</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-57996</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net_sched: sch_sfq: don&amp;#39;t allow 1 packet limit The current implementation does not work correctly with a limit of 1. iproute2 actually checks for this and this patch adds the check in kernel as well. This fixes the following syzkaller reported crash: UBSAN: array-index-out-of-bounds in net/sched/sch_sfq.c:210:6 index 65535 is out of range for type &amp;#39;struct sfq_head[128]&amp;#39; CPU: 0 PID: 2569 Comm: syz-executor101 Not tainted 5.10.0-smp-DEV #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace:   __dump_stack lib/dump_stack.c:79 [inline]   dump_stack+0x125/0x19f lib/dump_stack.c:120   ubsan_epilogue lib/ubsan.c:148 [inline]   __ubsan_handle_out_of_bounds+0xed/0x120 lib/ubsan.c:347   sfq_link net/sched/sch_sfq.c:210 [inline]   sfq_dec+0x528/0x600 net/sched/sch_sfq.c:238   sfq_dequeue+0x39b/0x9d0 net/sched/sch_sfq.c:500   sfq_reset+0x13/0x50 net/sched/sch_sfq.c:525   qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026   tbf_reset+0x3d/0x100 net/sched/sch_tbf.c:319   qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026   dev_reset_queue+0x8c/0x140 net/sched/sch_generic.c:1296   netdev_for_each_tx_queue include/linux/netdevice.h:2350 [inline]   dev_deactivate_many+0x6dc/0xc20 net/sched/sch_generic.c:1362   __dev_close_many+0x214/0x350 net/core/dev.c:1468   dev_close_many+0x207/0x510 net/core/dev.c:1506   unregister_netdevice_many+0x40f/0x16b0 net/core/dev.c:10738   unre…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net_sched: sch_sfq: don&amp;#39;t allow 1 packet limit The current implementation does not work correctly with a limit of 1. iproute2 actually checks for this and this patch adds the check in kernel as well. This fixes the following syzkaller reported crash: UBSAN: array-index-out-of-bounds in net/sched/sch_sfq.c:210:6 index 65535 is out of range for type &amp;#39;struct sfq_head[128]&amp;#39; CPU: 0 PID: 2569 Comm: syz-executor101 Not tainted 5.10.0-smp-DEV #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace:   __dump_stack lib/dump_stack.c:79 [inline]   dump_stack+0x125/0x19f lib/dump_stack.c:120   ubsan_epilogue lib/ubsan.c:148 [inline]   __ubsan_handle_out_of_bounds+0xed/0x120 lib/ubsan.c:347   sfq_link net/sched/sch_sfq.c:210 [inline]   sfq_dec+0x528/0x600 net/sched/sch_sfq.c:238   sfq_dequeue+0x39b/0x9d0 net/sched/sch_sfq.c:500   sfq_reset+0x13/0x50 net/sched/sch_sfq.c:525   qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026   tbf_reset+0x3d/0x100 net/sched/sch_tbf.c:319   qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026   dev_reset_queue+0x8c/0x140 net/sched/sch_generic.c:1296   netdev_for_each_tx_queue include/linux/netdevice.h:2350 [inline]   dev_deactivate_many+0x6dc/0xc20 net/sched/sch_generic.c:1362   __dev_close_many+0x214/0x350 net/core/dev.c:1468   dev_close_many+0x207/0x510 net/core/dev.c:1506   unregister_netdevice_many+0x40f/0x16b0 net/core/dev.c:10738   unre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-57996</guid>
    </item>
  </channel>
</rss>
