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

firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle

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

Description

In the Linux kernel, the following vulnerability has been resolved: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add() If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Fix this issue by calling kobject_put().

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-49370, 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.29% · top 78% 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 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < a9bfb37d6ba7c376b0d53337a4c5f5ff324bd725
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < ed38d04342dfbe9e5aca745c8b5eb4188a74f0ef
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < c66cc3c62870a27ea8f060a7e4c1ad8d26dd3f0d
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < a724634b2a49f6ff0177a9e19a5a92fc1545e1b7
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < 985706bd3bbeffc8737bc05965ca8d24837bc7db
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < fdffa4ad8f6bf1ece877edfb807f2b2c729d8578
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < 3ba359ebe914ac3f8c6c832b28007c14c39d3766
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < ec752973aa721ee281d5441e497364637c626c7b
    • affected 948af1f0bbc8526448e8cbe3f8d3bf211bdf5181 – < 660ba678f9998aca6db74f2dd912fa5124f0fa31
  • Linux · Linux

    • affected 2.6.39
    • unaffected < 2.6.39
    • unaffected 4.9.318 – ≤ 4.9.*
    • unaffected 4.14.283 – ≤ 4.14.*
    • unaffected 4.19.247 – ≤ 4.19.*
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.122 – ≤ 5.10.*
    • unaffected 5.15.47 – ≤ 5.15.*
    • unaffected 5.17.15 – ≤ 5.17.*
    • unaffected 5.18.4 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References (9)

Sources

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

Badge for a README or a ticket

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

Record last updated .