https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 13:20:30 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-10719 bdu:2026-10719 https://cve.radiocsirt.org/vuln/bdu:2026-10719 https://cve.radiocsirt.org/vuln/bell-cve-2026-31589 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-31589 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0519 certfr-2026-avi-0519 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0519 https://cve.radiocsirt.org/vuln/euvd-2026-347726 EUVD-2026-347726 https://cve.radiocsirt.org/vuln/euvd-2026-347726 https://cve.radiocsirt.org/vuln/fkie_cve-2026-31589 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: call -&gt;free_folio() directly in folio_unmap_invalidate()</p> <p>We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;ve already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping-&gt;a_ops.</p> <p>Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: call -&gt;free_folio() directly in folio_unmap_invalidate()</p> <p>We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;ve already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping-&gt;a_ops.</p> <p>Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-31589 https://cve.radiocsirt.org/vuln/ghsa-mg7h-q7hw-m596 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: call -&gt;free_folio() directly in folio_unmap_invalidate()</p> <p>We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;ve already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping-&gt;a_ops.</p> <p>Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: call -&gt;free_folio() directly in folio_unmap_invalidate()</p> <p>We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;ve already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping-&gt;a_ops.</p> <p>Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.</p> https://cve.radiocsirt.org/vuln/ghsa-mg7h-q7hw-m596 https://cve.radiocsirt.org/vuln/msrc_cve-2026-31589 msrc_CVE-2026-31589 https://cve.radiocsirt.org/vuln/msrc_cve-2026-31589 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10703-1 <p>kernel-devel-7.0.3-1.1 on GA media</p> <p>kernel-devel-7.0.3-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10703-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31589 <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 118 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm: call -&gt;free_folio() directly in folio_unmap_invalidate() We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;ve already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping-&gt;a_ops. Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.</p> <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 118 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm: call -&gt;free_folio() directly in folio_unmap_invalidate() We can only call filemap_free_folio() if we have a reference to (or hold a lock on) the mapping. Otherwise, we&#39;ve already removed the folio from the mapping so it no longer pins the mapping and the mapping can be removed, causing a use-after-free when accessing mapping-&gt;a_ops. Follow the same pattern as __remove_mapping() and load the free_folio function pointer before dropping the lock on the mapping. That lets us make filemap_free_folio() static as this was the only caller outside filemap.c.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31589 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279