CVE-2022-49923: nfc: nxp-nci: Fix potential memory leak in nxp_nci_send()
In the Linux kernel, the following vulnerability has been resolved:
nfc: nxp-nci: Fix potential memory leak in nxp_nci_send()
nxp_nci_send() will call nxp_nci_i2c_write(), and only free skb when
nxp_nci_i2c_write() failed. However, even if the nxp_nci_i2c_write()
run succeeds, the skb will not be freed in nxp_nci_i2c_write(). As the
result, the skb will memleak. nxp_nci_send() should also free the skb
when nxp_nci_i2c_write() succeeds.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49923 is a Linux kernel memory leak in the NXP NCI NFC driver path. A local, low-privileged user could potentially trigger memory consumption that affects system availability. It is not described as data theft or privilege escalation.
Executive priority
Treat as a moderate availability risk. Prioritize patching on endpoints, embedded Linux, or devices with NFC capability. It is lower urgency than remotely exploitable kernel flaws, but unresolved memory leaks can still disrupt business operations on exposed systems.
Technical view
In nxp_nci_send(), an skb is freed only when nxp_nci_i2c_write() fails. On successful write, the skb is not freed, causing a CWE-401 memory leak. The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact.
Likely exposure
Exposure is most relevant to Linux systems using affected kernel versions with the NXP NCI NFC driver path present or enabled. General-purpose servers without this NFC hardware or driver are less likely to be affected, but kernel package status should still be verified.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. Exploitation is characterized by CVSS as local and requiring low privileges. The documented impact is availability through memory exhaustion, not confidentiality or integrity compromise.
Researcher notes
Version data in the provided record is not fully self-explanatory, so use upstream stable commits and distro advisories for exact affected/fixed ranges. The fix is a memory-management correction in the NFC nxp-nci send path.
Mitigation direction
Apply a Linux kernel update containing the referenced stable fixes.
Use distribution vendor kernel advisories to identify fixed package versions.
Prioritize systems with NFC hardware or NXP NCI driver support enabled.
If patching is delayed, review vendor guidance for safe driver-level mitigations.
Validation and detection
Inventory running Linux kernel versions across affected assets.
Check whether NXP NCI NFC driver support is present or loaded.
Compare installed kernels against vendor advisories and referenced stable commits.
Confirm updated kernels are booted, not merely installed.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.