https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 03:45:15 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-10522 bdu:2026-10522 https://cve.radiocsirt.org/vuln/bdu:2026-10522 https://cve.radiocsirt.org/vuln/bell-cve-2025-40270 <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-2025-40270 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0169 certfr-2026-avi-0169 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0169 https://cve.radiocsirt.org/vuln/euvd-2026-347400 EUVD-2026-347400 https://cve.radiocsirt.org/vuln/euvd-2026-347400 https://cve.radiocsirt.org/vuln/fkie_cve-2025-40270 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm, swap: fix potential UAF issue for VMA readahead</p> <p>Since commit 78524b05f1a3 (&#34;mm, swap: avoid redundant swap device pinning&#34;), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device reference internally, because all callers of __read_swap_cache_async are already holding a swap entry reference. The repeated swap device pinning isn&#39;t needed on the same swap device.</p> <p>Caller of VMA readahead is also holding a reference to the target entry&#39;s swap device, but VMA readahead walks the page table, so it might encounter swap entries from other devices, and call __read_swap_cache_async on another device without holding a reference to it.</p> <p>So it is possible to cause a UAF when swapoff of device A raced with swapin on device B, and VMA readahead tries to read swap entries from device A. It&#39;s not easy to trigger, but in theory, it could cause real issues.</p> <p>Make VMA readahead try to get the device reference first if the swap device is a different one from the target entry.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm, swap: fix potential UAF issue for VMA readahead</p> <p>Since commit 78524b05f1a3 (&#34;mm, swap: avoid redundant swap device pinning&#34;), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device reference internally, because all callers of __read_swap_cache_async are already holding a swap entry reference. The repeated swap device pinning isn&#39;t needed on the same swap device.</p> <p>Caller of VMA readahead is also holding a reference to the target entry&#39;s swap device, but VMA readahead walks the page table, so it might encounter swap entries from other devices, and call __read_swap_cache_async on another device without holding a reference to it.</p> <p>So it is possible to cause a UAF when swapoff of device A raced with swapin on device B, and VMA readahead tries to read swap entries from device A. It&#39;s not easy to trigger, but in theory, it could cause real issues.</p> <p>Make VMA readahead try to get the device reference first if the swap device is a different one from the target entry.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-40270 https://cve.radiocsirt.org/vuln/ghsa-hfc9-3847-7v4r <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm, swap: fix potential UAF issue for VMA readahead</p> <p>Since commit 78524b05f1a3 (&#34;mm, swap: avoid redundant swap device pinning&#34;), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device reference internally, because all callers of __read_swap_cache_async are already holding a swap entry reference. The repeated swap device pinning isn&#39;t needed on the same swap device.</p> <p>Caller of VMA readahead is also holding a reference to the target entry&#39;s swap device, but VMA readahead walks the page table, so it might encounter swap entries from other devices, and call __read_swap_cache_async on another device without holding a reference to it.</p> <p>So it is possible to cause a UAF when swapoff of device A raced with swapin on device B, and VMA readahead tries to read swap entries from device A. It&#39;s not easy to trigger, but in theory, it could cause real issues.</p> <p>Make VMA readahead try to get the device reference first if the swap device is a different one from the target entry.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm, swap: fix potential UAF issue for VMA readahead</p> <p>Since commit 78524b05f1a3 (&#34;mm, swap: avoid redundant swap device pinning&#34;), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device reference internally, because all callers of __read_swap_cache_async are already holding a swap entry reference. The repeated swap device pinning isn&#39;t needed on the same swap device.</p> <p>Caller of VMA readahead is also holding a reference to the target entry&#39;s swap device, but VMA readahead walks the page table, so it might encounter swap entries from other devices, and call __read_swap_cache_async on another device without holding a reference to it.</p> <p>So it is possible to cause a UAF when swapoff of device A raced with swapin on device B, and VMA readahead tries to read swap entries from device A. It&#39;s not easy to trigger, but in theory, it could cause real issues.</p> <p>Make VMA readahead try to get the device reference first if the swap device is a different one from the target entry.</p> https://cve.radiocsirt.org/vuln/ghsa-hfc9-3847-7v4r https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40270 <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 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm, swap: fix potential UAF issue for VMA readahead Since commit 78524b05f1a3 (&#34;mm, swap: avoid redundant swap device pinning&#34;), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device reference internally, because all callers of __read_swap_cache_async are already holding a swap entry reference. The repeated swap device pinning isn&#39;t needed on the same swap device. Caller of VMA readahead is also holding a reference to the target entry&#39;s swap device, but VMA readahead walks the page table, so it might encounter swap entries from other devices, and call __read_swap_cache_async on another device without holding a reference to it. So it is possible to cause a UAF when swapoff of device A raced with swapin on device B, and VMA readahead tries to read swap entries from device A. It&#39;s not easy to trigger, but in theory, it could cause real issues. Make VMA readahead try to get the device reference first if the swap device is a different one from the target entry.</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 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm, swap: fix potential UAF issue for VMA readahead Since commit 78524b05f1a3 (&#34;mm, swap: avoid redundant swap device pinning&#34;), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device reference internally, because all callers of __read_swap_cache_async are already holding a swap entry reference. The repeated swap device pinning isn&#39;t needed on the same swap device. Caller of VMA readahead is also holding a reference to the target entry&#39;s swap device, but VMA readahead walks the page table, so it might encounter swap entries from other devices, and call __read_swap_cache_async on another device without holding a reference to it. So it is possible to cause a UAF when swapoff of device A raced with swapin on device B, and VMA readahead tries to read swap entries from device A. It&#39;s not easy to trigger, but in theory, it could cause real issues. Make VMA readahead try to get the device reference first if the swap device is a different one from the target entry.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40270 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756