CVE-2021-47518: nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
In the Linux kernel, the following vulnerability has been resolved:
nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
The done() netlink callback nfc_genl_dump_ses_done() should check if
received argument is non-NULL, because its allocation could fail earlier
in dumpit() (nfc_genl_dump_ses()).
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a potential crash bug in the NFC subsystem. If an earlier memory allocation fails, a later netlink cleanup callback may dereference a NULL pointer. The source bundle does not provide CVSS, CWE, or confirmed impact details, so business urgency depends on whether affected kernels and NFC functionality are present.
Executive priority
Treat this as routine-to-elevated kernel maintenance, not an emergency, unless affected systems expose NFC functionality or have many untrusted local users. There is no supplied evidence of active exploitation, but kernel crash bugs still matter for availability and operational resilience.
Technical view
CVE-2021-47518 fixes a missing NULL check in nfc_genl_dump_ses_done(). The done() netlink callback could receive a NULL argument because allocation may fail earlier in nfc_genl_dump_ses(). Stable kernel commits add the defensive handling. The record lists affected Linux versions and multiple stable backport commits.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with the NFC kernel subsystem available. The bundle does not identify affected distributions, device classes, required privileges, or whether NFC hardware must be present.
Exploitation context
No active exploitation is supported by the supplied sources. The CVE is not marked KEV, and the bundle provides no public exploit evidence. The described failure mode suggests availability risk from a kernel NULL pointer dereference, but exploitability details are incomplete.
Researcher notes
The key uncertainty is reachability. Sources identify the vulnerable callback and fix rationale, but not prerequisites, privilege level, distribution mappings, or realistic trigger conditions. Validation should focus on kernel lineage, NFC subsystem availability, and whether vendor kernels contain the stable commits.
Mitigation direction
Inventory Linux kernel versions across servers, endpoints, appliances, and embedded devices.
Prioritize systems where NFC support is enabled or locally reachable.
Apply vendor kernel updates containing the referenced stable fixes.
If patching is delayed, review vendor guidance for NFC subsystem hardening or disablement.
Track distribution advisories that map this kernel fix to package versions.
Validation and detection
Confirm running kernel versions against vendor advisories and the CVE record.
Check whether NFC kernel modules or configuration are enabled on relevant systems.
Verify installed kernel packages include the referenced stable backport fix.
Review crash logs for NFC or netlink-related NULL pointer dereference events.
Document any systems requiring vendor-specific exception handling.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47518 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.