<?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>Sat, 03 Oct 2026 23:00:14 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:8643 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:8643</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: net: gso: fix ownership in __udp_gso_segment (CVE-2025-21926)
  * kernel: vlan: enforce underlying device type (CVE-2025-21920)
  * kernel: xsk: fix an integer overflow in xp_create_and_assign_umem() (CVE-2025-21997)
  * kernel: net: fix geneve_opt length integer overflow (CVE-2025-22055)
  * kernel: ext4: fix OOB read when checking dotdot dir (CVE-2025-37785)
  * kernel: wifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi (CVE-2025-37943)&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:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: net: gso: fix ownership in __udp_gso_segment (CVE-2025-21926)
  * kernel: vlan: enforce underlying device type (CVE-2025-21920)
  * kernel: xsk: fix an integer overflow in xp_create_and_assign_umem() (CVE-2025-21997)
  * kernel: net: fix geneve_opt length integer overflow (CVE-2025-22055)
  * kernel: ext4: fix OOB read when checking dotdot dir (CVE-2025-37785)
  * kernel: wifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi (CVE-2025-37943)&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-2025:8643</guid>
    </item>
    <item>
      <title>bdu:2025-10257</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-10257</link>
      <description>bdu:2025-10257</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-10257</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-37785</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-37785</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-37785</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0368 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0368</link>
      <description>certfr-2025-avi-0368</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0368</guid>
    </item>
    <item>
      <title>EUVD-2026-364528</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364528</link>
      <description>EUVD-2026-364528</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364528</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37785</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37785</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix OOB read when checking dotdot dir&lt;/p&gt;
&lt;p&gt;Mounting a corrupted filesystem with directory which contains &amp;#39;.&amp;#39; dir
entry with rec_len == block size results in out-of-bounds read (later
on, when the corrupted directory is removed).&lt;/p&gt;
&lt;p&gt;ext4_empty_dir() assumes every ext4 directory contains at least &amp;#39;.&amp;#39;
and &amp;#39;..&amp;#39; as directory entries in the first data block. It first loads
the &amp;#39;.&amp;#39; dir entry, performs sanity checks by calling ext4_check_dir_entry()
and then uses its rec_len member to compute the location of &amp;#39;..&amp;#39; dir
entry (in ext4_next_entry). It assumes the &amp;#39;..&amp;#39; dir entry fits into the
same data block.&lt;/p&gt;
&lt;p&gt;If the rec_len of &amp;#39;.&amp;#39; is precisely one block (4KB), it slips through the
sanity checks (it is considered the last directory entry in the data
block) and leaves &amp;#34;struct ext4_dir_entry_2 *de&amp;#34; point exactly past the
memory slot allocated to the data block. The following call to
ext4_check_dir_entry() on new value of de then dereferences this pointer
which results in out-of-bounds mem access.&lt;/p&gt;
&lt;p&gt;Fix this by extending __ext4_check_dir_entry() to check for &amp;#39;.&amp;#39; dir
entries that reach the end of data block. Make sure to ignore the phony
dir entries for checksum (by checking name_len for non-zero).&lt;/p&gt;
&lt;p&gt;Note: This is reported by KASAN as use-after-free in case another
structure was recently freed from the slot past the bound, but it is
really an OOB read.&lt;/p&gt;
&lt;p&gt;This issue was found by syzkaller tool.&lt;/p&gt;
&lt;p&gt;Call Trace:
[   38.594108] BUG:…&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;ext4: fix OOB read when checking dotdot dir&lt;/p&gt;
&lt;p&gt;Mounting a corrupted filesystem with directory which contains &amp;#39;.&amp;#39; dir
entry with rec_len == block size results in out-of-bounds read (later
on, when the corrupted directory is removed).&lt;/p&gt;
&lt;p&gt;ext4_empty_dir() assumes every ext4 directory contains at least &amp;#39;.&amp;#39;
and &amp;#39;..&amp;#39; as directory entries in the first data block. It first loads
the &amp;#39;.&amp;#39; dir entry, performs sanity checks by calling ext4_check_dir_entry()
and then uses its rec_len member to compute the location of &amp;#39;..&amp;#39; dir
entry (in ext4_next_entry). It assumes the &amp;#39;..&amp;#39; dir entry fits into the
same data block.&lt;/p&gt;
&lt;p&gt;If the rec_len of &amp;#39;.&amp;#39; is precisely one block (4KB), it slips through the
sanity checks (it is considered the last directory entry in the data
block) and leaves &amp;#34;struct ext4_dir_entry_2 *de&amp;#34; point exactly past the
memory slot allocated to the data block. The following call to
ext4_check_dir_entry() on new value of de then dereferences this pointer
which results in out-of-bounds mem access.&lt;/p&gt;
&lt;p&gt;Fix this by extending __ext4_check_dir_entry() to check for &amp;#39;.&amp;#39; dir
entries that reach the end of data block. Make sure to ignore the phony
dir entries for checksum (by checking name_len for non-zero).&lt;/p&gt;
&lt;p&gt;Note: This is reported by KASAN as use-after-free in case another
structure was recently freed from the slot past the bound, but it is
really an OOB read.&lt;/p&gt;
&lt;p&gt;This issue was found by syzkaller tool.&lt;/p&gt;
&lt;p&gt;Call Trace:
[   38.594108] BUG:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37785</guid>
    </item>
    <item>
      <title>GHSA-w7jc-wqpw-qxqq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w7jc-wqpw-qxqq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: fix OOB read when checking dotdot dir&lt;/p&gt;
