In the Linux kernel, the following vulnerability has been resolved: iommu/sva: Set handle->dev before the SVA handle is visible… (CVE-2026-89451)
A vulnerability in the Linux kernel's iommu/sva subsystem was resolved by ensuring the SVA handle's device pointer is set before the handle becomes visible to concurrent operations. The issue involved a race condition where a bind operation could reuse a handle with an uninitialized device pointer, potentially leading to a NULL pointer dereference during unbind operations.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's iommu/sva code arises because iommu_attach_device_pasid() installs a new SVA attach handle in the group PASID lookup before iommu_sva_bind_device() returns. Since handle->dev was initialized only after dropping the iommu_sva_lock, a concurrent bind could find and reuse the same handle with a NULL dev pointer. This could cause a NULL pointer dereference in iommu_sva_unbind_device() when accessing handle->dev->iommu_group. The fix involves initializing handle->dev before releasing iommu_sva_lock, ensuring any visible SVA handle is fully initialized.
Potential Impact
The vulnerability could lead to a NULL pointer dereference in kernel space, which may cause system instability or crashes. There is no information about exploitation in the wild or privilege escalation. The impact is limited to potential denial of service due to kernel crashes.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to initialize handle->dev before releasing iommu_sva_lock, preventing the race condition. Users should apply the official kernel update that includes this fix. No additional mitigation steps are indicated.
In the Linux kernel, the following vulnerability has been resolved: iommu/sva: Set handle->dev before the SVA handle is visible… (CVE-2026-89451)
Description
A vulnerability in the Linux kernel's iommu/sva subsystem was resolved by ensuring the SVA handle's device pointer is set before the handle becomes visible to concurrent operations. The issue involved a race condition where a bind operation could reuse a handle with an uninitialized device pointer, potentially leading to a NULL pointer dereference during unbind operations.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's iommu/sva code arises because iommu_attach_device_pasid() installs a new SVA attach handle in the group PASID lookup before iommu_sva_bind_device() returns. Since handle->dev was initialized only after dropping the iommu_sva_lock, a concurrent bind could find and reuse the same handle with a NULL dev pointer. This could cause a NULL pointer dereference in iommu_sva_unbind_device() when accessing handle->dev->iommu_group. The fix involves initializing handle->dev before releasing iommu_sva_lock, ensuring any visible SVA handle is fully initialized.
Potential Impact
The vulnerability could lead to a NULL pointer dereference in kernel space, which may cause system instability or crashes. There is no information about exploitation in the wild or privilege escalation. The impact is limited to potential denial of service due to kernel crashes.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to initialize handle->dev before releasing iommu_sva_lock, preventing the race condition. Users should apply the official kernel update that includes this fix. No additional mitigation steps are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mm8r-pp22-xwxg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89451"]
Threat ID: 6aa4a02255bf5e2cf5a869a8
Added to database: 09/12/2026, 00:43:14 UTC
Last enriched: 09/12/2026, 01:16:47 UTC
Last updated: 09/12/2026, 01:16:47 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.