<?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 06:41:16 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-44958</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-44958</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-44958</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0997 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0997</link>
      <description>certfr-2024-avi-0997</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0997</guid>
    </item>
    <item>
      <title>OESA-2024-2216 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2216</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;
ALSA: usb-audio: Stop parsing channels bits when all channels are found.&#13;
&#13;
If a usb audio device sets more bits than the amount of channels
it could write outside of the map array.(CVE-2024-27436)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete&#13;
&#13;
FFS based applications can utilize the aio_cancel() callback to dequeue
pending USB requests submitted to the UDC.  There is a scenario where the
FFS application issues an AIO cancel call, while the UDC is handling a
soft disconnect.  For a DWC3 based implementation, the callstack looks
like the following:&#13;
&#13;
    DWC3 Gadget                               FFS Application
dwc3_gadget_soft_disconnect()              ...
  --&amp;amp;gt; dwc3_stop_active_transfers()
    --&amp;amp;gt; dwc3_gadget_giveback(-ESHUTDOWN)
      --&amp;amp;gt; ffs_epfile_async_io_complete()   ffs_aio_cancel()
        --&amp;amp;gt; usb_ep_free_request()            --&amp;amp;gt; usb_ep_dequeue()&#13;
&#13;
There is currently no locking implemented between the AIO completion
handler and AIO cancel, so the issue occurs if the completion routine is
running in parallel to an AIO cancel call coming from the FFS application.
As the completion call frees the USB request (io_data-&amp;amp;gt;req) the FFS
application is also referencing it for the usb_ep_dequeue() call.  This can…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;
ALSA: usb-audio: Stop parsing channels bits when all channels are found.&#13;
&#13;
If a usb audio device sets more bits than the amount of channels
it could write outside of the map array.(CVE-2024-27436)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete&#13;
&#13;
FFS based applications can utilize the aio_cancel() callback to dequeue
pending USB requests submitted to the UDC.  There is a scenario where the
FFS application issues an AIO cancel call, while the UDC is handling a
soft disconnect.  For a DWC3 based implementation, the callstack looks
like the following:&#13;
&#13;
    DWC3 Gadget                               FFS Application
dwc3_gadget_soft_disconnect()              ...
  --&amp;amp;gt; dwc3_stop_active_transfers()
    --&amp;amp;gt; dwc3_gadget_giveback(-ESHUTDOWN)
      --&amp;amp;gt; ffs_epfile_async_io_complete()   ffs_aio_cancel()
        --&amp;amp;gt; usb_ep_free_request()            --&amp;amp;gt; usb_ep_dequeue()&#13;
&#13;
There is currently no locking implemented between the AIO completion
handler and AIO cancel, so the issue occurs if the completion routine is
running in parallel to an AIO cancel call coming from the FFS application.
As the completion call frees the USB request (io_data-&amp;amp;gt;req) the FFS
application is also referencing it for the usb_ep_dequeue() call.  This can…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2216</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-44958</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-44958</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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/smt: Fix unbalance sched_smt_present dec/inc I got the following warn report while doing stress test: jump label: negative count! WARNING: CPU: 3 PID: 38 at kernel/jump_label.c:263 static_key_slow_try_dec+0x9d/0xb0 Call Trace:  &amp;lt;TASK&amp;gt;  __static_key_slow_dec_cpuslocked+0x16/0x70  sched_cpu_deactivate+0x26e/0x2a0  cpuhp_invoke_callback+0x3ad/0x10d0  cpuhp_thread_fun+0x3f5/0x680  smpboot_thread_fn+0x56d/0x8d0  kthread+0x309/0x400  ret_from_fork+0x41/0x70  ret_from_fork_asm+0x1b/0x30  &amp;lt;/TASK&amp;gt; Because when cpuset_cpu_inactive() fails in sched_cpu_deactivate(), the cpu offline failed, but sched_smt_present is decremented before calling sched_cpu_deactivate(), it leads to unbalanced dec/inc, so fix it by incrementing sched_smt_present in the error path.&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 179 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/smt: Fix unbalance sched_smt_present dec/inc I got the following warn report while doing stress test: jump label: negative count! WARNING: CPU: 3 PID: 38 at kernel/jump_label.c:263 static_key_slow_try_dec+0x9d/0xb0 Call Trace:  &amp;lt;TASK&amp;gt;  __static_key_slow_dec_cpuslocked+0x16/0x70  sched_cpu_deactivate+0x26e/0x2a0  cpuhp_invoke_callback+0x3ad/0x10d0  cpuhp_thread_fun+0x3f5/0x680  smpboot_thread_fn+0x56d/0x8d0  kthread+0x309/0x400  ret_from_fork+0x41/0x70  ret_from_fork_asm+0x1b/0x30  &amp;lt;/TASK&amp;gt; Because when cpuset_cpu_inactive() fails in sched_cpu_deactivate(), the cpu offline failed, but sched_smt_present is decremented before calling sched_cpu_deactivate(), it leads to unbalanced dec/inc, so fix it by incrementing sched_smt_present in the error path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-44958</guid>
    </item>
  </channel>
</rss>
