Skip to content
Fencer Vulns
medium 5.5

CVE-2021-47516 json

nfp: Fix memory leak in nfp_cpp_area_cache_add()

published 2024-05-24 2 y ago modified 2026-06-17 4 mo ago also EUVD-2021-34520

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

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 }

Patch / fix

  • Linux Linux 4.14.258, 4.19.221, 5.4.165, 5.10.85, 5.15.8, 5.16
  • linux Debian 14, Debian 13, Debian 12 5.15.15-1

debian advisories DEBIAN-CVE-2021-47516

  • linux Ubuntu 18.04 LTS 4.15.0-169.177
  • linux Ubuntu 20.04 LTS 5.4.0-100.113
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1121.129
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1066.69
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1065.69
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1015.16
  • linux-kvm Ubuntu 18.04 LTS 4.15.0-1107.109
  • linux-kvm Ubuntu 20.04 LTS 5.4.0-1056.58

ubuntu advisories UBUNTU-CVE-2021-47516

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-syms SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.225.1
  • kernel-source SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.225.1
  • kernel-default SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +2 more 4.12.14-122.225.1
  • kernel-obs-build SLE Software Development Kit 12 SP5 4.12.14-122.225.1
  • kernel-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.194.1
  • kernel-syms-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.194.1
  • kernel-source-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.194.1
  • kernel-rt SLE Real Time 12 SP5 4.12.14-10.197.1

suse advisories SUSE-SU-2024:2940-1SUSE-SU-2024:2901-1SUSE-SU-2024:2892-1SUSE-SU-2024:2190-1SUSE-SU-2024:2189-1SUSE-SU-2024:2185-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-47516 updated cvss 4.1

kernel: nfp: Fix memory leak in nfp_cpp_area_cache_add()

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix available
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.