<?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-04T22:32:25.550811+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:2026-02288</id>
    <title>bdu:2026-02288</title>
    <updated>2026-10-04T22:32:25.983071+00:00</updated>
    <content>bdu:2026-02288</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-02288"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-22125</id>
    <title>BELL-CVE-2025-22125</title>
    <updated>2026-10-04T22:32:25.983142+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-22125"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</id>
    <title>certfr-2025-avi-0509 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-10-04T22:32:25.983180+00:00</updated>
    <content>certfr-2025-avi-0509</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-314192</id>
    <title>EUVD-2026-314192</title>
    <updated>2026-10-04T22:32:25.983199+00:00</updated>
    <content>EUVD-2026-314192</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-314192"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-22125</id>
    <title>fkie_cve-2025-22125</title>
    <updated>2026-10-04T22:32:25.983211+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>md/raid1,raid10: don't ignore IO flags</p>
<p>If blk-wbt is enabled by default, it's found that raid write performance
is quite bad because all IO are throttled by wbt of underlying disks,
due to flag REQ_IDLE is ignored. And turns out this behaviour exist since
blk-wbt is introduced.</p>
<p>Other than REQ_IDLE, other flags should not be ignored as well, for
example REQ_META can be set for filesystems, clearing it can cause priority
reverse problems; And REQ_NOWAIT should not be cleared as well, because
io will wait instead of failing directly in underlying disks.</p>
<p>Fix those problems by keep IO flags from master bio.</p>
<p>Fises: f51d46d0e7cb ("md: add support for REQ_NOWAIT")</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-22125"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3wr8-w2fq-6q7v</id>
    <title>GHSA-3wr8-w2fq-6q7v</title>
    <updated>2026-10-04T22:32:25.983259+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>md/raid1,raid10: don't ignore IO flags</p>
<p>If blk-wbt is enabled by default, it's found that raid write performance
is quite bad because all IO are throttled by wbt of underlying disks,
due to flag REQ_IDLE is ignored. And turns out this behaviour exist since
blk-wbt is introduced.</p>
<p>Other than REQ_IDLE, other flags should not be ignored as well, for
example REQ_META can be set for filesystems, clearing it can cause priority
reverse problems; And REQ_NOWAIT should not be cleared as well, because
io will wait instead of failing directly in underlying disks.</p>
<p>Fix those problems by keep IO flags from master bio.</p>
<p>Fises: f51d46d0e7cb ("md: add support for REQ_NOWAIT")</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3wr8-w2fq-6q7v"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-22125</id>
    <title>msrc_CVE-2025-22125 — md/raid1,raid10: don't ignore IO flags</title>
    <updated>2026-10-04T22:32:25.983282+00:00</updated>
    <content>msrc_CVE-2025-22125</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-22125"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-1463</id>
    <title>OESA-2025-1463 — kernel security update</title>
    <updated>2026-10-04T22:32:25.983299+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>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>PCI/ASPM: Fix link state exit during switch upstream function removal</p>
<p>Before 456d8aa37d0f (&amp;quot;PCI/ASPM: Disable ASPM on MFD function removal to
avoid use-after-free&amp;quot;), we would free the ASPM link only after the last
function on the bus pertaining to the given link was removed.</p>
<p>That was too late. If function 0 is removed before sibling function,
link-&amp;gt;downstream would point to free&amp;apos;d memory after.</p>
<p>After above change, we freed the ASPM parent link state upon any function
removal on the bus pertaining to a given link.</p>
<p>That is too early. If the link is to a PCIe switch with MFD on the upstream
port, then removing functions other than 0 first would free a link which
still remains parent_link to the remaining downstream ports.</p>
<p>The resulting GPFs are especially frequent during hot-unplug, because
pciehp removes devices on the link bus in reverse order.</p>
<p>On that switch, function 0 is the virtual P2P bridge to the internal bus.
Free exactly when function 0 is removed -- before the parent link is
obsolete, but after all subordinate links are gone.</p>
<p>[kwilczynski: commit log](CVE-2024-58093)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>jfs: add check read-only before truncation in jfs_truncate_nolock()</p>
<p>Added a check for &amp;quot;read-only&amp;quot; mode in the `jfs_truncate_nolock`
function to avoid errors…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-1463"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2025:01919-1</id>
    <title>SUSE-SU-2025:01919-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T22:32:25.983425+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-2025:01919-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22125</id>
    <title>UBUNTU-CVE-2025-22125</title>
    <updated>2026-10-04T22:32:25.983702+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 206 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: md/raid1,raid10: don't ignore IO flags If blk-wbt is enabled by default, it's found that raid write performance is quite bad because all IO are throttled by wbt of underlying disks, due to flag REQ_IDLE is ignored. And turns out this behaviour exist since blk-wbt is introduced. Other than REQ_IDLE, other flags should not be ignored as well, for example REQ_META can be set for filesystems, clearing it can cause priority reverse problems; And REQ_NOWAIT should not be cleared as well, because io will wait instead of failing directly in underlying disks. Fix those problems by keep IO flags from master bio. Fises: f51d46d0e7cb ("md: add support for REQ_NOWAIT")</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22125"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</id>
    <title>WID-SEC-W-2025-0844 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T22:32:25.983947+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844"/>
  </entry>
</feed>
