Answer in brief
CVE-2026-72288 records a Unknown severity vulnerability in KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5dd4b924e390af426e424d5e52c1b4d1566af817 <d19dca8194ebed371e624331c6be2cb73b562caf || >=5dd4b924e390af426e424d5e52c1b4d1566af817 <b1a89d12d35a8256d2b170ced0b1c86851f3def2 || >=5dd4b924e390af426e424d5e52c1b4d1566af817 <7258770e5814f15e8308ebda82ac9acf6964ba8e | d19dca8194ebed371e624331c6be2cb73b562caf, b1a89d12d35a8256d2b170ced0b1c86851f3def2, 7258770e5814f15e8308ebda82ac9acf6964ba8e |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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).
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72288 records a Unknown severity vulnerability in KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5dd4b924e390af426e424d5e52c1b4d1566af817 <d19dca8194ebed371e624331c6be2cb73b562caf || >=5dd4b924e390af426e424d5e52c1b4d1566af817 <b1a89d12d35a8256d2b170ced0b1c86851f3def2 || >=5dd4b924e390af426e424d5e52c1b4d1566af817 <7258770e5814f15e8308ebda82ac9acf6964ba8e | d19dca8194ebed371e624331c6be2cb73b562caf, b1a89d12d35a8256d2b170ced0b1c86851f3def2, 7258770e5814f15e8308ebda82ac9acf6964ba8e |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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).
Quoted source text, attributed separately from HOL analysis.