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-2021-47058regmap: set debugfs_name to NULL after it is freed

Description

In the Linux kernel, the following vulnerability has been resolved: regmap: set debugfs_name to NULL after it is freed There is a upstream commit cffa4b2122f5("regmap:debugfs: Fix a memory leak when calling regmap_attach_dev") that adds a if condition when create name for debugfs_name. With below function invoking logical, debugfs_name is freed in regmap_debugfs_exit(), but it is not created again because of the if condition introduced by above commit. regmap_reinit_cache() regmap_debugfs_exit() ... regmap_debugfs_init() So, set debugfs_name to NULL after it is freed.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years 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-2021-47058, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (18 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: High 7.8.

Affected products

  • Linux · Linux

    • affected 5b654b03007917f3f1015b2a5c288c1ea6ae8f65 – < 2dc1554d5f0fdaf47cc5bea442b84b9226fea867
    • affected 480c5e9c7e4c76c01d5f1f7b73832d7b77e6b427 – < d8897f7b2283a500666c85ef06e820df38ed7b52
    • affected c9698380b01aed3281160d3ab25749b57d6913b8 – < eb949f891226c012138ffd9df90d1e509f428ae6
    • affected cffa4b2122f5f3e53cf3d529bbc74651f95856d5 – < c764e375ae647832de1ee73d43a4bb3ef8a8f43d
    • affected cffa4b2122f5f3e53cf3d529bbc74651f95856d5 – < b9e569ae1da3a113b3acee8703c94777fd20938a
    • affected cffa4b2122f5f3e53cf3d529bbc74651f95856d5 – < e41a962f82e7afb5b1ee644f48ad0b3aee656268
    • affected 4.19.168 – < 4.19.191
    • affected 5.4.90 – < 5.4.119
    • affected 5.10.8 – < 5.10.37
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 4.19.191 – ≤ 4.19.*
    • unaffected 5.4.119 – ≤ 5.4.*
    • unaffected 5.10.37 – ≤ 5.10.*
    • unaffected 5.11.21 – ≤ 5.11.*
    • unaffected 5.12.4 – ≤ 5.12.*
    • unaffected 5.13 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .