https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 07:51:44 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46071 <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-46071 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/euvd-2026-327111 EUVD-2026-327111 https://cve.radiocsirt.org/vuln/euvd-2026-327111 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46071 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12</p> <p>svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined.</p> <p>Move vmcb_mark_dirty() to callers and drop it for vmcb12.</p> <p>This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12</p> <p>svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined.</p> <p>Move vmcb_mark_dirty() to callers and drop it for vmcb12.</p> <p>This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46071 https://cve.radiocsirt.org/vuln/ghsa-h9fc-vq2v-qf62 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12</p> <p>svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined.</p> <p>Move vmcb_mark_dirty() to callers and drop it for vmcb12.</p> <p>This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12</p> <p>svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined.</p> <p>Move vmcb_mark_dirty() to callers and drop it for vmcb12.</p> <p>This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().</p> https://cve.radiocsirt.org/vuln/ghsa-h9fc-vq2v-qf62 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46071 msrc_CVE-2026-46071 https://cve.radiocsirt.org/vuln/msrc_cve-2026-46071 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 <p>kernel-devel-7.0.11-1.1 on GA media</p> <p>kernel-devel-7.0.11-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 https://cve.radiocsirt.org/vuln/suse-su-2026:22521-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:22521-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46071 <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 154 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined. Move vmcb_mark_dirty() to callers and drop it for vmcb12. This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().</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 154 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined. Move vmcb_mark_dirty() to callers and drop it for vmcb12. This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46071 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700 <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> <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> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700