Most recent entries from all

bdu:2024-06527

2026-10-03T19:45:00.562578+00:00

bdu:2024-06527

certfr-2024-avi-0693 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…

2026-10-03T19:45:00.562637+00:00

certfr-2024-avi-0693

EUVD-2026-310152

2026-10-03T19:45:00.562658+00:00

EUVD-2026-310152

fkie_cve-2022-48793

2026-10-03T19:45:00.562671+00:00

In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: nSVM: fix potential NULL derefernce on nested migration

Turns out that due to review feedback and/or rebases I accidentally moved the call to nested_svm_load_cr3 to be too early, before the NPT is enabled, which is very wrong to do.

KVM can't even access guest memory at that point as nested NPT is needed for that, and of course it won't initialize the walk_mmu, which is main issue the patch was addressing.

Fix this for real.

GHSA-p5hp-9793-2w9c

2026-10-03T19:45:00.562707+00:00

In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: nSVM: fix potential NULL derefernce on nested migration

Turns out that due to review feedback and/or rebases I accidentally moved the call to nested_svm_load_cr3 to be too early, before the NPT is enabled, which is very wrong to do.

KVM can't even access guest memory at that point as nested NPT is needed for that, and of course it won't initialize the walk_mmu, which is main issue the patch was addressing.

Fix this for real.

RHSA-2024:5692 — Red Hat Security Advisory: kernel security update

2026-10-03T19:45:00.562728+00:00

kernel: ipc/mqueue, msg, sem: avoid relying on a stack reference past its expiry kernel: mISDN: fix possible use-after-free in HFC_cleanup() kernel: isdn: mISDN: Fix sleeping function called from invalid context kernel: KVM: x86: nSVM: fix potential NULL derefernce on nested migration kernel: perf: Fix list corruption in perf_cgroup_switch() kernel: smb: client: fix potential OOBs in smb2_parse_contexts() kernel: net/sched: act_ct: fix skb leak and crash on ooo frags kernel: platform/x86: wmi: Fix opening of char device kernel: wifi: iwlwifi: dbg-tlv: ensure NUL termination kernel: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() kernel: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). kernel: wifi: nl80211: don't free NULL coalescing rule kernel: gfs2: Fix potential glock use-after-free on unmount

SUSE-SU-2024:2894-1 — Security update for the Linux Kernel

2026-10-03T19:45:00.562771+00:00

Security update for the Linux Kernel

UBUNTU-CVE-2022-48793

2026-10-03T19:45:00.562965+00:00

Affected: 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 61 more

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: nSVM: fix potential NULL derefernce on nested migration Turns out that due to review feedback and/or rebases I accidentally moved the call to nested_svm_load_cr3 to be too early, before the NPT is enabled, which is very wrong to do. KVM can't even access guest memory at that point as nested NPT is needed for that, and of course it won't initialize the walk_mmu, which is main issue the patch was addressing. Fix this for real.

WID-SEC-W-2024-1625 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

2026-10-03T19:45:00.563061+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.