← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-72288

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-72288

Key Details

CVECVE-2026-72288
CVSS Score / Version
9.3 (Critical) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is none; user interaction is none; scope is changed; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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 RD to disable its LPIs

- vcpu-C moves I from B to C

If the last two race nicely enough, vgic_prune_ap_list() can drop

the irq and AP list locks, reacquire them, and in the interval

the irq has been freed. UAF follows.

The fix is two-fold:

- Before dropping the irq and ap_list locks, take a reference on

the irq

- Do not try to handle migration of the pending bit: there is no

expectation that this state is retained, as per the architecture

With that, we're sure that the interrupt is still around, and we

safely remove it from the AP list as it has no target at this

stage (unless another interrupt fires, but that's another story). (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-72288
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-72288
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.