<?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>Fri, 02 Oct 2026 22:10:31 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:1661 — Moderate: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:1661</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: IB/hfi1: Fix sdma.h tx-&amp;gt;num_descs off-by-one error (CVE-2024-26766)
  * kernel: RDMA/core: Fix &amp;#34;KASAN: slab-use-after-free Read in ib_register_device&amp;#34; problem (CVE-2025-38022)
  * kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)
  * kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)
  * kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)
  * kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)
  * kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)
  * kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
  * kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling (CVE-2025-40322)
  * kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: IB/hfi1: Fix sdma.h tx-&amp;gt;num_descs off-by-one error (CVE-2024-26766)
  * kernel: RDMA/core: Fix &amp;#34;KASAN: slab-use-after-free Read in ib_register_device&amp;#34; problem (CVE-2025-38022)
  * kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)
  * kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)
  * kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)
  * kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)
  * kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)
  * kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
  * kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling (CVE-2025-40322)
  * kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:1661</guid>
    </item>
    <item>
      <title>bdu:2025-09134</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-09134</link>
      <description>bdu:2025-09134</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-09134</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38415</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38415</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://cve.radiocsirt.org/vuln/bell-cve-2025-38415</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>EUVD-2026-328620</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-328620</link>
      <description>EUVD-2026-328620</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-328620</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38415</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38415</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Squashfs: check return result of sb_min_blocksize&lt;/p&gt;
&lt;p&gt;Syzkaller reports an &amp;#34;UBSAN: shift-out-of-bounds in squashfs_bio_read&amp;#34; bug.&lt;/p&gt;
&lt;p&gt;Syzkaller forks multiple processes which after mounting the Squashfs
filesystem, issues an ioctl(&amp;#34;/dev/loop0&amp;#34;, LOOP_SET_BLOCK_SIZE, 0x8000). 
Now if this ioctl occurs at the same time another process is in the
process of mounting a Squashfs filesystem on /dev/loop0, the failure
occurs.  When this happens the following code in squashfs_fill_super()
fails.&lt;/p&gt;
&lt;p&gt;----
msblk-&amp;gt;devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE);
msblk-&amp;gt;devblksize_log2 = ffz(~msblk-&amp;gt;devblksize);
----&lt;/p&gt;
&lt;p&gt;sb_min_blocksize() returns 0, which means msblk-&amp;gt;devblksize is set to 0.&lt;/p&gt;
&lt;p&gt;As a result, ffz(~msblk-&amp;gt;devblksize) returns 64, and msblk-&amp;gt;devblksize_log2
is set to 64.&lt;/p&gt;
&lt;p&gt;This subsequently causes the&lt;/p&gt;
&lt;p&gt;UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36
shift exponent 64 is too large for 64-bit type &amp;#39;u64&amp;#39; (aka
&amp;#39;unsigned long long&amp;#39;)&lt;/p&gt;
&lt;p&gt;This commit adds a check for a 0 return by sb_min_blocksize().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Squashfs: check return result of sb_min_blocksize&lt;/p&gt;
&lt;p&gt;Syzkaller reports an &amp;#34;UBSAN: shift-out-of-bounds in squashfs_bio_read&amp;#34; bug.&lt;/p&gt;
&lt;p&gt;Syzkaller forks multiple processes which after mounting the Squashfs
filesystem, issues an ioctl(&amp;#34;/dev/loop0&amp;#34;, LOOP_SET_BLOCK_SIZE, 0x8000). 
Now if this ioctl occurs at the same time another process is in the
process of mounting a Squashfs filesystem on /dev/loop0, the failure
occurs.  When this happens the following code in squashfs_fill_super()
fails.&lt;/p&gt;
&lt;p&gt;----
msblk-&amp;gt;devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE);
msblk-&amp;gt;devblksize_log2 = ffz(~msblk-&amp;gt;devblksize);
----&lt;/p&gt;
&lt;p&gt;sb_min_blocksize() returns 0, which means msblk-&amp;gt;devblksize is set to 0.&lt;/p&gt;
&lt;p&gt;As a result, ffz(~msblk-&amp;gt;devblksize) returns 64, and msblk-&amp;gt;devblksize_log2
is set to 64.&lt;/p&gt;
&lt;p&gt;This subsequently causes the&lt;/p&gt;
&lt;p&gt;UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36
shift exponent 64 is too large for 64-bit type &amp;#39;u64&amp;#39; (aka
&amp;#39;unsigned long long&amp;#39;)&lt;/p&gt;
&lt;p&gt;This commit adds a check for a 0 return by sb_min_blocksize().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38415</guid>
    </item>
    <item>
      <title>GHSA-j3rr-hppv-g55q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j3rr-hppv-g55q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Squashfs: check return result of sb_min_blocksize&lt;/p&gt;
