Skip to content
Fencer Vulns
medium 5.5

CVE-2021-46924 json

NFC: st21nfca: Fix memory leak in device probe and remove

published 2024-02-27 2 y ago modified 2026-06-17 4 mo ago also EUVD-2021-33572

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 13%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

NFC: st21nfca: Fix memory leak in device probe and remove

'phy->pending_skb' is alloced when device probe, but forgot to free in the error handling path and remove path, this cause memory leak as follows:

unreferenced object 0xffff88800bc06800 (size 512): comm "8", pid 11775, jiffies 4295159829 (age 9.032s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000d66c09ce>] __kmalloc_node_track_caller+0x1ed/0x450 [<00000000c93382b3>] kmalloc_reserve+0x37/0xd0 [<000000005fea522c>] __alloc_skb+0x124/0x380 [<0000000019f29f9a>] st21nfca_hci_i2c_probe+0x170/0x8f2

Fix it by freeing 'pending_skb' in error and remove.

Patch / fix

  • Linux Linux 4.14.261, 4.19.224, 5.4.170, 5.10.90, 5.15.13, 5.16
  • linux Debian 14, Debian 13, Debian 12 5.15.15-1

debian advisories DEBIAN-CVE-2021-46924

  • linux Ubuntu 18.04 LTS 4.15.0-173.182
  • linux Ubuntu 20.04 LTS 5.4.0-105.119
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1124.133
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1069.73
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1068.72
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1018.20
  • linux-kvm Ubuntu 18.04 LTS 4.15.0-1110.113
  • linux-kvm Ubuntu 20.04 LTS 5.4.0-1059.62

ubuntu advisories UBUNTU-CVE-2021-46924

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-rt SLE Micro 5.4, SLE Micro 5.3, openSUSE Leap Micro 5.4 +1 more 5.14.21-150400.15.71.1
  • kernel-source-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.71.1
  • kernel-rt SLE Real Time 12 SP5 4.12.14-10.171.1
  • kernel-syms-rt SLE Real Time 12 SP5 4.12.14-10.171.1
  • kernel-rt_debug SLE Real Time 12 SP5 4.12.14-10.171.1
  • kernel-source-rt SLE Real Time 12 SP5 4.12.14-10.171.1
  • kernel-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.173.1
  • kernel-syms-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.173.1

suse advisories SUSE-SU-2024:0977-1SUSE-SU-2024:0976-1SUSE-SU-2024:0975-1SUSE-SU-2024:0926-1SUSE-SU-2024:0925-1SUSE-SU-2024:0910-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-46924 updated cvss 4.4

kernel: NFC: st21nfca: Fix memory leak in device probe and remove

  • 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
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 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.23% chance of exploitation in the next 30 days, higher than 13% 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.