<?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 20:37:45 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-80651 — CVE-2026-80651 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80651</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80651</guid>
    </item>
    <item>
      <title>EUVD-2026-361036</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361036</link>
      <description>EUVD-2026-361036</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361036</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80651</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80651</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: ccp/sev-dev-tsm - bail out early when pdev-&amp;gt;bus is NULL&lt;/p&gt;
&lt;p&gt;dsm_create() initially checks pdev-&amp;gt;bus when computing segment_id:&lt;/p&gt;
&lt;p&gt;u8 segment_id = pdev-&amp;gt;bus ? pci_domain_nr(pdev-&amp;gt;bus) : 0;&lt;/p&gt;
&lt;p&gt;But the next two lines unconditionally dereference pdev-&amp;gt;bus via
pcie_find_root_port() and especially pci_dev_id(pdev), which expands
to PCI_DEVID(dev-&amp;gt;bus-&amp;gt;number, dev-&amp;gt;devfn). If pdev-&amp;gt;bus is in fact
NULL, segment_id is initialised to 0 but the very next statement
crashes the kernel.&lt;/p&gt;
&lt;p&gt;smatch flags this:&lt;/p&gt;
&lt;p&gt;drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we
    previously assumed &amp;#39;pdev-&amp;gt;bus&amp;#39; could be null (see line 251)&lt;/p&gt;
&lt;p&gt;Make the NULL handling consistent: if pdev-&amp;gt;bus is NULL the device
has no PCI context to work with and SEV TIO setup cannot proceed,
so return -ENODEV before any of the bus-dependent lookups. The
remaining initialisation now runs only on the path where pdev-&amp;gt;bus
is known to be valid.&lt;/p&gt;
&lt;p&gt;No change for callers where pdev-&amp;gt;bus is non-NULL, which is the
only case where dsm_create() did meaningful work before this change.&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;crypto: ccp/sev-dev-tsm - bail out early when pdev-&amp;gt;bus is NULL&lt;/p&gt;
&lt;p&gt;dsm_create() initially checks pdev-&amp;gt;bus when computing segment_id:&lt;/p&gt;
&lt;p&gt;u8 segment_id = pdev-&amp;gt;bus ? pci_domain_nr(pdev-&amp;gt;bus) : 0;&lt;/p&gt;
&lt;p&gt;But the next two lines unconditionally dereference pdev-&amp;gt;bus via
pcie_find_root_port() and especially pci_dev_id(pdev), which expands
to PCI_DEVID(dev-&amp;gt;bus-&amp;gt;number, dev-&amp;gt;devfn). If pdev-&amp;gt;bus is in fact
NULL, segment_id is initialised to 0 but the very next statement
crashes the kernel.&lt;/p&gt;
&lt;p&gt;smatch flags this:&lt;/p&gt;
&lt;p&gt;drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we
    previously assumed &amp;#39;pdev-&amp;gt;bus&amp;#39; could be null (see line 251)&lt;/p&gt;
&lt;p&gt;Make the NULL handling consistent: if pdev-&amp;gt;bus is NULL the device
has no PCI context to work with and SEV TIO setup cannot proceed,
so return -ENODEV before any of the bus-dependent lookups. The
remaining initialisation now runs only on the path where pdev-&amp;gt;bus
is known to be valid.&lt;/p&gt;
&lt;p&gt;No change for callers where pdev-&amp;gt;bus is non-NULL, which is the
only case where dsm_create() did meaningful work before this change.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80651</guid>
    </item>
    <item>
      <title>GHSA-m48c-q8rx-qxxm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m48c-q8rx-qxxm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: ccp/sev-dev-tsm - bail out early when pdev-&amp;gt;bus is NULL&lt;/p&gt;
&lt;p&gt;dsm_create() initially checks pdev-&amp;gt;bus when computing segment_id:&lt;/p&gt;
&lt;p&gt;u8 segment_id = pdev-&amp;gt;bus ? pci_domain_nr(pdev-&amp;gt;bus) : 0;&lt;/p&gt;
&lt;p&gt;But the next two lines unconditionally dereference pdev-&amp;gt;bus via
pcie_find_root_port() and especially pci_dev_id(pdev), which expands
to PCI_DEVID(dev-&amp;gt;bus-&amp;gt;number, dev-&amp;gt;devfn). If pdev-&amp;gt;bus is in fact
NULL, segment_id is initialised to 0 but the very next statement
crashes the kernel.&lt;/p&gt;
&lt;p&gt;smatch flags this:&lt;/p&gt;
&lt;p&gt;drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we
    previously assumed &amp;#39;pdev-&amp;gt;bus&amp;#39; could be null (see line 251)&lt;/p&gt;
