iommu/sva: Set handle->dev before the SVA handle is visible (CVE-2026-89451) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89451

iommu/sva: Set handle->dev before the SVA handle is visible

Answer in brief

CVE-2026-89451 records a Unknown severity vulnerability in iommu/sva: Set handle->dev before the SVA handle is visible. 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.

Published Sep 11, 2026Updated Sep 11, 2026Source checked Sep 11, 2026First seen by HOL Sep 11, 2026Material review Sep 11, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=be51b1d6bbff48c7d1943a8ff1e5a55777807f6e <bcffb1c75da8fc9d51168ff9f09d471c26507912 \|\| >=be51b1d6bbff48c7d1943a8ff1e5a55777807f6e <968e9a1f71140c86dc4092f6b361e997923f3813 \|\| >=be51b1d6bbff48c7d1943a8ff1e5a55777807f6e <37a96a30617a4c96f048a5874c00509bc4fe4d85 \|\| >=be51b1d6bbff48c7d1943a8ff1e5a55777807f6e <530f8f9c3546cb3ebee1b135375aaee08a073ebb	bcffb1c75da8fc9d51168ff9f09d471c26507912, 968e9a1f71140c86dc4092f6b361e997923f3813, 37a96a30617a4c96f048a5874c00509bc4fe4d85, 530f8f9c3546cb3ebee1b135375aaee08a073ebb
Linux/Linuxgeneric	6.2	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to bcffb1c75da8fc9d51168ff9f09d471c26507912 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 11, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: iommu/sva: Set handle->dev before the SVA handle is visible iommu_attach_device_pasid() installs the new SVA attach handle in the group PASID lookup before iommu_sva_bind_device() returns. A concurrent bind can therefore find and reuse the same handle after iommu_sva_lock is dropped. handle->dev was initialized after dropping iommu_sva_lock. This leaves a window where a racing bind can return a handle whose dev pointer is still NULL. A subsequent iommu_sva_unbind_device() can then dereference it via handle->dev->iommu_group. Initialize handle->dev before releasing iommu_sva_lock so any visible SVA handle is fully initialized.

Quoted source text, attributed separately from HOL analysis.