<?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 03:42:18 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03078</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03078</link>
      <description>bdu:2026-03078</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03078</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38658</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38658</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38658</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1073 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1073</link>
      <description>certfr-2025-avi-1073</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1073</guid>
    </item>
    <item>
      <title>EUVD-2026-347138</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347138</link>
      <description>EUVD-2026-347138</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347138</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38658</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38658</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails&lt;/p&gt;
&lt;p&gt;Have nvmet_req_init() and req-&amp;gt;execute() complete failed commands.&lt;/p&gt;
&lt;p&gt;Description of the problem:
nvmet_req_init() calls __nvmet_req_complete() internally upon failure,
e.g., unsupported opcode, which calls the &amp;#34;queue_response&amp;#34; callback,
this results in nvmet_pci_epf_queue_response() being called, which will
call nvmet_pci_epf_complete_iod() if data_len is 0 or if dma_dir is
different from DMA_TO_DEVICE. This results in a double completion as
nvmet_pci_epf_exec_iod_work() also calls nvmet_pci_epf_complete_iod()
when nvmet_req_init() fails.&lt;/p&gt;
&lt;p&gt;Steps to reproduce:
On the host send a command with an unsupported opcode with nvme-cli,
For example the admin command &amp;#34;security receive&amp;#34;
$ sudo nvme security-recv /dev/nvme0n1 -n1 -x4096&lt;/p&gt;
&lt;p&gt;This triggers a double completion as nvmet_req_init() fails and
nvmet_pci_epf_queue_response() is called, here iod-&amp;gt;dma_dir is still
in the default state of &amp;#34;DMA_NONE&amp;#34; as set by default in
nvmet_pci_epf_alloc_iod(), so nvmet_pci_epf_complete_iod() is called.
Because nvmet_req_init() failed nvmet_pci_epf_complete_iod() is also
called in nvmet_pci_epf_exec_iod_work() leading to a double completion.
This not only sends two completions to the host but also corrupts the
state of the PCI NVMe target leading to kernel oops.&lt;/p&gt;
&lt;p&gt;This patch lets nvmet_req_init() and req-&amp;gt;execute() complete all failed
commands, and removes the…&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;nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails&lt;/p&gt;
&lt;p&gt;Have nvmet_req_init() and req-&amp;gt;execute() complete failed commands.&lt;/p&gt;
&lt;p&gt;Description of the problem:
nvmet_req_init() calls __nvmet_req_complete() internally upon failure,
e.g., unsupported opcode, which calls the &amp;#34;queue_response&amp;#34; callback,
this results in nvmet_pci_epf_queue_response() being called, which will
call nvmet_pci_epf_complete_iod() if data_len is 0 or if dma_dir is
different from DMA_TO_DEVICE. This results in a double completion as
nvmet_pci_epf_exec_iod_work() also calls nvmet_pci_epf_complete_iod()
when nvmet_req_init() fails.&lt;/p&gt;
&lt;p&gt;Steps to reproduce:
On the host send a command with an unsupported opcode with nvme-cli,
For example the admin command &amp;#34;security receive&amp;#34;
$ sudo nvme security-recv /dev/nvme0n1 -n1 -x4096&lt;/p&gt;
&lt;p&gt;This triggers a double completion as nvmet_req_init() fails and
nvmet_pci_epf_queue_response() is called, here iod-&amp;gt;dma_dir is still
in the default state of &amp;#34;DMA_NONE&amp;#34; as set by default in
nvmet_pci_epf_alloc_iod(), so nvmet_pci_epf_complete_iod() is called.
Because nvmet_req_init() failed nvmet_pci_epf_complete_iod() is also
called in nvmet_pci_epf_exec_iod_work() leading to a double completion.
This not only sends two completions to the host but also corrupts the
state of the PCI NVMe target leading to kernel oops.&lt;/p&gt;
&lt;p&gt;This patch lets nvmet_req_init() and req-&amp;gt;execute() complete all failed
commands, and removes the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38658</guid>
    </item>
    <item>
      <title>GHSA-hw95-chc9-4w36</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hw95-chc9-4w36</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails&lt;/p&gt;
