CVE-2022-48724iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
- 5.5MediumCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
Published
- 23 months later
· 23 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 03992c88d71ba79d956f2ed54e370e630b8750f4 – < a0c685ba99961b1dd894b2e470e692a539770f6d
- affected c0c489e5430530a7021f4c889cd5931597e4b200 – < a31cb1f0fb6caf46ffe88c41252b6b7a4ee062d9
- affected 36f7355545725c5e9400520ae33e6ee16cf78c0e – < 5c43d46daa0d2928234dd2792ebebc35d29ee2d1
- affected e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb – < 9d9995b0371e4e8c18d4f955479e5d47efe7b2d4
- affected e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb – < 336d096b62bdc673e852b6b80d5072d7888ce85d
- affected e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb – < b62eceb5f8f08815fe3f945fc55bbf997c344ecd
- affected e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb – < 99e675d473eb8cf2deac1376a0f840222fc1adcf
- affected b4198ecddb87cd955aa9e024dd656af5ceaf6196
- affected 4.14.190 – < 4.14.265
- affected 4.19.135 – < 4.19.228
- affected 5.4.54 – < 5.4.178
- affected 5.7.11 – < 5.8
- affected 5.8
- unaffected < 5.8
- unaffected 4.14.265 – ≤ 4.14.*
- unaffected 4.19.228 – ≤ 4.19.*
- unaffected 5.4.178 – ≤ 5.4.*
- unaffected 5.10.99 – ≤ 5.10.*
- unaffected 5.15.22 – ≤ 5.15.*
- unaffected 5.16.8 – ≤ 5.16.*
- unaffected 5.17 – ≤ *
References
References7
- https://git.kernel.org/stable/c/a0c685ba99961b1dd894b2e470e692a539770f6d (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/a31cb1f0fb6caf46ffe88c41252b6b7a4ee062d9 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/5c43d46daa0d2928234dd2792ebebc35d29ee2d1 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/9d9995b0371e4e8c18d4f955479e5d47efe7b2d4 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/336d096b62bdc673e852b6b80d5072d7888ce85d (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/b62eceb5f8f08815fe3f945fc55bbf997c344ecd (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/99e675d473eb8cf2deac1376a0f840222fc1adcf (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-53603 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-48724)Record last updated .