iommu/vt-d: Fix RB-tree corruption in probe error path
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.40, 7.1.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 4f1492efb495bcef34c9ee8a94af81e6cea5abf4 · fixed in f5102e0fc3c6dc8685549891a96e4589fdb3e211; From 4f1492efb495bcef34c9ee8a94af81e6cea5abf4 · fixed in d16923a45d4d08367650fdc3451c89299ab6ac5a; From 4f1492efb495bcef34c9ee8a94af81e6cea5abf4 · fixed in 43bd9e6d5513cb1edbafdeef146a1edc3aaced56
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5