&lt;p&gt;Syzkaller reports an &amp;#34;UBSAN: shift-out-of-bounds in squashfs_bio_read&amp;#34; bug.&lt;/p&gt;
&lt;p&gt;Syzkaller forks multiple processes which after mounting the Squashfs
filesystem, issues an ioctl(&amp;#34;/dev/loop0&amp;#34;, LOOP_SET_BLOCK_SIZE, 0x8000). 
Now if this ioctl occurs at the same time another process is in the
process of mounting a Squashfs filesystem on /dev/loop0, the failure
occurs.  When this happens the following code in squashfs_fill_super()
fails.&lt;/p&gt;
&lt;p&gt;----
msblk-&amp;gt;devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE);
msblk-&amp;gt;devblksize_log2 = ffz(~msblk-&amp;gt;devblksize);
----&lt;/p&gt;
&lt;p&gt;sb_min_blocksize() returns 0, which means msblk-&amp;gt;devblksize is set to 0.&lt;/p&gt;
&lt;p&gt;As a result, ffz(~msblk-&amp;gt;devblksize) returns 64, and msblk-&amp;gt;devblksize_log2
is set to 64.&lt;/p&gt;
&lt;p&gt;This subsequently causes the&lt;/p&gt;
&lt;p&gt;UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36
shift exponent 64 is too large for 64-bit type &amp;#39;u64&amp;#39; (aka
&amp;#39;unsigned long long&amp;#39;)&lt;/p&gt;
&lt;p&gt;This commit adds a check for a 0 return by sb_min_blocksize().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Squashfs: check return result of sb_min_blocksize&lt;/p&gt;
&lt;p&gt;Syzkaller reports an &amp;#34;UBSAN: shift-out-of-bounds in squashfs_bio_read&amp;#34; bug.&lt;/p&gt;
&lt;p&gt;Syzkaller forks multiple processes which after mounting the Squashfs
filesystem, issues an ioctl(&amp;#34;/dev/loop0&amp;#34;, LOOP_SET_BLOCK_SIZE, 0x8000). 
Now if this ioctl occurs at the same time another process is in the
process of mounting a Squashfs filesystem on /dev/loop0, the failure
occurs.  When this happens the following code in squashfs_fill_super()
fails.&lt;/p&gt;
&lt;p&gt;----
msblk-&amp;gt;devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE);
msblk-&amp;gt;devblksize_log2 = ffz(~msblk-&amp;gt;devblksize);
----&lt;/p&gt;
&lt;p&gt;sb_min_blocksize() returns 0, which means msblk-&amp;gt;devblksize is set to 0.&lt;/p&gt;
&lt;p&gt;As a result, ffz(~msblk-&amp;gt;devblksize) returns 64, and msblk-&amp;gt;devblksize_log2
is set to 64.&lt;/p&gt;
&lt;p&gt;This subsequently causes the&lt;/p&gt;
&lt;p&gt;UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36
shift exponent 64 is too large for 64-bit type &amp;#39;u64&amp;#39; (aka
&amp;#39;unsigned long long&amp;#39;)&lt;/p&gt;
&lt;p&gt;This commit adds a check for a 0 return by sb_min_blocksize().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j3rr-hppv-g55q</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38415 — Squashfs: check return result of sb_min_blocksize</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38415</link>
      <description>msrc_CVE-2025-38415</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38415</guid>
    </item>
    <item>
      <title>OESA-2025-1959 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1959</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfrm: state: fix out-of-bounds read during lookup&lt;/p&gt;
&lt;p&gt;lookup and resize can run in parallel.&lt;/p&gt;
&lt;p&gt;The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.&lt;/p&gt;
&lt;p&gt;rehash does:
  rcu_assign_pointer(net-&amp;amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;amp;gt;xfrm.state_hmask = nhashmask;&lt;/p&gt;
&lt;p&gt;While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;amp;gt;xfrm.state_bydst + h, bydst) {&lt;/p&gt;
&lt;p&gt;This is only safe in case the update to state_bydst is larger than
net-&amp;amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).&lt;/p&gt;
&lt;p&gt;Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.&lt;/p&gt;
&lt;p&gt;The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.&lt;/p&gt;
&lt;p&gt;xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eth: bnxt: always recalculate features after XDP clearing, fix n…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfrm: state: fix out-of-bounds read during lookup&lt;/p&gt;
&lt;p&gt;lookup and resize can run in parallel.&lt;/p&gt;
&lt;p&gt;The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.&lt;/p&gt;
&lt;p&gt;rehash does:
  rcu_assign_pointer(net-&amp;amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;amp;gt;xfrm.state_hmask = nhashmask;&lt;/p&gt;
&lt;p&gt;While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;amp;gt;xfrm.state_bydst + h, bydst) {&lt;/p&gt;
&lt;p&gt;This is only safe in case the update to state_bydst is larger than
net-&amp;amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).&lt;/p&gt;
&lt;p&gt;Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.&lt;/p&gt;
&lt;p&gt;The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.&lt;/p&gt;
&lt;p&gt;xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;eth: bnxt: always recalculate features after XDP clearing, fix n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1959</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1</guid>
    </item>
    <item>
      <title>RHSA-2026:1661 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:1661</link>
      <description>&lt;p&gt;kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() kernel: IB/hfi1: Fix sdma.h tx-&amp;gt;num_descs off-by-one error kernel: RDMA/core: Fix &amp;#34;KASAN: slab-use-after-free Read in ib_register_device&amp;#34; problem kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing kernel: mptcp: fix race condition in mptcp_schedule_work() kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() kernel: IB/hfi1: Fix sdma.h tx-&amp;gt;num_descs off-by-one error kernel: RDMA/core: Fix &amp;#34;KASAN: slab-use-after-free Read in ib_register_device&amp;#34; problem kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing kernel: mptcp: fix race condition in mptcp_schedule_work() kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:1661</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02846-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02846-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:02846-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38415</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38415</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 212 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Squashfs: check return result of sb_min_blocksize Syzkaller reports an &amp;#34;UBSAN: shift-out-of-bounds in squashfs_bio_read&amp;#34; bug. Syzkaller forks multiple processes which after mounting the Squashfs filesystem, issues an ioctl(&amp;#34;/dev/loop0&amp;#34;, LOOP_SET_BLOCK_SIZE, 0x8000). Now if this ioctl occurs at the same time another process is in the process of mounting a Squashfs filesystem on /dev/loop0, the failure occurs.  When this happens the following code in squashfs_fill_super() fails. ---- msblk-&amp;gt;devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE); msblk-&amp;gt;devblksize_log2 = ffz(~msblk-&amp;gt;devblksize); ---- sb_min_blocksize() returns 0, which means msblk-&amp;gt;devblksize is set to 0. As a result, ffz(~msblk-&amp;gt;devblksize) returns 64, and msblk-&amp;gt;devblksize_log2 is set to 64. This subsequently causes the UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36 shift exponent 64 is too large for 64-bit type &amp;#39;u64&amp;#39; (aka &amp;#39;unsigned long long&amp;#39;) This commit adds a check for a 0 return by sb_min_blocksize().&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 212 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Squashfs: check return result of sb_min_blocksize Syzkaller reports an &amp;#34;UBSAN: shift-out-of-bounds in squashfs_bio_read&amp;#34; bug. Syzkaller forks multiple processes which after mounting the Squashfs filesystem, issues an ioctl(&amp;#34;/dev/loop0&amp;#34;, LOOP_SET_BLOCK_SIZE, 0x8000). Now if this ioctl occurs at the same time another process is in the process of mounting a Squashfs filesystem on /dev/loop0, the failure occurs.  When this happens the following code in squashfs_fill_super() fails. ---- msblk-&amp;gt;devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE); msblk-&amp;gt;devblksize_log2 = ffz(~msblk-&amp;gt;devblksize); ---- sb_min_blocksize() returns 0, which means msblk-&amp;gt;devblksize is set to 0. As a result, ffz(~msblk-&amp;gt;devblksize) returns 64, and msblk-&amp;gt;devblksize_log2 is set to 64. This subsequently causes the UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36 shift exponent 64 is too large for 64-bit type &amp;#39;u64&amp;#39; (aka &amp;#39;unsigned long long&amp;#39;) This commit adds a check for a 0 return by sb_min_blocksize().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38415</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1653 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1653</link>
      <description>&lt;p&gt;Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1653</guid>
    </item>
  </channel>
</rss>
