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-50482

iommu/vt-d: Clean up si_domain in the init_dmars() error path

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Clean up si_domain in the init_dmars() error path A splat from kmem_cache_destroy() was seen with a kernel prior to commit ee2653bbe89d ("iommu/vt-d: Remove domain and devinfo mempool") when there was a failure in init_dmars(), because the iommu_domain cache still had objects. While the mempool code is now gone, there still is a leak of the si_domain memory if init_dmars() fails. So clean up si_domain in the init_dmars() error path.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 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-50482, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.16% · top 94% of all CVEs (11 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 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 – < 749bea542b67513e99240dc58bbfc099e842d508
    • affected 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 – < 5cecfe151874b835331efe086bbdcaeaf64f6b90
    • affected 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 – < 724483b585a1b1e063d42ac5aa835707ff2ec165
    • affected 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 – < d74196bb278b8f8af88e16bd595997dfa3d6fdb0
    • affected 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 – < 0365d6af75f9f2696e94a0fef24a2c8464c037c8
    • affected 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 – < c4ad3ae4c6be9d8b0701761c839771116bca6ea3
    • affected 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 – < 620bf9f981365c18cc2766c53d92bf8131c63f32
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 4.14.298 – ≤ 4.14.*
    • unaffected 4.19.264 – ≤ 4.19.*
    • unaffected 5.4.221 – ≤ 5.4.*
    • unaffected 5.10.152 – ≤ 5.10.*
    • unaffected 5.15.76 – ≤ 5.15.*
    • unaffected 6.0.6 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .