https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 19:07:51 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46280 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-46280 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0783 certfr-2026-avi-0783 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0783 https://cve.radiocsirt.org/vuln/euvd-2026-348065 EUVD-2026-348065 https://cve.radiocsirt.org/vuln/euvd-2026-348065 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46280 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: test_hmm: evict device pages on file close to avoid use-after-free</p> <p>Patch series &#34;Minor hmm_test fixes and cleanups&#34;.</p> <p>Two bugfixes a cleanup for the HMM kernel selftests. These were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing and pointing out the problems.</p> <p>This patch (of 3):</p> <p>When dmirror_fops_release() is called it frees the dmirror struct but doesn&#39;t migrate device private pages back to system memory first. This leaves those pages with a dangling zone_device_data pointer to the freed dmirror.</p> <p>If a subsequent fault occurs on those pages (eg. during coredump) the dmirror_devmem_fault() callback dereferences the stale pointer causing a kernel panic. This was reported [1] when running mm/ksft_hmm.sh on arm64, where a test failure triggered SIGABRT and the resulting coredump walked the VMAs faulting in the stale device private pages.</p> <p>Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in dmirror_fops_release() to migrate all device private pages back to system memory before freeing the dmirror struct. The function is moved earlier in the file to avoid a forward declaration.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: test_hmm: evict device pages on file close to avoid use-after-free</p> <p>Patch series &#34;Minor hmm_test fixes and cleanups&#34;.</p> <p>Two bugfixes a cleanup for the HMM kernel selftests. These were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing and pointing out the problems.</p> <p>This patch (of 3):</p> <p>When dmirror_fops_release() is called it frees the dmirror struct but doesn&#39;t migrate device private pages back to system memory first. This leaves those pages with a dangling zone_device_data pointer to the freed dmirror.</p> <p>If a subsequent fault occurs on those pages (eg. during coredump) the dmirror_devmem_fault() callback dereferences the stale pointer causing a kernel panic. This was reported [1] when running mm/ksft_hmm.sh on arm64, where a test failure triggered SIGABRT and the resulting coredump walked the VMAs faulting in the stale device private pages.</p> <p>Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in dmirror_fops_release() to migrate all device private pages back to system memory before freeing the dmirror struct. The function is moved earlier in the file to avoid a forward declaration.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46280 https://cve.radiocsirt.org/vuln/ghsa-vjjg-r28q-g2g4 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: test_hmm: evict device pages on file close to avoid use-after-free</p> <p>Patch series &#34;Minor hmm_test fixes and cleanups&#34;.</p> <p>Two bugfixes a cleanup for the HMM kernel selftests. These were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing and pointing out the problems.</p> <p>This patch (of 3):</p> <p>When dmirror_fops_release() is called it frees the dmirror struct but doesn&#39;t migrate device private pages back to system memory first. This leaves those pages with a dangling zone_device_data pointer to the freed dmirror.</p> <p>If a subsequent fault occurs on those pages (eg. during coredump) the dmirror_devmem_fault() callback dereferences the stale pointer causing a kernel panic. This was reported [1] when running mm/ksft_hmm.sh on arm64, where a test failure triggered SIGABRT and the resulting coredump walked the VMAs faulting in the stale device private pages.</p> <p>Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in dmirror_fops_release() to migrate all device private pages back to system memory before freeing the dmirror struct. The function is moved earlier in the file to avoid a forward declaration.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>lib: test_hmm: evict device pages on file close to avoid use-after-free</p> <p>Patch series &#34;Minor hmm_test fixes and cleanups&#34;.</p> <p>Two bugfixes a cleanup for the HMM kernel selftests. These were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing and pointing out the problems.</p> <p>This patch (of 3):</p> <p>When dmirror_fops_release() is called it frees the dmirror struct but doesn&#39;t migrate device private pages back to system memory first. This leaves those pages with a dangling zone_device_data pointer to the freed dmirror.</p> <p>If a subsequent fault occurs on those pages (eg. during coredump) the dmirror_devmem_fault() callback dereferences the stale pointer causing a kernel panic. This was reported [1] when running mm/ksft_hmm.sh on arm64, where a test failure triggered SIGABRT and the resulting coredump walked the VMAs faulting in the stale device private pages.</p> <p>Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in dmirror_fops_release() to migrate all device private pages back to system memory before freeing the dmirror struct. The function is moved earlier in the file to avoid a forward declaration.</p> https://cve.radiocsirt.org/vuln/ghsa-vjjg-r28q-g2g4 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46280 msrc_CVE-2026-46280 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46280 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 <p>kernel-devel-7.0.12-1.1 on GA media</p> <p>kernel-devel-7.0.12-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11014-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46280 <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 192 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: lib: test_hmm: evict device pages on file close to avoid use-after-free Patch series &#34;Minor hmm_test fixes and cleanups&#34;. Two bugfixes a cleanup for the HMM kernel selftests. These were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing and pointing out the problems. This patch (of 3): When dmirror_fops_release() is called it frees the dmirror struct but doesn&#39;t migrate device private pages back to system memory first. This leaves those pages with a dangling zone_device_data pointer to the freed dmirror. If a subsequent fault occurs on those pages (eg. during coredump) the dmirror_devmem_fault() callback dereferences the stale pointer causing a kernel panic. This was reported [1] when running mm/ksft_hmm.sh on arm64, where a test failure triggered SIGABRT and the resulting coredump walked the VMAs faulting in the stale device private pages. Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in dmirror_fops_release() to migrate all device private pages back to system memory before freeing the dmirror struct. The function is moved earlier in the file to avoid a forward declaration.</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 192 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: lib: test_hmm: evict device pages on file close to avoid use-after-free Patch series &#34;Minor hmm_test fixes and cleanups&#34;. Two bugfixes a cleanup for the HMM kernel selftests. These were mostly reported by Zenghui Yu with special thanks to Lorenzo for analysing and pointing out the problems. This patch (of 3): When dmirror_fops_release() is called it frees the dmirror struct but doesn&#39;t migrate device private pages back to system memory first. This leaves those pages with a dangling zone_device_data pointer to the freed dmirror. If a subsequent fault occurs on those pages (eg. during coredump) the dmirror_devmem_fault() callback dereferences the stale pointer causing a kernel panic. This was reported [1] when running mm/ksft_hmm.sh on arm64, where a test failure triggered SIGABRT and the resulting coredump walked the VMAs faulting in the stale device private pages. Fix this by calling dmirror_device_evict_chunk() for each devmem chunk in dmirror_fops_release() to migrate all device private pages back to system memory before freeing the dmirror struct. The function is moved earlier in the file to avoid a forward declaration.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46280 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1827 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1827