Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49549

x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails

Medium5.5EPSS 0.27%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails In mce_threshold_create_device(), if threshold_create_bank() fails, the previously allocated threshold banks array @bp will be leaked because the call to mce_threshold_remove_device() will not free it. This happens because mce_threshold_remove_device() fetches the pointer through the threshold_banks per-CPU variable but bp is written there only after the bank creation is successful, and not before, when threshold_create_bank() fails. Add a helper which unwinds all the bank creation work previously done and pass into it the previously allocated threshold banks array for freeing. [ bp: Massage. ]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 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-49549, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.27% · top 81% of all CVEs (7 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.

Weakness

Affected products

  • Linux · Linux

    • affected 6458de97fc15530b54477c4e2b70af653e8ac3d9 – < b4acb8e7f1594607bc9017ef0aacb40b24a003d6
    • affected 6458de97fc15530b54477c4e2b70af653e8ac3d9 – < cc0dd4456f9573bf8af9b4d8754433918e809e1e
    • affected 6458de97fc15530b54477c4e2b70af653e8ac3d9 – < 9708f1956eeb70c86943e0bc62fa3b0101b59616
    • affected 6458de97fc15530b54477c4e2b70af653e8ac3d9 – < 396b8e7ab2a99ddac57d3522b3da5e58cb608d37
    • affected 6458de97fc15530b54477c4e2b70af653e8ac3d9 – < e5f28623ceb103e13fc3d7bd45edf9818b227fd0
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.121 – ≤ 5.10.*
    • unaffected 5.15.46 – ≤ 5.15.*
    • unaffected 5.17.14 – ≤ 5.17.*
    • unaffected 5.18.3 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References (5)

Sources

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

Badge for a README or a ticket

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

Record last updated .