CVE-2026-72278

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Re-translate VNCR before injecting abort KVM faults in the VNCR page with FOLLWRITE whenever the guest aborts for a write, similar to how a regular stage-2 mapping is handled. It is entirely possible that the gues...

UBUNTU-CVE-2026-72278

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Re-translate VNCR before injecting abort KVM faults in the VNCR page with FOLLWRITE whenever the guest aborts for a write, similar to how a regular stage-2 mapping is handled. It is entirely possible that the gues...

CVE-2026-72487 PCI: Check ROM header and data structure addr before accessing

In the Linux kernel, the following vulnerability has been resolved: PCI: Check ROM header and data structure addr before accessing We meet a crash when running stress-ng on x8664 machine: BUG: unable to handle page fault for address: ffa0000007f40000 RIP: 0010:pcigetromsize+0x52/0x220 Call Trace:...

CVE-2026-72341 net/mlx5e: Fix publication race for priv->channel_stats[]

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix publication race for priv-channelstats mlx5echannelstatsalloc publishes a new entry to priv-channelstats and then increments priv-statsnch as a publication token, but neither store carries any memory barrier:...

EUVD-2026-59240

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix publication race for priv-channelstats mlx5echannelstatsalloc publishes a new entry to priv-channelstats and then increments priv-statsnch as a publication token, but neither store carries any memory barrier:...

EUVD-2026-59188

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Check the interrupt is still ours before migrating it vgicpruneaplist drops both aplistlock and irqlock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity ...

CVE-2026-72289 KVM: arm64: vgic: Check the interrupt is still ours before migrating it

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Check the interrupt is still ours before migrating it vgicpruneaplist drops both aplistlock and irqlock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity ...

CVE-2026-72289

CVE-2026-72289 affects the Linux kernel (KVM on arm64) where vgic interrupt migration logic can mis-handle pending/active interrupts during lock-protected migrations. Specifically, vgic_prune_ap_list() drops ap_list_lock and irq_lock and rechecks only affinity, which can pass for an interrupt tha...

CVE-2026-72288

The CVE-2026-72288 entry concerns the Linux kernel KVM arm64 vgic race between interrupt affinity changes and LPI disabling. Under a specific sequence—LPI-I pending in vcpu-B’s AP list; vcpu-A disables LPIs via vcpu-B’s RD; vcpu-C moves I from B to C—the vgic_prune_ap_list() path can drop irq and...

CVE-2026-72289 KVM: arm64: vgic: Check the interrupt is still ours before migrating it

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Check the interrupt is still ours before migrating it vgicpruneaplist drops both aplistlock and irqlock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity ...

CVE-2026-72288 KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling Hyunwoo Kim reports some really bad races should the following situation occur: - LPI-I is pending in vcpu-B's AP list - vcpu-A writes to vcpu-B's ...

CVE-2026-72281 KVM: arm64: account pKVM reclaim against the VM mm

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: account pKVM reclaim against the VM mm Protected guest faults charge long term pins to the VM's mm. Teardown can run later from file release, where current-mm may be unrelated. Drop the charge from kvm-mm instead...

EUVD-2026-59180

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: account pKVM reclaim against the VM mm Protected guest faults charge long term pins to the VM's mm. Teardown can run later from file release, where current-mm may be unrelated. Drop the charge from kvm-mm instead...

CVE-2026-72281

The CVE-2026-72281 entry concerns the Linux kernel KVM arm64/pKVM reclaim against the VM memory manager. The issue arose because protected guest faults could pin long-term resources to the VM’s mm (memory descriptor), and teardown could execute later from file release with current->mm potentia...

CVE-2026-72281 KVM: arm64: account pKVM reclaim against the VM mm

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: account pKVM reclaim against the VM mm Protected guest faults charge long term pins to the VM's mm. Teardown can run later from file release, where current-mm may be unrelated. Drop the charge from kvm-mm instead...

CVE-2026-72279 KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR KVM currently maps the L1 VNCR into the host stage-1 by relying entirely on the permissions of the guest stage-1. At the same time, it is entirely possible that the backi...

CVE-2026-72279

The CVE-2026-72279 entry concerns the Linux kernel KVM arm64 implementation for the L1 VNCR mapping. The fix ensures that the host stage-1 mapping respects the read-only status of the guest PFN by caching PFN writability in the VNCR TLB and using this to constrain fixmap permissions. If a guest t...

CVE-2026-72280

CVE-2026-72280 concerns the Linux kernel KVM on arm64. The vulnerability arises from a logic issue where a guest could write to the ZCR_EL2 sysreg alias in a nested context if FEAT_NV2 is advertised to the L1 hypervisor. The fix is to drop the bogus WARN that could lead to a hyp_panic once hyp ve...

EUVD-2026-59178

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR KVM currently maps the L1 VNCR into the host stage-1 by relying entirely on the permissions of the guest stage-1. At the same time, it is entirely possible that the backi...

CVE-2026-72280 KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL2

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Drop bogus WARN for write to ZCREL2 It is entirely possible for a guest to write to the ZCREL2 sysreg alias while in a nested context, as it is expected if FEATNV2 is advertised to the L1 hypervisor. Get rid of th...