<?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-02T20:54:22.047689+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/bell-cve-2026-46013</id>
    <title>Withdrawn: BELL-CVE-2026-46013 — CVE-2026-46013 does not affect BellSoft software</title>
    <updated>2026-10-02T20:54:22.146244+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <strong>Withdrawn by the publisher.</strong>
        </p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-46013"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831</id>
    <title>certfr-2026-avi-0831 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-10-02T20:54:22.146285+00:00</updated>
    <content>certfr-2026-avi-0831</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-327079</id>
    <title>EUVD-2026-327079</title>
    <updated>2026-10-02T20:54:22.146303+00:00</updated>
    <content>EUVD-2026-327079</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-327079"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46013</id>
    <title>fkie_cve-2026-46013</title>
    <updated>2026-10-02T20:54:22.146315+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>mm/memfd_luo: fix physical address conversion in put_folios cleanup</p>
<p>In memfd_luo_retrieve_folios()'s put_folios cleanup path:</p>
<p>1. kho_restore_folio() expects a phys_addr_t (physical address) but
   receives a raw PFN (pfolio-&gt;pfn). This causes kho_restore_page() to
   check the wrong physical address (pfn &lt;&lt; PAGE_SHIFT instead of the
   actual physical address).</p>
<p>2. This loop lacks the !pfolio-&gt;pfn check that exists in the main
   retrieval loop and memfd_luo_discard_folios(), which could
   incorrectly process sparse file holes where pfn=0.</p>
<p>Fix by converting PFN to physical address with PFN_PHYS() and adding
the !pfolio-&gt;pfn check, matching the pattern used elsewhere in this file.</p>
<p>This issue was identified by the AI review.
https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-46013"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-gxmw-vhgm-hqg8</id>
    <title>GHSA-gxmw-vhgm-hqg8</title>
    <updated>2026-10-02T20:54:22.146353+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>mm/memfd_luo: fix physical address conversion in put_folios cleanup</p>
<p>In memfd_luo_retrieve_folios()'s put_folios cleanup path:</p>
<p>1. kho_restore_folio() expects a phys_addr_t (physical address) but
   receives a raw PFN (pfolio-&gt;pfn). This causes kho_restore_page() to
   check the wrong physical address (pfn &lt;&lt; PAGE_SHIFT instead of the
   actual physical address).</p>
<p>2. This loop lacks the !pfolio-&gt;pfn check that exists in the main
   retrieval loop and memfd_luo_discard_folios(), which could
   incorrectly process sparse file holes where pfn=0.</p>
<p>Fix by converting PFN to physical address with PFN_PHYS() and adding
the !pfolio-&gt;pfn check, matching the pattern used elsewhere in this file.</p>
<p>This issue was identified by the AI review.
https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-gxmw-vhgm-hqg8"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</id>
    <title>openSUSE-SU-2026:10954-1 — kernel-devel-7.0.11-1.1 on GA media</title>
    <updated>2026-10-02T20:54:22.146387+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-7.0.11-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46013</id>
    <title>UBUNTU-CVE-2026-46013</title>
    <updated>2026-10-02T20:54:22.146552+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 98 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: mm/memfd_luo: fix physical address conversion in put_folios cleanup In memfd_luo_retrieve_folios()'s put_folios cleanup path: 1. kho_restore_folio() expects a phys_addr_t (physical address) but    receives a raw PFN (pfolio-&gt;pfn). This causes kho_restore_page() to    check the wrong physical address (pfn &lt;&lt; PAGE_SHIFT instead of the    actual physical address). 2. This loop lacks the !pfolio-&gt;pfn check that exists in the main    retrieval loop and memfd_luo_discard_folios(), which could    incorrectly process sparse file holes where pfn=0. Fix by converting PFN to physical address with PFN_PHYS() and adding the !pfolio-&gt;pfn check, matching the pattern used elsewhere in this file. This issue was identified by the AI review. https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46013"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</id>
    <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-02T20:54:22.146709+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700"/>
  </entry>
</feed>