&lt;p&gt;Make the NULL handling consistent: if pdev-&amp;gt;bus is NULL the device
has no PCI context to work with and SEV TIO setup cannot proceed,
so return -ENODEV before any of the bus-dependent lookups. The
remaining initialisation now runs only on the path where pdev-&amp;gt;bus
is known to be valid.&lt;/p&gt;
&lt;p&gt;No change for callers where pdev-&amp;gt;bus is non-NULL, which is the
only case where dsm_create() did meaningful work before this change.&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;crypto: ccp/sev-dev-tsm - bail out early when pdev-&amp;gt;bus is NULL&lt;/p&gt;
&lt;p&gt;dsm_create() initially checks pdev-&amp;gt;bus when computing segment_id:&lt;/p&gt;
&lt;p&gt;u8 segment_id = pdev-&amp;gt;bus ? pci_domain_nr(pdev-&amp;gt;bus) : 0;&lt;/p&gt;
&lt;p&gt;But the next two lines unconditionally dereference pdev-&amp;gt;bus via
pcie_find_root_port() and especially pci_dev_id(pdev), which expands
to PCI_DEVID(dev-&amp;gt;bus-&amp;gt;number, dev-&amp;gt;devfn). If pdev-&amp;gt;bus is in fact
NULL, segment_id is initialised to 0 but the very next statement
crashes the kernel.&lt;/p&gt;
&lt;p&gt;smatch flags this:&lt;/p&gt;
&lt;p&gt;drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we
    previously assumed &amp;#39;pdev-&amp;gt;bus&amp;#39; could be null (see line 251)&lt;/p&gt;
&lt;p&gt;Make the NULL handling consistent: if pdev-&amp;gt;bus is NULL the device
has no PCI context to work with and SEV TIO setup cannot proceed,
so return -ENODEV before any of the bus-dependent lookups. The
remaining initialisation now runs only on the path where pdev-&amp;gt;bus
is known to be valid.&lt;/p&gt;
&lt;p&gt;No change for callers where pdev-&amp;gt;bus is non-NULL, which is the
only case where dsm_create() did meaningful work before this change.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m48c-q8rx-qxxm</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80651</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80651</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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: crypto: ccp/sev-dev-tsm - bail out early when pdev-&amp;gt;bus is NULL dsm_create() initially checks pdev-&amp;gt;bus when computing segment_id: 	u8 segment_id = pdev-&amp;gt;bus ? pci_domain_nr(pdev-&amp;gt;bus) : 0; But the next two lines unconditionally dereference pdev-&amp;gt;bus via pcie_find_root_port() and especially pci_dev_id(pdev), which expands to PCI_DEVID(dev-&amp;gt;bus-&amp;gt;number, dev-&amp;gt;devfn). If pdev-&amp;gt;bus is in fact NULL, segment_id is initialised to 0 but the very next statement crashes the kernel. smatch flags this:   drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we     previously assumed &amp;#39;pdev-&amp;gt;bus&amp;#39; could be null (see line 251) Make the NULL handling consistent: if pdev-&amp;gt;bus is NULL the device has no PCI context to work with and SEV TIO setup cannot proceed, so return -ENODEV before any of the bus-dependent lookups. The remaining initialisation now runs only on the path where pdev-&amp;gt;bus is known to be valid. No change for callers where pdev-&amp;gt;bus is non-NULL, which is the only case where dsm_create() did meaningful work before this change.&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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: crypto: ccp/sev-dev-tsm - bail out early when pdev-&amp;gt;bus is NULL dsm_create() initially checks pdev-&amp;gt;bus when computing segment_id: 	u8 segment_id = pdev-&amp;gt;bus ? pci_domain_nr(pdev-&amp;gt;bus) : 0; But the next two lines unconditionally dereference pdev-&amp;gt;bus via pcie_find_root_port() and especially pci_dev_id(pdev), which expands to PCI_DEVID(dev-&amp;gt;bus-&amp;gt;number, dev-&amp;gt;devfn). If pdev-&amp;gt;bus is in fact NULL, segment_id is initialised to 0 but the very next statement crashes the kernel. smatch flags this:   drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we     previously assumed &amp;#39;pdev-&amp;gt;bus&amp;#39; could be null (see line 251) Make the NULL handling consistent: if pdev-&amp;gt;bus is NULL the device has no PCI context to work with and SEV TIO setup cannot proceed, so return -ENODEV before any of the bus-dependent lookups. The remaining initialisation now runs only on the path where pdev-&amp;gt;bus is known to be valid. No change for callers where pdev-&amp;gt;bus is non-NULL, which is the only case where dsm_create() did meaningful work before this change.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80651</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
