<?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>Sun, 04 Oct 2026 08:23:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-13737</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13737</link>
      <description>bdu:2026-13737</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13737</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-46268</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-46268</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-2026-46268</guid>
    </item>
    <item>
      <title>EUVD-2026-324428</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-324428</link>
      <description>EUVD-2026-324428</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-324428</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46268</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46268</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition&lt;/p&gt;
&lt;p&gt;Commit b7e282378773 has already changed the initial page refcount of
p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses
&amp;#34;VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))&amp;#34; to assert the initial page
refcount should not be zero and the following will be reported when
CONFIG_DEBUG_VM is enabled:&lt;/p&gt;
&lt;p&gt;page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000
  flags: 0x20000000002000(reserved|node=0|zone=4)
  raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000
  raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
  page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))
  ------------[ cut here ]------------
  WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60&lt;/p&gt;
&lt;p&gt;Fix by using &amp;#34;page_ref_count(page)&amp;#34; as the assertion condition.&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;PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition&lt;/p&gt;
&lt;p&gt;Commit b7e282378773 has already changed the initial page refcount of
p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses
&amp;#34;VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))&amp;#34; to assert the initial page
refcount should not be zero and the following will be reported when
CONFIG_DEBUG_VM is enabled:&lt;/p&gt;
&lt;p&gt;page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000
  flags: 0x20000000002000(reserved|node=0|zone=4)
  raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000
  raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
  page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))
  ------------[ cut here ]------------
  WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60&lt;/p&gt;
&lt;p&gt;Fix by using &amp;#34;page_ref_count(page)&amp;#34; as the assertion condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46268</guid>
    </item>
    <item>
      <title>GHSA-9f46-h8mj-93v5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9f46-h8mj-93v5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition&lt;/p&gt;
&lt;p&gt;Commit b7e282378773 has already changed the initial page refcount of
p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses
&amp;#34;VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))&amp;#34; to assert the initial page
refcount should not be zero and the following will be reported when
CONFIG_DEBUG_VM is enabled:&lt;/p&gt;
&lt;p&gt;page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000
  flags: 0x20000000002000(reserved|node=0|zone=4)
  raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000
  raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
  page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))
  ------------[ cut here ]------------
  WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60&lt;/p&gt;
&lt;p&gt;Fix by using &amp;#34;page_ref_count(page)&amp;#34; as the assertion condition.&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;PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition&lt;/p&gt;
&lt;p&gt;Commit b7e282378773 has already changed the initial page refcount of
p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses
&amp;#34;VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))&amp;#34; to assert the initial page
refcount should not be zero and the following will be reported when
CONFIG_DEBUG_VM is enabled:&lt;/p&gt;
&lt;p&gt;page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000
  flags: 0x20000000002000(reserved|node=0|zone=4)
  raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000
  raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
  page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))
  ------------[ cut here ]------------
  WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60&lt;/p&gt;
&lt;p&gt;Fix by using &amp;#34;page_ref_count(page)&amp;#34; as the assertion condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9f46-h8mj-93v5</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46268</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46268</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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition Commit b7e282378773 has already changed the initial page refcount of p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses &amp;#34;VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))&amp;#34; to assert the initial page refcount should not be zero and the following will be reported when CONFIG_DEBUG_VM is enabled:   page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000   flags: 0x20000000002000(reserved|node=0|zone=4)   raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000   raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000   page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))   ------------[ cut here ]------------   WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60 Fix by using &amp;#34;page_ref_count(page)&amp;#34; as the assertion condition.&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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition Commit b7e282378773 has already changed the initial page refcount of p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses &amp;#34;VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))&amp;#34; to assert the initial page refcount should not be zero and the following will be reported when CONFIG_DEBUG_VM is enabled:   page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000   flags: 0x20000000002000(reserved|node=0|zone=4)   raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000   raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000   page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))   ------------[ cut here ]------------   WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60 Fix by using &amp;#34;page_ref_count(page)&amp;#34; as the assertion condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46268</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1802 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1802</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1802</guid>
    </item>
  </channel>
</rss>
