iommu/vt-d: Fix RB-tree corruption in probe error path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 43bd9e6d5513cb1edbafdeef146a1edc3aaced56, Kernel d16923a45d4d08367650fdc3451c89299ab6ac5a and Kernel f5102e0fc3c6dc8685549891a96e4589fdb3e211.
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().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <43bd9e6d5513cb1edbafdeef146a1edc3aaced56, >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <d16923a45d4d08367650fdc3451c89299ab6ac5a, >=4f1492efb495bcef34c9ee8a94af81e6cea5abf4 <f5102e0fc3c6dc8685549891a96e4589fdb3e211 | 43bd9e6d5513cb1edbafdeef146a1edc3aaced56, d16923a45d4d08367650fdc3451c89299ab6ac5a, f5102e0fc3c6dc8685549891a96e4589fdb3e211 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket