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:28:32 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-11388 bdu:2026-11388 https://cve.radiocsirt.org/vuln/bdu:2026-11388 https://cve.radiocsirt.org/vuln/bell-cve-2026-64561 <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-64561 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1029 certfr-2026-avi-1029 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1029 https://cve.radiocsirt.org/vuln/euvd-2026-359846 EUVD-2026-359846 https://cve.radiocsirt.org/vuln/euvd-2026-359846 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64561 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: x86: Check for invalid/obsolete root *after* making MMU pages available</p> <p>Check for a &#34;stale&#34; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is &#34;fine&#34;, but because child shadow pages inherit their parent&#39;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM&#39;s invariant that invalid pages are never on the list of active MMU pages.</p> <p>Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, &#34;KVM: MMU: ignore zapped root pagetables&#34;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can&#39;t be on the list of active pages.</p> <p>Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: x86: Check for invalid/obsolete root *after* making MMU pages available</p> <p>Check for a &#34;stale&#34; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is &#34;fine&#34;, but because child shadow pages inherit their parent&#39;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM&#39;s invariant that invalid pages are never on the list of active MMU pages.</p> <p>Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, &#34;KVM: MMU: ignore zapped root pagetables&#34;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can&#39;t be on the list of active pages.</p> <p>Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-64561 https://cve.radiocsirt.org/vuln/ghsa-hp26-g45f-hxp5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: x86: Check for invalid/obsolete root *after* making MMU pages available</p> <p>Check for a &#34;stale&#34; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is &#34;fine&#34;, but because child shadow pages inherit their parent&#39;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM&#39;s invariant that invalid pages are never on the list of active MMU pages.</p> <p>Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, &#34;KVM: MMU: ignore zapped root pagetables&#34;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can&#39;t be on the list of active pages.</p> <p>Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: x86: Check for invalid/obsolete root *after* making MMU pages available</p> <p>Check for a &#34;stale&#34; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is &#34;fine&#34;, but because child shadow pages inherit their parent&#39;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM&#39;s invariant that invalid pages are never on the list of active MMU pages.</p> <p>Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, &#34;KVM: MMU: ignore zapped root pagetables&#34;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can&#39;t be on the list of active pages.</p> <p>Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.</p> https://cve.radiocsirt.org/vuln/ghsa-hp26-g45f-hxp5 https://cve.radiocsirt.org/vuln/msrc_cve-2026-64561 msrc_CVE-2026-64561 https://cve.radiocsirt.org/vuln/msrc_cve-2026-64561 https://cve.radiocsirt.org/vuln/oesa-2026-3704 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es):</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: hns3: add VLAN id validation before using</p> <p>Currently, the VLAN id may be used without validation when receive a VLAN configuration mailbox from VF. The length of vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause out-of-bounds memory access once the VLAN id is bigger than or equal to VLAN_N_VID.</p> <p>Therefore, VLAN id needs to be checked to ensure it is within the range of VLAN_N_VID.(CVE-2025-71112)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix string copying in parse_apply_sb_mount_options()</p> <p>strscpy_pad() can&amp;apos;t be used to copy a non-NUL-term string into a NUL-term string of possibly bigger size. Commit 0efc5990bca5 (&amp;quot;string.h: Introduce memtostr() and memtostr_pad()&amp;quot;) provides additional information in that regard. So if this happens, the following warning is observed:</p> <p>strnlen: detected buffer overflow: 65 byte read of buffer size 64 WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Modules linked in: CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Call Trace: &amp;lt;TASK&amp;gt; __fortify_panic+0x1f/0x30 lib/s…</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es):</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: hns3: add VLAN id validation before using</p> <p>Currently, the VLAN id may be used without validation when receive a VLAN configuration mailbox from VF. The length of vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause out-of-bounds memory access once the VLAN id is bigger than or equal to VLAN_N_VID.</p> <p>Therefore, VLAN id needs to be checked to ensure it is within the range of VLAN_N_VID.(CVE-2025-71112)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix string copying in parse_apply_sb_mount_options()</p> <p>strscpy_pad() can&amp;apos;t be used to copy a non-NUL-term string into a NUL-term string of possibly bigger size. Commit 0efc5990bca5 (&amp;quot;string.h: Introduce memtostr() and memtostr_pad()&amp;quot;) provides additional information in that regard. So if this happens, the following warning is observed:</p> <p>strnlen: detected buffer overflow: 65 byte read of buffer size 64 WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Modules linked in: CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Call Trace: &amp;lt;TASK&amp;gt; __fortify_panic+0x1f/0x30 lib/s…</p> https://cve.radiocsirt.org/vuln/oesa-2026-3704 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1 <p>kernel-devel-7.1.7-1.1 on GA media</p> <p>kernel-devel-7.1.7-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1 https://cve.radiocsirt.org/vuln/rhsa-2026:45116 <p>kernel: KVM: x86: Don&#39;t (re)check L1 intercepts when completing userspace I/O kernel: tipc: fix double-free in tipc_buf_append() kernel: dm log: fix out-of-bounds write due to region_count overflow kernel: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available</p> <p>kernel: KVM: x86: Don&#39;t (re)check L1 intercepts when completing userspace I/O kernel: tipc: fix double-free in tipc_buf_append() kernel: dm log: fix out-of-bounds write due to region_count overflow kernel: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available</p> https://cve.radiocsirt.org/vuln/rhsa-2026:45116 https://cve.radiocsirt.org/vuln/rlsa-2026:45114 <p><strong>Affected:</strong> Rocky Linux:10: kernel</p> <p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p> <p>Security Fix(es):</p> <p>* kernel: fs/notify: call exportfs_encode_fid with s_umount (CVE-2025-40237) * kernel: scsi: core: Wake up the error handler when final completions race against each other (CVE-2026-23110) * kernel: rtnetlink: add missing netlink_ns_capable() check for peer netns (CVE-2026-31692) * kernel: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels (CVE-2026-46099) * kernel: futex: Drop CLONE_THREAD requirement for private default hash alloc (CVE-2026-52973) * kernel: dm log: fix out-of-bounds write due to region_count overflow (CVE-2026-53059)</p> <p><strong>Affected:</strong> Rocky Linux:10: kernel</p> <p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p> <p>Security Fix(es):</p> <p>* kernel: fs/notify: call exportfs_encode_fid with s_umount (CVE-2025-40237) * kernel: scsi: core: Wake up the error handler when final completions race against each other (CVE-2026-23110) * kernel: rtnetlink: add missing netlink_ns_capable() check for peer netns (CVE-2026-31692) * kernel: net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels (CVE-2026-46099) * kernel: futex: Drop CLONE_THREAD requirement for private default hash alloc (CVE-2026-52973) * kernel: dm log: fix out-of-bounds write due to region_count overflow (CVE-2026-53059)</p> https://cve.radiocsirt.org/vuln/rlsa-2026:45114 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64561 <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 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available Check for a &#34;stale&#34; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is &#34;fine&#34;, but because child shadow pages inherit their parent&#39;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM&#39;s invariant that invalid pages are never on the list of active MMU pages. Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, &#34;KVM: MMU: ignore zapped root pagetables&#34;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can&#39;t be on the list of active pages. Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.</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 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Check for invalid/obsolete root *after* making MMU pages available Check for a &#34;stale&#34; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is &#34;fine&#34;, but because child shadow pages inherit their parent&#39;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM&#39;s invariant that invalid pages are never on the list of active MMU pages. Note, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, &#34;KVM: MMU: ignore zapped root pagetables&#34;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can&#39;t be on the list of active pages. Note #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64561 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2640 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um vertrauliche Informationen offenzulegen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder seine Rechte zu erweitern.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um vertrauliche Informationen offenzulegen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder seine Rechte zu erweitern.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2640