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-47516nfp: Fix memory leak in nfp_cpp_area_cache_add()

Description

In the Linux kernel, the following vulnerability has been resolved: nfp: Fix memory leak in nfp_cpp_area_cache_add() In line 800 (#1), nfp_cpp_area_alloc() allocates and initializes a CPP area structure. But in line 807 (#2), when the cache is allocated failed, this CPP area structure is not freed, which will result in memory leak. We can fix it by freeing the CPP area when the cache is allocated failed (#2). 792 int nfp_cpp_area_cache_add(struct nfp_cpp *cpp, size_t size) 793 { 794 struct nfp_cpp_area_cache *cache; 795 struct nfp_cpp_area *area; 800 area = nfp_cpp_area_alloc(cpp, NFP_CPP_ID(7, NFP_CPP_ACTION_RW, 0), 801 0, size); // #1: allocates and initializes 802 if (!area) 803 return -ENOMEM; 805 cache = kzalloc(sizeof(*cache), GFP_KERNEL); 806 if (!cache) 807 return -ENOMEM; // #2: missing free 817 return 0; 818 }

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 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-2021-47516, by who scored it
Scored byCVSSScoreVector
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.24% · top 85% of all CVEs (16 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 4cb584e0ee7df70fd0376aee60cf701855ea8c81 – < 3e93abcdcec0436fbf0b6a88ae806902426895a2
    • affected 4cb584e0ee7df70fd0376aee60cf701855ea8c81 – < eb51f639ef3fd5498b7def290ed8681b6aadd9a7
    • affected 4cb584e0ee7df70fd0376aee60cf701855ea8c81 – < 2e0e072e62fdaf7816220af08e05c020f0fcb77a
    • affected 4cb584e0ee7df70fd0376aee60cf701855ea8c81 – < 484069b5de9d223cc1c64c6f80389a99cfef51f1
    • affected 4cb584e0ee7df70fd0376aee60cf701855ea8c81 – < f707820c09239d6f67699d9b2ff57863cc7905b0
    • affected 4cb584e0ee7df70fd0376aee60cf701855ea8c81 – < c56c96303e9289cc34716b1179597b6f470833de
  • Linux · Linux

    • affected 4.11
    • unaffected < 4.11
    • unaffected 4.14.258 – ≤ 4.14.*
    • unaffected 4.19.221 – ≤ 4.19.*
    • unaffected 5.4.165 – ≤ 5.4.*
    • unaffected 5.10.85 – ≤ 5.10.*
    • unaffected 5.15.8 – ≤ 5.15.*
    • unaffected 5.16 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .