<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T17:58:29.428510+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2025-14574</id>
    <title>bdu:2025-14574</title>
    <updated>2026-10-04T17:58:29.906875+00:00</updated>
    <content>bdu:2025-14574</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-14574"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-40190</id>
    <title>BELL-CVE-2025-40190</title>
    <updated>2026-10-04T17:58:29.906948+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2025-40190"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1048</id>
    <title>certfr-2025-avi-1048 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
    <updated>2026-10-04T17:58:29.906983+00:00</updated>
    <content>certfr-2025-avi-1048</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-1048"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-347368</id>
    <title>EUVD-2026-347368</title>
    <updated>2026-10-04T17:58:29.907001+00:00</updated>
    <content>EUVD-2026-347368</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-347368"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-40190</id>
    <title>fkie_cve-2025-40190</title>
    <updated>2026-10-04T17:58:29.907013+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: guard against EA inode refcount underflow in xattr update</p>
<p>syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA
inode refcount that is already &lt;= 0 and then applies ref_change (often
-1). That lets the refcount underflow and we proceed with a bogus value,
triggering errors like:</p>
<p>EXT4-fs error: EA inode &lt;n&gt; ref underflow: ref_count=-1 ref_change=-1
  EXT4-fs warning: ea_inode dec ref err=-117</p>
<p>Make the invariant explicit: if the current refcount is non-positive,
treat this as on-disk corruption, emit ext4_error_inode(), and fail the
operation with -EFSCORRUPTED instead of updating the refcount. Delete the
WARN_ONCE() as negative refcounts are now impossible; keep error reporting
in ext4_error_inode().</p>
<p>This prevents the underflow and the follow-on orphan/cleanup churn.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-40190"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-j9x6-gmq6-xm5x</id>
    <title>GHSA-j9x6-gmq6-xm5x</title>
    <updated>2026-10-04T17:58:29.907048+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: guard against EA inode refcount underflow in xattr update</p>
<p>syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA
inode refcount that is already &lt;= 0 and then applies ref_change (often
-1). That lets the refcount underflow and we proceed with a bogus value,
triggering errors like:</p>
<p>EXT4-fs error: EA inode &lt;n&gt; ref underflow: ref_count=-1 ref_change=-1
  EXT4-fs warning: ea_inode dec ref err=-117</p>
<p>Make the invariant explicit: if the current refcount is non-positive,
treat this as on-disk corruption, emit ext4_error_inode(), and fail the
operation with -EFSCORRUPTED instead of updating the refcount. Delete the
WARN_ONCE() as negative refcounts are now impossible; keep error reporting
in ext4_error_inode().</p>
<p>This prevents the underflow and the follow-on orphan/cleanup churn.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-j9x6-gmq6-xm5x"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-40190</id>
    <title>msrc_CVE-2025-40190 — ext4: guard against EA inode refcount underflow in xattr update</title>
    <updated>2026-10-04T17:58:29.907072+00:00</updated>
    <content>msrc_CVE-2025-40190</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-40190"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-2765</id>
    <title>OESA-2025-2765 — kernel security update</title>
    <updated>2026-10-04T17:58:29.907090+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.(CVE-2024-36357)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fs/ntfs3: Prevent integer overflow in hdr_first_de()</p>
<p>The &amp;quot;de_off&amp;quot; and &amp;quot;used&amp;quot; variables come from the disk so they both need to
check.  The problem is that on 32bit systems if they&amp;apos;re both greater than
UINT_MAX - 16 then the check does work as intended because of an integer
overflow.(CVE-2025-22080)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: fix off-by-one error in do_split</p>
<p>Syzkaller detected a use-after-free issue in ext4_insert_dentry that was
caused by out-of-bounds access due to incorrect splitting in do_split.</p>
<p>BUG: KASAN: use-after-free in ext4_insert_dentry+0x36a/0x6d0 fs/ext4/namei.c:2109
Write of size 251 at addr ffff888074572f14 by task syz-executor335/5847</p>
<p>CPU: 0 UID: 0 PID: 5847 Comm: syz-executor335 Not tainted 6.12.0-rc6-syzkaller-00318-ga9cda7c0ffed #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:377 [inline]
 print_report+0x169/0x550 mm/k…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-2765"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1</id>
    <title>openSUSE-SU-2026:20145-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T17:58:29.907374+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1</id>
    <title>SUSE-SU-2026:0278-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T17:58:29.907534+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40190</id>
    <title>UBUNTU-CVE-2025-40190</title>
    <updated>2026-10-04T17:58:29.907861+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 255 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ext4: guard against EA inode refcount underflow in xattr update syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA inode refcount that is already &lt;= 0 and then applies ref_change (often -1). That lets the refcount underflow and we proceed with a bogus value, triggering errors like:   EXT4-fs error: EA inode &lt;n&gt; ref underflow: ref_count=-1 ref_change=-1   EXT4-fs warning: ea_inode dec ref err=-117 Make the invariant explicit: if the current refcount is non-positive, treat this as on-disk corruption, emit ext4_error_inode(), and fail the operation with -EFSCORRUPTED instead of updating the refcount. Delete the WARN_ONCE() as negative refcounts are now impossible; keep error reporting in ext4_error_inode(). This prevents the underflow and the follow-on orphan/cleanup churn.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40190"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2595</id>
    <title>WID-SEC-W-2025-2595 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T17:58:29.908157+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2595"/>
  </entry>
</feed>
