Answer in brief
CVE-2026-74355 records a Unknown severity vulnerability in iommu/vt-d: Fix RB-tree corruption in probe error path. 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <f5102e0fc3c6dc8685549891a96e4589fdb3e211 || >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <d16923a45d4d08367650fdc3451c89299ab6ac5a || >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <43bd9e6d5513cb1edbafdeef146a1edc3aaced56 | f5102e0fc3c6dc8685549891a96e4589fdb3e211, d16923a45d4d08367650fdc3451c89299ab6ac5a, 43bd9e6d5513cb1edbafdeef146a1edc3aaced56 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74355 records a Unknown severity vulnerability in iommu/vt-d: Fix RB-tree corruption in probe error path. 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <f5102e0fc3c6dc8685549891a96e4589fdb3e211 || >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <d16923a45d4d08367650fdc3451c89299ab6ac5a || >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <43bd9e6d5513cb1edbafdeef146a1edc3aaced56 | f5102e0fc3c6dc8685549891a96e4589fdb3e211, d16923a45d4d08367650fdc3451c89299ab6ac5a, 43bd9e6d5513cb1edbafdeef146a1edc3aaced56 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.