<?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 08:35:53 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-74403 — CVE-2026-74403 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74403</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-74403</guid>
    </item>
    <item>
      <title>EUVD-2026-354211</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354211</link>
      <description>EUVD-2026-354211</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354211</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74403</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74403</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: ccp - Check for page allocation failure correctly in TIO&lt;/p&gt;
&lt;p&gt;Sashiko notes:&lt;/p&gt;
&lt;p&gt;&amp;gt; if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it
&amp;gt; safe to pass it directly to page_address()?
&amp;gt;
&amp;gt; On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might
&amp;gt; compute a deterministic but invalid, non-zero virtual address. The
&amp;gt; subsequent if (tio_status) check would then evaluate to true, and
&amp;gt; sev_tsm_init_locked() would dereference the invalid pointer.&lt;/p&gt;
&lt;p&gt;Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by
checking the page allocation itself for NULL, not the resulting virtual
address.&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 - Check for page allocation failure correctly in TIO&lt;/p&gt;
&lt;p&gt;Sashiko notes:&lt;/p&gt;
&lt;p&gt;&amp;gt; if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it
&amp;gt; safe to pass it directly to page_address()?
&amp;gt;
&amp;gt; On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might
&amp;gt; compute a deterministic but invalid, non-zero virtual address. The
&amp;gt; subsequent if (tio_status) check would then evaluate to true, and
&amp;gt; sev_tsm_init_locked() would dereference the invalid pointer.&lt;/p&gt;
&lt;p&gt;Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by
checking the page allocation itself for NULL, not the resulting virtual
address.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74403</guid>
    </item>
    <item>
      <title>GHSA-6wq7-xhx5-p3vw</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6wq7-xhx5-p3vw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: ccp - Check for page allocation failure correctly in TIO&lt;/p&gt;
&lt;p&gt;Sashiko notes:&lt;/p&gt;
&lt;p&gt;&amp;gt; if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it
&amp;gt; safe to pass it directly to page_address()?
&amp;gt;
&amp;gt; On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might
&amp;gt; compute a deterministic but invalid, non-zero virtual address. The
&amp;gt; subsequent if (tio_status) check would then evaluate to true, and
&amp;gt; sev_tsm_init_locked() would dereference the invalid pointer.&lt;/p&gt;
&lt;p&gt;Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by
checking the page allocation itself for NULL, not the resulting virtual
address.&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 - Check for page allocation failure correctly in TIO&lt;/p&gt;
&lt;p&gt;Sashiko notes:&lt;/p&gt;
&lt;p&gt;&amp;gt; if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it
&amp;gt; safe to pass it directly to page_address()?
&amp;gt;
&amp;gt; On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might
&amp;gt; compute a deterministic but invalid, non-zero virtual address. The
&amp;gt; subsequent if (tio_status) check would then evaluate to true, and
&amp;gt; sev_tsm_init_locked() would dereference the invalid pointer.&lt;/p&gt;
&lt;p&gt;Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by
checking the page allocation itself for NULL, not the resulting virtual
address.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6wq7-xhx5-p3vw</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74403</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74403</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 115 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Check for page allocation failure correctly in TIO Sashiko notes: &amp;gt; if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it &amp;gt; safe to pass it directly to page_address()? &amp;gt; &amp;gt; On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might &amp;gt; compute a deterministic but invalid, non-zero virtual address. The &amp;gt; subsequent if (tio_status) check would then evaluate to true, and &amp;gt; sev_tsm_init_locked() would dereference the invalid pointer. Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by checking the page allocation itself for NULL, not the resulting virtual address.&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 115 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Check for page allocation failure correctly in TIO Sashiko notes: &amp;gt; if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it &amp;gt; safe to pass it directly to page_address()? &amp;gt; &amp;gt; On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might &amp;gt; compute a deterministic but invalid, non-zero virtual address. The &amp;gt; subsequent if (tio_status) check would then evaluate to true, and &amp;gt; sev_tsm_init_locked() would dereference the invalid pointer. Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by checking the page allocation itself for NULL, not the resulting virtual address.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74403</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
