CVE 8.8 HIGH

iommu/vt-d: Avoid NULL pointer dereference or refcount corruption_CVE-2026-53281

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

Description

In the Linux kernel, the following vulnerability has been resolved:

iommu/vt-d: Avoid NULL pointer dereference or refcount corruption

Commit 60f030f7418d ("iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE")
fixed a NULL pointer dereference in an unlikely situation partly.

If dev_pasid is not found in the dev_pasids list, it remains NULL.
However, the teardown operations are executed unconditionally, this lead
to a NULL pointer dereference or refcount corruption.

If the domain was never attached to this IOMMU, info will be NULL, which
would cause an immediate dereference when checking --info->refcnt.

Even if info is not NULL, decrementing the refcount without having removed
a valid PASID might unbalance the count. This could lead to premature
dropping of the refcount to 0, potentially causing a use-after-free for the
remaining active devices sharing the domain.

Fix it by returning early if dev_pasid is NULL, before executing the
teardown operations.

Issue found by AI review and suggested by Kevin Tian.
https://sashiko.dev/#/patchset/20260421031347.1408890-1-zhenzhong.duan%40intel.com

AI Analysis

NULL pointer dereference or refcount corruption vulnerability in Linux kernel's iommu/vt-d component

Basic Information

ID CVE-2026-53281
Source Linux
Published Jun 26, 2026 at 19:40
Modified Jun 28, 2026 at 06:41

Affected Product

Vendor Linux
Product Linux
Version 60f030f7418d3f1d94f2fb207fe3080e1844630b
Affected Versions Linux Linux 60f030f7418d3f1d94f2fb207fe3080e1844630b
Linux Linux 60f030f7418d3f1d94f2fb207fe3080e1844630b
Linux Linux 60f030f7418d3f1d94f2fb207fe3080e1844630b
Linux Linux 68ec78beb4a3fb0877cbaaf49758c85410c05977
Linux Linux df96876be3b064aefc493f760e0639765d13ed0d
Linux Linux 6.12.57
Linux Linux 6.13.3
Linux Linux 6.14

AI Assessment

AI Score 8.8 / 10
AI Severity High
Vendor Linux Foundation
Product Linux Kernel
Version 6.12.57, 6.13.3, 6.14

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.