1. Home
  2. Vulnerabilities
  3. CVE-2026-74355
0.0
NA
CVE-2026-74355
iommu/vt-d: Fix RB-tree corruption in probe error path
Overview
Description

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix RB-tree corruption in probe error path The info->node RB-tree member is zero-initialized via kzalloc. If a device does not support ATS, the device_rbtree_insert() call is skipped. If a subsequent probe step fails, the error path jumps to device_rbtree_remove(), which misinterprets the zeroed node as a tree root and corrupts the device RB-tree. Fix this by explicitly initializing the RB-node as empty using RB_CLEAR_NODE() during initialization and guarding the removal with RB_EMPTY_NODE().

Details
INFO

Published Date :

Aug. 15, 2026, 6:22 a.m.

Last Modified :

Aug. 15, 2026, 6:22 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Impact
Affected Products

The following products are affected by CVE-2026-74355 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

: Total Affected Vendor : 0 | Products : 0
Solution
Initialize RB-tree nodes correctly and guard removals to prevent corruption.
  • Initialize RB-tree nodes as empty using RB_CLEAR_NODE().
  • Guard RB-tree removals with RB_EMPTY_NODE().
  • Apply the kernel patch for iommu/vt-d.
References
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-74355.

URL Resource
https://git.kernel.org/stable/c/43bd9e6d5513cb1edbafdeef146a1edc3aaced56
https://git.kernel.org/stable/c/d16923a45d4d08367650fdc3451c89299ab6ac5a
https://git.kernel.org/stable/c/f5102e0fc3c6dc8685549891a96e4589fdb3e211
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-74355 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-74355 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-74355 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2026-74355 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 15, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4f1492efb495bcef34c9ee8a94af81e6cea5abf4', 'lessThan': 'f5102e0fc3c6dc8685549891a96e4589fdb3e211', 'versionType': 'git'}, {'status': 'affected', 'version': '4f1492efb495bcef34c9ee8a94af81e6cea5abf4', 'lessThan': 'd16923a45d4d08367650fdc3451c89299ab6ac5a', 'versionType': 'git'}, {'status': 'affected', 'version': '4f1492efb495bcef34c9ee8a94af81e6cea5abf4', 'lessThan': '43bd9e6d5513cb1edbafdeef146a1edc3aaced56', 'versionType': 'git'}], 'programFiles': ['drivers/iommu/intel/iommu.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.15'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.15', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.5', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/iommu/intel/iommu.c'], 'defaultStatus': 'affected'}]
    Added Description In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix RB-tree corruption in probe error path The info->node RB-tree member is zero-initialized via kzalloc. If a device does not support ATS, the device_rbtree_insert() call is skipped. If a subsequent probe step fails, the error path jumps to device_rbtree_remove(), which misinterprets the zeroed node as a tree root and corrupts the device RB-tree. Fix this by explicitly initializing the RB-node as empty using RB_CLEAR_NODE() during initialization and guarding the removal with RB_EMPTY_NODE().
    Added Reference https://git.kernel.org/stable/c/43bd9e6d5513cb1edbafdeef146a1edc3aaced56
    Added Reference https://git.kernel.org/stable/c/d16923a45d4d08367650fdc3451c89299ab6ac5a
    Added Reference https://git.kernel.org/stable/c/f5102e0fc3c6dc8685549891a96e4589fdb3e211
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CVSS
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.