Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

CriticalCVSS 9.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 37/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 7258770e5814f15e8308ebda82ac9acf6964ba8e, 7328cff91703ac4e93c200b20cebaa36d2f314ed, 77c61235d66246dd6a5f55587f0afc273d832775.

Low priority for now. Upgrade to Linux Linux 7258770e5814f15e8308ebda82ac9acf6964ba8e, 7328cff91703ac4e93c200b20cebaa36d2f314ed, 77c61235d66246dd6a5f55587f0afc273d832775 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

Published
Aug 15, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72288

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.8affected
    • 5dd4b924e390af426e424d5e52c1b4d1566af817 and later · before 7328cff91703ac4e93c200b20cebaa36d2f314edaffected · git
    • 5dd4b924e390af426e424d5e52c1b4d1566af817 and later · before eb74f3feb68e64cf69f86cb806a15d8cfb6757f4affected · git
    • 5dd4b924e390af426e424d5e52c1b4d1566af817 and later · before 77c61235d66246dd6a5f55587f0afc273d832775affected · git
    • 5dd4b924e390af426e424d5e52c1b4d1566af817 and later · before d19dca8194ebed371e624331c6be2cb73b562cafaffected · git
    • 5dd4b924e390af426e424d5e52c1b4d1566af817 and later · before b1a89d12d35a8256d2b170ced0b1c86851f3def2affected · git
    • 5dd4b924e390af426e424d5e52c1b4d1566af817 and later · before 7258770e5814f15e8308ebda82ac9acf6964ba8eaffected · git
    • before 4.8not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.180.1.el8_104.18.0-553.180.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.180.1.rt7.521.el8_104.18.0-553.180.1.rt7.521.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72284Aug 15, 2026 · KVM: x86: Ignore pending PV EOI if the vCPU has since disabled PV EOIs
    28Monitor
  • ← EarlierCVE-2026-72286Aug 15, 2026 · KVM: SEV: Do not allow intra-host migration/mirroring of SNP VMs
    35Monitor
  • Later →CVE-2026-72289Aug 15, 2026 · KVM: arm64: vgic: Check the interrupt is still ours before migrating it
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux7258770e5814f15e8308ebda82ac9acf6964ba8eVendor (CNA)
Linux Linux7328cff91703ac4e93c200b20cebaa36d2f314edVendor (CNA)
Linux Linux77c61235d66246dd6a5f55587f0afc273d832775Vendor (CNA)
Linux Linuxb1a89d12d35a8256d2b170ced0b1c86851f3def2Vendor (CNA)
Linux Linuxd19dca8194ebed371e624331c6be2cb73b562cafVendor (CNA)
Linux Linuxeb74f3feb68e64cf69f86cb806a15d8cfb6757f4Vendor (CNA)
almalinux:kernel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux7.1.5-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.58.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records