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-49821mISDN: fix possible memory leak in mISDN_dsp_element_register()

Description

In the Linux kernel, the following vulnerability has been resolved: mISDN: fix possible memory leak in mISDN_dsp_element_register() Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, use put_device() to give up the reference, so that the name can be freed in kobject_cleanup() when the refcount is 0. The 'entry' is going to be freed in mISDN_dsp_dev_release(), so the kfree() is removed. list_del() is called in mISDN_dsp_dev_release(), so it need be initialized.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 18 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-49821, 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.20% · top 90% of all CVEs (19 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 1fa5ae857bb14f6046205171d98506d8112dd74e – < bbd53d05c4c892080ef3b617eff4f57903acecb9
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < b119bedbefb7dd9ed8bf8cb9f1056504250d610e
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 727ed7d28348c026c7ef4d852f3d0e5054d376e8
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 0f2c681900a01e3f23789bca26d88268c3d5b51d
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 083a2c9ef82e184bdf0b9f9a1e5fc38d32afbb47
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 7a05e3929668c8cfef495c69752a9e91fac4878f
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < d4b8394725079670be309f9a35ad88a8cbbaaefd
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 98a2ac1ca8fd6eca6867726fe238d06e75eb1acd
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 4.9.334 – ≤ 4.9.*
    • unaffected 4.14.300 – ≤ 4.14.*
    • unaffected 4.19.267 – ≤ 4.19.*
    • unaffected 5.4.225 – ≤ 5.4.*
    • unaffected 5.10.156 – ≤ 5.10.*
    • unaffected 5.15.80 – ≤ 5.15.*
    • unaffected 6.0.10 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .