<?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 02:24:43 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-40942</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-40942</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-40942</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — 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-2024-avi-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>OESA-2024-1944 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1944</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: musb: tusb6010: check return value after calling platform_get_resource()&#13;
&#13;
It will cause null-ptr-deref if platform_get_resource() returns NULL,
we need check the return value.(CVE-2021-47181)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: fix memory ordering between normal and ordered work functions&#13;
&#13;
Ordered work functions aren&amp;amp;apos;t guaranteed to be handled by the same thread
which executed the normal work functions. The only way execution between
normal/ordered functions is synchronized is via the WORK_DONE_BIT,
unfortunately the used bitops don&amp;amp;apos;t guarantee any ordering whatsoever.&#13;
&#13;
This manifested as seemingly inexplicable crashes on ARM64, where
async_chunk::inode is seen as non-null in async_cow_submit which causes
submit_compressed_extents to be called and crash occurs because
async_chunk::inode suddenly became NULL. The call trace was similar to:&#13;
&#13;
    pc : submit_compressed_extents+0x38/0x3d0
    lr : async_cow_submit+0x50/0xd0
    sp : ffff800015d4bc20&#13;
&#13;
    &amp;amp;lt;registers omitted for brevity&amp;amp;gt;&#13;
&#13;
    Call trace:
     submit_compressed_extents+0x38/0x3d0
     async_cow_submit+0x50/0xd0
     run_ordered_work+0xc8/0x280
     btrfs_work_helper+0x98/0x250
     process_one_work+0x1f0/0x4ac
     worker_thread+0x188/0x504
     kthread+0x110/0x114
     ret_from_fork+0x10/0x18…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: musb: tusb6010: check return value after calling platform_get_resource()&#13;
&#13;
It will cause null-ptr-deref if platform_get_resource() returns NULL,
we need check the return value.(CVE-2021-47181)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: fix memory ordering between normal and ordered work functions&#13;
&#13;
Ordered work functions aren&amp;amp;apos;t guaranteed to be handled by the same thread
which executed the normal work functions. The only way execution between
normal/ordered functions is synchronized is via the WORK_DONE_BIT,
unfortunately the used bitops don&amp;amp;apos;t guarantee any ordering whatsoever.&#13;
&#13;
This manifested as seemingly inexplicable crashes on ARM64, where
async_chunk::inode is seen as non-null in async_cow_submit which causes
submit_compressed_extents to be called and crash occurs because
async_chunk::inode suddenly became NULL. The call trace was similar to:&#13;
&#13;
    pc : submit_compressed_extents+0x38/0x3d0
    lr : async_cow_submit+0x50/0xd0
    sp : ffff800015d4bc20&#13;
&#13;
    &amp;amp;lt;registers omitted for brevity&amp;amp;gt;&#13;
&#13;
    Call trace:
     submit_compressed_extents+0x38/0x3d0
     async_cow_submit+0x50/0xd0
     run_ordered_work+0xc8/0x280
     btrfs_work_helper+0x98/0x250
     process_one_work+0x1f0/0x4ac
     worker_thread+0x188/0x504
     kthread+0x110/0x114
     ret_from_fork+0x10/0x18…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1944</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-40942</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40942</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 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned. Fix this by flushing all corresponding items of the preq_queue in mesh_path_flush_pending(). This should take care of KASAN reports like this: unreferenced object 0xffff00000668d800 (size 128):   comm &amp;#34;kworker/u8:4&amp;#34;, pid 67, jiffies 4295419552 (age 1836.444s)   hex dump (first 32 bytes):     00 1f 05 09 00 00 ff ff 00 d5 68 06 00 00 ff ff  ..........h.....     8e 97 ea eb 3e b8 01 00 00 00 00 00 00 00 00 00  ....&amp;gt;...........   backtrace:     [&amp;lt;000000007302a0b6&amp;gt;] __kmem_cache_alloc_node+0x1e0/0x35c     [&amp;lt;00000000049bd418&amp;gt;] kmalloc_trace+0x34/0x80     [&amp;lt;0000000000d792bb&amp;gt;] mesh_queue_preq+0x44/0x2a8     [&amp;lt;00000000c99c3696&amp;gt;] mesh_nexthop_resolve+0x198/0x19c     [&amp;lt;00000000926bf598&amp;gt;] ieee80211_xmit+0x1d0/0x1f4     [&amp;lt;00000000fc8c2284&amp;gt;] __ieee80211_subif_start_xmit+0x30c/0x764     [&amp;lt;000000005926ee38&amp;gt;] ieee80211_subif_start_xmit+0x9c/0x7a4     [&amp;lt;000000004c86e916&amp;gt;] dev_hard_start_xmit+0x174/0x440     [&amp;lt;0000000023495647&amp;gt;] __dev_queue_xmit+0xe24/0x111c     [&amp;lt;00000000cfe9ca78&amp;gt;] batadv_send_skb_packet+0x180/0x1e4     [&amp;lt;000000007bacc5d5&amp;gt;] batadv_v_elp_periodic_work+0x2f4/0x508     [&amp;lt;00000000adc3cd94&amp;gt;] process_one_work+0x4b8/0xa1c…&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 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned. Fix this by flushing all corresponding items of the preq_queue in mesh_path_flush_pending(). This should take care of KASAN reports like this: unreferenced object 0xffff00000668d800 (size 128):   comm &amp;#34;kworker/u8:4&amp;#34;, pid 67, jiffies 4295419552 (age 1836.444s)   hex dump (first 32 bytes):     00 1f 05 09 00 00 ff ff 00 d5 68 06 00 00 ff ff  ..........h.....     8e 97 ea eb 3e b8 01 00 00 00 00 00 00 00 00 00  ....&amp;gt;...........   backtrace:     [&amp;lt;000000007302a0b6&amp;gt;] __kmem_cache_alloc_node+0x1e0/0x35c     [&amp;lt;00000000049bd418&amp;gt;] kmalloc_trace+0x34/0x80     [&amp;lt;0000000000d792bb&amp;gt;] mesh_queue_preq+0x44/0x2a8     [&amp;lt;00000000c99c3696&amp;gt;] mesh_nexthop_resolve+0x198/0x19c     [&amp;lt;00000000926bf598&amp;gt;] ieee80211_xmit+0x1d0/0x1f4     [&amp;lt;00000000fc8c2284&amp;gt;] __ieee80211_subif_start_xmit+0x30c/0x764     [&amp;lt;000000005926ee38&amp;gt;] ieee80211_subif_start_xmit+0x9c/0x7a4     [&amp;lt;000000004c86e916&amp;gt;] dev_hard_start_xmit+0x174/0x440     [&amp;lt;0000000023495647&amp;gt;] __dev_queue_xmit+0xe24/0x111c     [&amp;lt;00000000cfe9ca78&amp;gt;] batadv_send_skb_packet+0x180/0x1e4     [&amp;lt;000000007bacc5d5&amp;gt;] batadv_v_elp_periodic_work+0x2f4/0x508     [&amp;lt;00000000adc3cd94&amp;gt;] process_one_work+0x4b8/0xa1c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-40942</guid>
    </item>
  </channel>
</rss>
