<?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 01:15:02 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-36894</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-36894</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-36894</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</link>
      <description>certfr-2024-avi-0526</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0526</guid>
    </item>
    <item>
      <title>OESA-2024-1767 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-1767</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;
can: mcba_usb: fix memory leak in mcba_usb&#13;
&#13;
Syzbot reported memory leak in SocketCAN driver for Microchip CAN BUS
Analyzer Tool. The problem was in unfreed usb_coherent.&#13;
&#13;
In mcba_usb_start() 20 coherent buffers are allocated and there is
nothing, that frees them:&#13;
&#13;
1) In callback function the urb is resubmitted and that&amp;amp;apos;s all
2) In disconnect function urbs are simply killed, but URB_FREE_BUFFER
   is not set (see mcba_usb_start) and this flag cannot be used with
   coherent buffers.&#13;
&#13;
Fail log:
| [ 1354.053291][ T8413] mcba_usb 1-1:0.0 can0: device disconnected
| [ 1367.059384][ T8420] kmemleak: 20 new suspected memory leaks (see /sys/kernel/debug/kmem)&#13;
&#13;
So, all allocated buffers should be freed with usb_free_coherent()
explicitly&#13;
&#13;
NOTE:
The same pattern for allocating and freeing coherent buffers
is used in drivers/net/can/usb/kvaser_usb/kvaser_usb_core.c(CVE-2021-47231)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
can: j1939: fix Use-after-Free, hold skb ref while in use&#13;
&#13;
This patch fixes a Use-after-Free found by the syzbot.&#13;
&#13;
The problem is that a skb is taken from the per-session skb queue,
without incrementing the ref count. This leads to a Use-after-Free if
the skb is taken concurrently from the session queue due to a CTS.(CVE-2021-47232)&#13;
&#13;
In the Linux kernel, the following v…&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;
can: mcba_usb: fix memory leak in mcba_usb&#13;
&#13;
Syzbot reported memory leak in SocketCAN driver for Microchip CAN BUS
Analyzer Tool. The problem was in unfreed usb_coherent.&#13;
&#13;
In mcba_usb_start() 20 coherent buffers are allocated and there is
nothing, that frees them:&#13;
&#13;
1) In callback function the urb is resubmitted and that&amp;amp;apos;s all
2) In disconnect function urbs are simply killed, but URB_FREE_BUFFER
   is not set (see mcba_usb_start) and this flag cannot be used with
   coherent buffers.&#13;
&#13;
Fail log:
| [ 1354.053291][ T8413] mcba_usb 1-1:0.0 can0: device disconnected
| [ 1367.059384][ T8420] kmemleak: 20 new suspected memory leaks (see /sys/kernel/debug/kmem)&#13;
&#13;
So, all allocated buffers should be freed with usb_free_coherent()
explicitly&#13;
&#13;
NOTE:
The same pattern for allocating and freeing coherent buffers
is used in drivers/net/can/usb/kvaser_usb/kvaser_usb_core.c(CVE-2021-47231)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
can: j1939: fix Use-after-Free, hold skb ref while in use&#13;
&#13;
This patch fixes a Use-after-Free found by the syzbot.&#13;
&#13;
The problem is that a skb is taken from the per-session skb queue,
without incrementing the ref count. This leads to a Use-after-Free if
the skb is taken concurrently from the session queue due to a CTS.(CVE-2021-47232)&#13;
&#13;
In the Linux kernel, the following v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-1767</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-36894</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36894</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 184 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete 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:     DWC3 Gadget                               FFS Application dwc3_gadget_soft_disconnect()              ...   --&amp;gt; dwc3_stop_active_transfers()     --&amp;gt; dwc3_gadget_giveback(-ESHUTDOWN)       --&amp;gt; ffs_epfile_async_io_complete()   ffs_aio_cancel()         --&amp;gt; usb_ep_free_request()            --&amp;gt; usb_ep_dequeue() 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;gt;req) the FFS application is also referencing it for the usb_ep_dequeue() call.  This can lead to accessing a stale/hanging pointer. commit b566d38857fc (&amp;#34;usb: gadget: f_fs: use io_data-&amp;gt;status consistently&amp;#34;) relocated the usb_ep_free_request() into ffs_epfile_async_io_complete(). However, in order to properly implement locking to mitigate this issue, the spinlock can&amp;#39;t be added to ffs_epfile_async_io_complete(), as usb_ep_dequeue() (if successfully dequeuing a U…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 184 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete 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:     DWC3 Gadget                               FFS Application dwc3_gadget_soft_disconnect()              ...   --&amp;gt; dwc3_stop_active_transfers()     --&amp;gt; dwc3_gadget_giveback(-ESHUTDOWN)       --&amp;gt; ffs_epfile_async_io_complete()   ffs_aio_cancel()         --&amp;gt; usb_ep_free_request()            --&amp;gt; usb_ep_dequeue() 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;gt;req) the FFS application is also referencing it for the usb_ep_dequeue() call.  This can lead to accessing a stale/hanging pointer. commit b566d38857fc (&amp;#34;usb: gadget: f_fs: use io_data-&amp;gt;status consistently&amp;#34;) relocated the usb_ep_free_request() into ffs_epfile_async_io_complete(). However, in order to properly implement locking to mitigate this issue, the spinlock can&amp;#39;t be added to ffs_epfile_async_io_complete(), as usb_ep_dequeue() (if successfully dequeuing a U…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-36894</guid>
    </item>
  </channel>
</rss>