&lt;p&gt;Have nvmet_req_init() and req-&amp;gt;execute() complete failed commands.&lt;/p&gt;
&lt;p&gt;Description of the problem:
nvmet_req_init() calls __nvmet_req_complete() internally upon failure,
e.g., unsupported opcode, which calls the &amp;#34;queue_response&amp;#34; callback,
this results in nvmet_pci_epf_queue_response() being called, which will
call nvmet_pci_epf_complete_iod() if data_len is 0 or if dma_dir is
different from DMA_TO_DEVICE. This results in a double completion as
nvmet_pci_epf_exec_iod_work() also calls nvmet_pci_epf_complete_iod()
when nvmet_req_init() fails.&lt;/p&gt;
&lt;p&gt;Steps to reproduce:
On the host send a command with an unsupported opcode with nvme-cli,
For example the admin command &amp;#34;security receive&amp;#34;
$ sudo nvme security-recv /dev/nvme0n1 -n1 -x4096&lt;/p&gt;
&lt;p&gt;This triggers a double completion as nvmet_req_init() fails and
nvmet_pci_epf_queue_response() is called, here iod-&amp;gt;dma_dir is still
in the default state of &amp;#34;DMA_NONE&amp;#34; as set by default in
nvmet_pci_epf_alloc_iod(), so nvmet_pci_epf_complete_iod() is called.
Because nvmet_req_init() failed nvmet_pci_epf_complete_iod() is also
called in nvmet_pci_epf_exec_iod_work() leading to a double completion.
This not only sends two completions to the host but also corrupts the
state of the PCI NVMe target leading to kernel oops.&lt;/p&gt;
&lt;p&gt;This patch lets nvmet_req_init() and req-&amp;gt;execute() complete all failed
commands, and removes the…&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;nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails&lt;/p&gt;
&lt;p&gt;Have nvmet_req_init() and req-&amp;gt;execute() complete failed commands.&lt;/p&gt;
&lt;p&gt;Description of the problem:
nvmet_req_init() calls __nvmet_req_complete() internally upon failure,
e.g., unsupported opcode, which calls the &amp;#34;queue_response&amp;#34; callback,
this results in nvmet_pci_epf_queue_response() being called, which will
call nvmet_pci_epf_complete_iod() if data_len is 0 or if dma_dir is
different from DMA_TO_DEVICE. This results in a double completion as
nvmet_pci_epf_exec_iod_work() also calls nvmet_pci_epf_complete_iod()
when nvmet_req_init() fails.&lt;/p&gt;
&lt;p&gt;Steps to reproduce:
On the host send a command with an unsupported opcode with nvme-cli,
For example the admin command &amp;#34;security receive&amp;#34;
$ sudo nvme security-recv /dev/nvme0n1 -n1 -x4096&lt;/p&gt;
&lt;p&gt;This triggers a double completion as nvmet_req_init() fails and
nvmet_pci_epf_queue_response() is called, here iod-&amp;gt;dma_dir is still
in the default state of &amp;#34;DMA_NONE&amp;#34; as set by default in
nvmet_pci_epf_alloc_iod(), so nvmet_pci_epf_complete_iod() is called.
Because nvmet_req_init() failed nvmet_pci_epf_complete_iod() is also
called in nvmet_pci_epf_exec_iod_work() leading to a double completion.
This not only sends two completions to the host but also corrupts the
state of the PCI NVMe target leading to kernel oops.&lt;/p&gt;
&lt;p&gt;This patch lets nvmet_req_init() and req-&amp;gt;execute() complete all failed
commands, and removes the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hw95-chc9-4w36</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>SUSE-SU-2025:21074-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21074-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:21074-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38658</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38658</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails Have nvmet_req_init() and req-&amp;gt;execute() complete failed commands. Description of the problem: nvmet_req_init() calls __nvmet_req_complete() internally upon failure, e.g., unsupported opcode, which calls the &amp;#34;queue_response&amp;#34; callback, this results in nvmet_pci_epf_queue_response() being called, which will call nvmet_pci_epf_complete_iod() if data_len is 0 or if dma_dir is different from DMA_TO_DEVICE. This results in a double completion as nvmet_pci_epf_exec_iod_work() also calls nvmet_pci_epf_complete_iod() when nvmet_req_init() fails. Steps to reproduce: On the host send a command with an unsupported opcode with nvme-cli, For example the admin command &amp;#34;security receive&amp;#34; $ sudo nvme security-recv /dev/nvme0n1 -n1 -x4096 This triggers a double completion as nvmet_req_init() fails and nvmet_pci_epf_queue_response() is called, here iod-&amp;gt;dma_dir is still in the default state of &amp;#34;DMA_NONE&amp;#34; as set by default in nvmet_pci_epf_alloc_iod(), so nvmet_pci_epf_complete_iod() is called. Because nvmet_req_init() failed nvmet_pci_epf_complete_iod() is also called in nvmet_pci_epf_exec_iod_work() leading to a double completion. This not only sends two completions to the host but also corrupts the state of the PCI NVMe target leading to kernel oops. This patch lets nvmet_req_init() and req-&amp;gt;execute() complete all failed commands, and removes the double…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails Have nvmet_req_init() and req-&amp;gt;execute() complete failed commands. Description of the problem: nvmet_req_init() calls __nvmet_req_complete() internally upon failure, e.g., unsupported opcode, which calls the &amp;#34;queue_response&amp;#34; callback, this results in nvmet_pci_epf_queue_response() being called, which will call nvmet_pci_epf_complete_iod() if data_len is 0 or if dma_dir is different from DMA_TO_DEVICE. This results in a double completion as nvmet_pci_epf_exec_iod_work() also calls nvmet_pci_epf_complete_iod() when nvmet_req_init() fails. Steps to reproduce: On the host send a command with an unsupported opcode with nvme-cli, For example the admin command &amp;#34;security receive&amp;#34; $ sudo nvme security-recv /dev/nvme0n1 -n1 -x4096 This triggers a double completion as nvmet_req_init() fails and nvmet_pci_epf_queue_response() is called, here iod-&amp;gt;dma_dir is still in the default state of &amp;#34;DMA_NONE&amp;#34; as set by default in nvmet_pci_epf_alloc_iod(), so nvmet_pci_epf_complete_iod() is called. Because nvmet_req_init() failed nvmet_pci_epf_complete_iod() is also called in nvmet_pci_epf_exec_iod_work() leading to a double completion. This not only sends two completions to the host but also corrupts the state of the PCI NVMe target leading to kernel oops. This patch lets nvmet_req_init() and req-&amp;gt;execute() complete all failed commands, and removes the double…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38658</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1898 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und Privilegieneskalation</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen, um seine Privilegien zu erhöhen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1898</guid>
    </item>
  </channel>
</rss>
