iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- 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 4.14.265, 4.19.228, 5.4.178, 5.8
- 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() After commit e3beca48a45b ("irqdomain/treewide: Keep firmware node unconditionally allocated"). For tear down scenario, fn is only freed after fail to allocate ir_domain, though it also should be freed in case dmar_enable_qi returns error. Besides free fn, irq_domain and ir_msi_domain need to be removed as well if intel_setup_irq_remapping fails to enable queued invalidation. Improve the rewinding path by add out_free_ir_domain and out_free_fwnode lables per Baolu's suggestion.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 4.14.190 · fixed in 4.14.265; From 4.19.135 · fixed in 4.19.228; From 5.4.54 · fixed in 5.4.178; From 5.7.11 · fixed in 5.8
- Linux Linux
5.8
References 7
git.kernel.org
- stable/c/a0c685ba99961b1dd894b2e470e692a539770f6d
- stable/c/a31cb1f0fb6caf46ffe88c41252b6b7a4ee062d9
- stable/c/5c43d46daa0d2928234dd2792ebebc35d29ee2d1
- stable/c/9d9995b0371e4e8c18d4f955479e5d47efe7b2d4
- stable/c/336d096b62bdc673e852b6b80d5072d7888ce85d
- stable/c/b62eceb5f8f08815fe3f945fc55bbf997c344ecd
- stable/c/99e675d473eb8cf2deac1376a0f840222fc1adcf