&lt;p&gt;Mounting a corrupted filesystem with directory which contains &amp;#39;.&amp;#39; dir
entry with rec_len == block size results in out-of-bounds read (later
on, when the corrupted directory is removed).&lt;/p&gt;
&lt;p&gt;ext4_empty_dir() assumes every ext4 directory contains at least &amp;#39;.&amp;#39;
and &amp;#39;..&amp;#39; as directory entries in the first data block. It first loads
the &amp;#39;.&amp;#39; dir entry, performs sanity checks by calling ext4_check_dir_entry()
and then uses its rec_len member to compute the location of &amp;#39;..&amp;#39; dir
entry (in ext4_next_entry). It assumes the &amp;#39;..&amp;#39; dir entry fits into the
same data block.&lt;/p&gt;
&lt;p&gt;If the rec_len of &amp;#39;.&amp;#39; is precisely one block (4KB), it slips through the
sanity checks (it is considered the last directory entry in the data
block) and leaves &amp;#34;struct ext4_dir_entry_2 *de&amp;#34; point exactly past the
memory slot allocated to the data block. The following call to
ext4_check_dir_entry() on new value of de then dereferences this pointer
which results in out-of-bounds mem access.&lt;/p&gt;
&lt;p&gt;Fix this by extending __ext4_check_dir_entry() to check for &amp;#39;.&amp;#39; dir
entries that reach the end of data block. Make sure to ignore the phony
dir entries for checksum (by checking name_len for non-zero).&lt;/p&gt;
&lt;p&gt;Note: This is reported by KASAN as use-after-free in case another
structure was recently freed from the slot past the bound, but it is
really an OOB read.&lt;/p&gt;
&lt;p&gt;This issue was found by syzkaller tool.&lt;/p&gt;
&lt;p&gt;Call Trace:
[   38.594108] BUG:…&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;ext4: fix OOB read when checking dotdot dir&lt;/p&gt;
&lt;p&gt;Mounting a corrupted filesystem with directory which contains &amp;#39;.&amp;#39; dir
entry with rec_len == block size results in out-of-bounds read (later
on, when the corrupted directory is removed).&lt;/p&gt;
&lt;p&gt;ext4_empty_dir() assumes every ext4 directory contains at least &amp;#39;.&amp;#39;
and &amp;#39;..&amp;#39; as directory entries in the first data block. It first loads
the &amp;#39;.&amp;#39; dir entry, performs sanity checks by calling ext4_check_dir_entry()
and then uses its rec_len member to compute the location of &amp;#39;..&amp;#39; dir
entry (in ext4_next_entry). It assumes the &amp;#39;..&amp;#39; dir entry fits into the
same data block.&lt;/p&gt;
&lt;p&gt;If the rec_len of &amp;#39;.&amp;#39; is precisely one block (4KB), it slips through the
sanity checks (it is considered the last directory entry in the data
block) and leaves &amp;#34;struct ext4_dir_entry_2 *de&amp;#34; point exactly past the
memory slot allocated to the data block. The following call to
ext4_check_dir_entry() on new value of de then dereferences this pointer
which results in out-of-bounds mem access.&lt;/p&gt;
&lt;p&gt;Fix this by extending __ext4_check_dir_entry() to check for &amp;#39;.&amp;#39; dir
entries that reach the end of data block. Make sure to ignore the phony
dir entries for checksum (by checking name_len for non-zero).&lt;/p&gt;
&lt;p&gt;Note: This is reported by KASAN as use-after-free in case another
structure was recently freed from the slot past the bound, but it is
really an OOB read.&lt;/p&gt;
&lt;p&gt;This issue was found by syzkaller tool.&lt;/p&gt;
&lt;p&gt;Call Trace:
[   38.594108] BUG:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w7jc-wqpw-qxqq</guid>
    </item>
    <item>
      <title>ICSA-26-209-04 — Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-26-209-04</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-26-209-04</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-37785 — ext4: fix OOB read when checking dotdot dir</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-37785</link>
      <description>msrc_CVE-2025-37785</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-37785</guid>
    </item>
    <item>
      <title>OESA-2025-1465 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1465</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context&lt;/p&gt;
&lt;p&gt;If a driver calls can_get_echo_skb() during a hardware IRQ (which is often, but
not always, the case), the &amp;amp;apos;WARN_ON(in_irq)&amp;amp;apos; in
net/core/skbuff.c#skb_release_head_state() might be triggered, under network
congestion circumstances, together with the potential risk of a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;The root cause of this issue is the call to kfree_skb() instead of
dev_kfree_skb_irq() in net/core/dev.c#enqueue_to_backlog().&lt;/p&gt;
&lt;p&gt;This patch prevents the skb to be freed within the call to netif_rx() by
incrementing its reference count with skb_get(). The skb is finally freed by
one of the in-irq-context safe functions: dev_consume_skb_any() or
dev_kfree_skb_any(). The &amp;amp;quot;any&amp;amp;quot; version is used because some drivers might call
can_get_echo_skb() in a normal context.&lt;/p&gt;
&lt;p&gt;The reason for this issue to occur is that initially, in the core network
stack, loopback skb were not supposed to be received in hardware IRQ context.
The CAN stack is an exeption.&lt;/p&gt;
&lt;p&gt;This bug was previously reported back in 2017 in [1] but the proposed patch
never got accepted.&lt;/p&gt;
&lt;p&gt;While [1] directly modifies net/core/dev.c, we try to propose here a
smoother modification local to CAN network stack (the assumption
behind is that only CAN devices are affected by this issue).&lt;/p&gt;
&lt;p&gt;[1] http://lore.kern…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context&lt;/p&gt;
&lt;p&gt;If a driver calls can_get_echo_skb() during a hardware IRQ (which is often, but
not always, the case), the &amp;amp;apos;WARN_ON(in_irq)&amp;amp;apos; in
net/core/skbuff.c#skb_release_head_state() might be triggered, under network
congestion circumstances, together with the potential risk of a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;The root cause of this issue is the call to kfree_skb() instead of
dev_kfree_skb_irq() in net/core/dev.c#enqueue_to_backlog().&lt;/p&gt;
&lt;p&gt;This patch prevents the skb to be freed within the call to netif_rx() by
incrementing its reference count with skb_get(). The skb is finally freed by
one of the in-irq-context safe functions: dev_consume_skb_any() or
dev_kfree_skb_any(). The &amp;amp;quot;any&amp;amp;quot; version is used because some drivers might call
can_get_echo_skb() in a normal context.&lt;/p&gt;
&lt;p&gt;The reason for this issue to occur is that initially, in the core network
stack, loopback skb were not supposed to be received in hardware IRQ context.
The CAN stack is an exeption.&lt;/p&gt;
&lt;p&gt;This bug was previously reported back in 2017 in [1] but the proposed patch
never got accepted.&lt;/p&gt;
&lt;p&gt;While [1] directly modifies net/core/dev.c, we try to propose here a
smoother modification local to CAN network stack (the assumption
behind is that only CAN devices are affected by this issue).&lt;/p&gt;
&lt;p&gt;[1] http://lore.kern…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1465</guid>
    </item>
    <item>
      <title>RHSA-2025:8374 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:8374</link>
      <description>&lt;p&gt;kernel: sched/fair: Fix potential memory corruption in child_cfs_rq_on_list kernel: cifs: Fix integer overflow while processing acregmax mount option kernel: ext4: fix OOB read when checking dotdot dir&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: sched/fair: Fix potential memory corruption in child_cfs_rq_on_list kernel: cifs: Fix integer overflow while processing acregmax mount option kernel: ext4: fix OOB read when checking dotdot dir&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:8374</guid>
    </item>
    <item>
      <title>RHSA-2025:8643 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:8643</link>
      <description>&lt;p&gt;kernel: vlan: enforce underlying device type kernel: net: gso: fix ownership in __udp_gso_segment kernel: xsk: fix an integer overflow in xp_create_and_assign_umem() kernel: net: fix geneve_opt length integer overflow kernel: ext4: fix OOB read when checking dotdot dir kernel: wifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: vlan: enforce underlying device type kernel: net: gso: fix ownership in __udp_gso_segment kernel: xsk: fix an integer overflow in xp_create_and_assign_umem() kernel: net: fix geneve_opt length integer overflow kernel: ext4: fix OOB read when checking dotdot dir kernel: wifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:8643</guid>
    </item>
    <item>
      <title>SSA-019113 — SSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-019113</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-019113</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01600-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:01600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37785</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37785</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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix OOB read when checking dotdot dir Mounting a corrupted filesystem with directory which contains &amp;#39;.&amp;#39; dir entry with rec_len == block size results in out-of-bounds read (later on, when the corrupted directory is removed). ext4_empty_dir() assumes every ext4 directory contains at least &amp;#39;.&amp;#39; and &amp;#39;..&amp;#39; as directory entries in the first data block. It first loads the &amp;#39;.&amp;#39; dir entry, performs sanity checks by calling ext4_check_dir_entry() and then uses its rec_len member to compute the location of &amp;#39;..&amp;#39; dir entry (in ext4_next_entry). It assumes the &amp;#39;..&amp;#39; dir entry fits into the same data block. If the rec_len of &amp;#39;.&amp;#39; is precisely one block (4KB), it slips through the sanity checks (it is considered the last directory entry in the data block) and leaves &amp;#34;struct ext4_dir_entry_2 *de&amp;#34; point exactly past the memory slot allocated to the data block. The following call to ext4_check_dir_entry() on new value of de then dereferences this pointer which results in out-of-bounds mem access. Fix this by extending __ext4_check_dir_entry() to check for &amp;#39;.&amp;#39; dir entries that reach the end of data block. Make sure to ignore the phony dir entries for checksum (by checking name_len for non-zero). Note: This is reported by KASAN as use-after-free in case another structure was recently freed from the slot past the bound, but it is really an OOB read. This issue was found by syzkaller tool. Call Trace: [   38.594108] BUG: KASAN: s…&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 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix OOB read when checking dotdot dir Mounting a corrupted filesystem with directory which contains &amp;#39;.&amp;#39; dir entry with rec_len == block size results in out-of-bounds read (later on, when the corrupted directory is removed). ext4_empty_dir() assumes every ext4 directory contains at least &amp;#39;.&amp;#39; and &amp;#39;..&amp;#39; as directory entries in the first data block. It first loads the &amp;#39;.&amp;#39; dir entry, performs sanity checks by calling ext4_check_dir_entry() and then uses its rec_len member to compute the location of &amp;#39;..&amp;#39; dir entry (in ext4_next_entry). It assumes the &amp;#39;..&amp;#39; dir entry fits into the same data block. If the rec_len of &amp;#39;.&amp;#39; is precisely one block (4KB), it slips through the sanity checks (it is considered the last directory entry in the data block) and leaves &amp;#34;struct ext4_dir_entry_2 *de&amp;#34; point exactly past the memory slot allocated to the data block. The following call to ext4_check_dir_entry() on new value of de then dereferences this pointer which results in out-of-bounds mem access. Fix this by extending __ext4_check_dir_entry() to check for &amp;#39;.&amp;#39; dir entries that reach the end of data block. Make sure to ignore the phony dir entries for checksum (by checking name_len for non-zero). Note: This is reported by KASAN as use-after-free in case another structure was recently freed from the slot past the bound, but it is really an OOB read. This issue was found by syzkaller tool. Call Trace: [   38.594108] BUG: KASAN: s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37785</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0861 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0861</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand oder nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand oder nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0861</guid>
    </item>
  </channel>
</rss>
