<?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://cve.radiocsirt.org</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>Thu, 15 Oct 2026 11:26:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39790 — bus: mhi: host: Detect events pointing to unexpected TREs</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-39790</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bus: mhi: host: Detect events pointing to unexpected TREs&lt;/p&gt;
&lt;p&gt;When a remote device sends a completion event to the host, it contains a
pointer to the consumed TRE. The host uses this pointer to process all of
the TREs between it and the host&amp;#39;s local copy of the ring&amp;#39;s read pointer.
This works when processing completion for chained transactions, but can
lead to nasty results if the device sends an event for a single-element
transaction with a read pointer that is multiple elements ahead of the
host&amp;#39;s read pointer.&lt;/p&gt;
&lt;p&gt;For instance, if the host accesses an event ring while the device is
updating it, the pointer inside of the event might still point to an old
TRE. If the host uses the channel&amp;#39;s xfer_cb() to directly free the buffer
pointed to by the TRE, the buffer will be double-freed.&lt;/p&gt;
&lt;p&gt;This behavior was observed on an ep that used upstream EP stack without
&amp;#39;commit 6f18d174b73d (&amp;#34;bus: mhi: ep: Update read pointer only after buffer
is written&amp;#34;)&amp;#39;. Where the device updated the events ring pointer before
updating the event contents, so it left a window where the host was able to
access the stale data the event pointed to, before the device had the
chance to update them. The usual pattern was that the host received an
event pointing to a TRE that is not immediately after the last processed
one, so it got treated as if it was a chained transaction, processing all
of the TREs in between the two read pointers.&lt;/p&gt;
&lt;p&gt;This commit…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bus: mhi: host: Detect events pointing to unexpected TREs&lt;/p&gt;
&lt;p&gt;When a remote device sends a completion event to the host, it contains a
pointer to the consumed TRE. The host uses this pointer to process all of
the TREs between it and the host&amp;#39;s local copy of the ring&amp;#39;s read pointer.
This works when processing completion for chained transactions, but can
lead to nasty results if the device sends an event for a single-element
transaction with a read pointer that is multiple elements ahead of the
host&amp;#39;s read pointer.&lt;/p&gt;
&lt;p&gt;For instance, if the host accesses an event ring while the device is
updating it, the pointer inside of the event might still point to an old
TRE. If the host uses the channel&amp;#39;s xfer_cb() to directly free the buffer
pointed to by the TRE, the buffer will be double-freed.&lt;/p&gt;
&lt;p&gt;This behavior was observed on an ep that used upstream EP stack without
&amp;#39;commit 6f18d174b73d (&amp;#34;bus: mhi: ep: Update read pointer only after buffer
is written&amp;#34;)&amp;#39;. Where the device updated the events ring pointer before
updating the event contents, so it left a window where the host was able to
access the stale data the event pointed to, before the device had the
chance to update them. The usual pattern was that the host received an
event pointing to a TRE that is not immediately after the last processed
one, so it got treated as if it was a chained transaction, processing all
of the TREs in between the two read pointers.&lt;/p&gt;
&lt;p&gt;This commit…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-39790</guid>
    </item>
    <item>
      <title>LSN-0122-1 — Kernel Live Patch Security Notice</title>
      <link>https://cve.radiocsirt.org/vuln/lsn-0122-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15, Ubuntu:Pro:18.04:LTS: linux and 25 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: fs: dlm: fix use after free in midcomms commit While working on
processing dlm message in softirq context I experienced the following KASAN
use-after-free warning: .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: wifi: brcmfmac: Fix oops due to NULL pointer dereference in
brcmf_sdiod_sglist_rw() This patch fixes a NULL pointer dereference bug in
brcmfmac that occurs when a high &amp;#39;sd_sgentry_align&amp;#39; value applies (e.g.
512) and a lot of queued SKBs are sent from the pkt queue.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: padata: fix UAF in padata_reorder A bug was found when run ltp
test: BUG: KASAN: slab-use-after-free in padata_find_next+0x29/0x1a0 Read
of size 4 at addr ffff88bbfe003524 by task kworker/u113:2/3039206 CPU: 0
PID: 3039206 Comm: kworker/u113:2 Kdump: loaded Not tainted 6.6.0+
Workqueue: pdecrypt_parallel padata_parallel_worker Call Trace: &amp;lt;TASK&amp;gt;
dump_stack_lvl+0x32/0x50 print_address_description.constprop.0+0x6b/0x3d0
print_report+0xdd/0x2c0 kasan_report+0xa5/0xd0 padata_find_next+0x29/0x1a0
padata_reorder+0x131/0x220 padata_parallel_worker+0x3d/0xc0
process_one_work+0x2ec/0x5a0 If &amp;#39;mdelay(10)&amp;#39; is added before calling
&amp;#39;padata_find_next&amp;#39; in the &amp;#39;padata_reorder&amp;#39; function, this issue could be
reproduced easily with ltp test (pcrypt_aead01).&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: geneve: Fix use-after-free in geneve_find_de…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15, Ubuntu:Pro:18.04:LTS: linux and 25 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: fs: dlm: fix use after free in midcomms commit While working on
processing dlm message in softirq context I experienced the following KASAN
use-after-free warning: .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: wifi: brcmfmac: Fix oops due to NULL pointer dereference in
brcmf_sdiod_sglist_rw() This patch fixes a NULL pointer dereference bug in
brcmfmac that occurs when a high &amp;#39;sd_sgentry_align&amp;#39; value applies (e.g.
512) and a lot of queued SKBs are sent from the pkt queue.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: padata: fix UAF in padata_reorder A bug was found when run ltp
test: BUG: KASAN: slab-use-after-free in padata_find_next+0x29/0x1a0 Read
of size 4 at addr ffff88bbfe003524 by task kworker/u113:2/3039206 CPU: 0
PID: 3039206 Comm: kworker/u113:2 Kdump: loaded Not tainted 6.6.0+
Workqueue: pdecrypt_parallel padata_parallel_worker Call Trace: &amp;lt;TASK&amp;gt;
dump_stack_lvl+0x32/0x50 print_address_description.constprop.0+0x6b/0x3d0
print_report+0xdd/0x2c0 kasan_report+0xa5/0xd0 padata_find_next+0x29/0x1a0
padata_reorder+0x131/0x220 padata_parallel_worker+0x3d/0xc0
process_one_work+0x2ec/0x5a0 If &amp;#39;mdelay(10)&amp;#39; is added before calling
&amp;#39;padata_find_next&amp;#39; in the &amp;#39;padata_reorder&amp;#39; function, this issue could be
reproduced easily with ltp test (pcrypt_aead01).&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: geneve: Fix use-after-free in geneve_find_de…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/lsn-0122-1</guid>
    </item>
  </channel>
</rss>
