<?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>Tue, 13 Oct 2026 02:56:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39735 — jfs: fix slab-out-of-bounds read in ea_get()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-39735</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jfs: fix slab-out-of-bounds read in ea_get()&lt;/p&gt;
&lt;p&gt;During the &amp;#34;size_check&amp;#34; label in ea_get(), the code checks if the extended
attribute list (xattr) size matches ea_size. If not, it logs
&amp;#34;ea_get: invalid extended attribute&amp;#34; and calls print_hex_dump().&lt;/p&gt;
&lt;p&gt;Here, EALIST_SIZE(ea_buf-&amp;gt;xattr) returns 4110417968, which exceeds
INT_MAX (2,147,483,647). Then ea_size is clamped:&lt;/p&gt;
&lt;p&gt;int size = clamp_t(int, ea_size, 0, EALIST_SIZE(ea_buf-&amp;gt;xattr));&lt;/p&gt;
&lt;p&gt;Although clamp_t aims to bound ea_size between 0 and 4110417968, the upper
limit is treated as an int, causing an overflow above 2^31 - 1. This leads
&amp;#34;size&amp;#34; to wrap around and become negative (-184549328).&lt;/p&gt;
&lt;p&gt;The &amp;#34;size&amp;#34; is then passed to print_hex_dump() (called &amp;#34;len&amp;#34; in
print_hex_dump()), it is passed as type size_t (an unsigned
type), this is then stored inside a variable called
&amp;#34;int remaining&amp;#34;, which is then assigned to &amp;#34;int linelen&amp;#34; which
is then passed to hex_dump_to_buffer(). In print_hex_dump()
the for loop, iterates through 0 to len-1, where len is
18446744073525002176, calling hex_dump_to_buffer()
on each iteration:&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;lt; len; i += rowsize) {
		linelen = min(remaining, rowsize);
		remaining -= rowsize;&lt;/p&gt;
&lt;p&gt;hex_dump_to_buffer(ptr + i, linelen, rowsize, groupsize,
				   linebuf, sizeof(linebuf), ascii);&lt;/p&gt;
&lt;p&gt;...
	}&lt;/p&gt;
&lt;p&gt;The expected stopping condition (i &amp;lt; len) is effectively broken
since len is corrupted and very large. This eventually leads to
the &amp;#34;ptr+i&amp;#34; being passed t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;jfs: fix slab-out-of-bounds read in ea_get()&lt;/p&gt;
&lt;p&gt;During the &amp;#34;size_check&amp;#34; label in ea_get(), the code checks if the extended
attribute list (xattr) size matches ea_size. If not, it logs
&amp;#34;ea_get: invalid extended attribute&amp;#34; and calls print_hex_dump().&lt;/p&gt;
&lt;p&gt;Here, EALIST_SIZE(ea_buf-&amp;gt;xattr) returns 4110417968, which exceeds
INT_MAX (2,147,483,647). Then ea_size is clamped:&lt;/p&gt;
&lt;p&gt;int size = clamp_t(int, ea_size, 0, EALIST_SIZE(ea_buf-&amp;gt;xattr));&lt;/p&gt;
&lt;p&gt;Although clamp_t aims to bound ea_size between 0 and 4110417968, the upper
limit is treated as an int, causing an overflow above 2^31 - 1. This leads
&amp;#34;size&amp;#34; to wrap around and become negative (-184549328).&lt;/p&gt;
&lt;p&gt;The &amp;#34;size&amp;#34; is then passed to print_hex_dump() (called &amp;#34;len&amp;#34; in
print_hex_dump()), it is passed as type size_t (an unsigned
type), this is then stored inside a variable called
&amp;#34;int remaining&amp;#34;, which is then assigned to &amp;#34;int linelen&amp;#34; which
is then passed to hex_dump_to_buffer(). In print_hex_dump()
the for loop, iterates through 0 to len-1, where len is
18446744073525002176, calling hex_dump_to_buffer()
on each iteration:&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;lt; len; i += rowsize) {
		linelen = min(remaining, rowsize);
		remaining -= rowsize;&lt;/p&gt;
&lt;p&gt;hex_dump_to_buffer(ptr + i, linelen, rowsize, groupsize,
				   linebuf, sizeof(linebuf), ascii);&lt;/p&gt;
&lt;p&gt;...
	}&lt;/p&gt;
&lt;p&gt;The expected stopping condition (i &amp;lt; len) is effectively broken
since len is corrupted and very large. This eventually leads to
the &amp;#34;ptr+i&amp;#34; being passed t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-39735</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>
