Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-48724iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()

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

  1. ID reserved

    By Linux

  2. Published

  3. · 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

CVSS scores of CVE-2022-48724, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS: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
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • 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
  • Linux · Linux

    • 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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48724 badge
[![CVE-2022-48724](https://cveledger.app/badge/CVE-2022-48724.svg)](https://cveledger.app/cve/CVE-2022-48724)

Record last updated .