Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

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 0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe, 0658b09cba7fe866c6cd70cd2dcdfdcabe80328f, 3893e1fcf6f306b327a8358dcd1cbd077989a240.

Low priority for now. Upgrade to Linux Linux 0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe, 0658b09cba7fe866c6cd70cd2dcdfdcabe80328f, 3893e1fcf6f306b327a8358dcd1cbd077989a240 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: Check the interrupt is still ours before migrating it vgic_prune_ap_list() drops both ap_list_lock and irq_lock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity is unchanged (target_vcpu == vgic_target_oracle(irq)) before moving the interrupt, which assumes that an interrupt whose affinity is preserved is still queued on this vCPU's ap_list. That assumption no longer holds if the interrupt is taken off the ap_list while the locks are dropped. vgic_flush_pending_lpis() removes the interrupt from the list and sets irq->vcpu to NULL, but leaves enabled/pending/target_vcpu untouched. As the interrupt is still enabled and pending, vgic_target_oracle() returns the same target_vcpu, so the affinity check passes and list_del() is run a second time on an entry that has already been removed. Also check that the interrupt is still assigned to this vCPU (irq->vcpu == vcpu) before moving it.

CriticalCVSS 9.3 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 16, 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-72289

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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.

Running WordPress? Scan your site free with WP Lens

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.7affected
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before 3893e1fcf6f306b327a8358dcd1cbd077989a240affected · git
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before cb3efe1a354f1638726725c3ecee1ce8d1a7e2dcaffected · git
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before da2d249a39a1881681c303ceea33f38ba1c5bbebaffected · git
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before 654be81c4c637af12709d47c7efc3302cd336513affected · git
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before e363c0bc0226dc5ea5046a88e9a6864b82c45399affected · git
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before 79fdd2aa774e44847cd9bb7edc811e73e3dc7bfeaffected · git
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before 0658b09cba7fe866c6cd70cd2dcdfdcabe80328faffected · git
    • 0919e84c0fc1fc73525fdcedefab89ea8460f697 and later · before 0074b82cdfcb5fd13710a0ac308ade68ac6f6fbeaffected · git
    • before 4.7not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2

+96

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-72286Aug 15, 2026 · KVM: SEV: Do not allow intra-host migration/mirroring of SNP VMs
    35Monitor
  • ← EarlierCVE-2026-72288Aug 15, 2026 · KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling
    37Monitor
  • Later →CVE-2026-72296Aug 15, 2026 · net: ife: require ETH_HLEN to be pullable in ife_decode()
    36Monitor

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 Linux0074b82cdfcb5fd13710a0ac308ade68ac6f6fbeVendor (CNA)
Linux Linux0658b09cba7fe866c6cd70cd2dcdfdcabe80328fVendor (CNA)
Linux Linux3893e1fcf6f306b327a8358dcd1cbd077989a240Vendor (CNA)
Linux Linux654be81c4c637af12709d47c7efc3302cd336513Vendor (CNA)
Linux Linux79fdd2aa774e44847cd9bb7edc811e73e3dc7bfeVendor (CNA)
Linux Linuxcb3efe1a354f1638726725c3ecee1ce8d1a7e2dcVendor (CNA)
Linux Linuxda2d249a39a1881681c303ceea33f38ba1c5bbebVendor (CNA)
Linux Linuxe363c0bc0226dc5ea5046a88e9a6864b82c45399Vendor (CNA)
almalinux:kernel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+5

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.

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

All records