CVE-2023-53298: nfc: fix memory leak of se_io context in nfc_genl_se_io
In the Linux kernel, the following vulnerability has been resolved:
nfc: fix memory leak of se_io context in nfc_genl_se_io
The callback context for sending/receiving APDUs to/from the selected
secure element is allocated inside nfc_genl_se_io and supposed to be
eventually freed in se_io_cb callback function. However, there are several
error paths where the bwi_timer is not charged to call se_io_cb later, and
the cb_context is leaked.
The patch proposes to free the cb_context explicitly on those error paths.
At the moment we can't simply check 'dev->ops->se_io()' return value as it
may be negative in both cases: when the timer was charged and was not.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53298 is a Linux kernel memory leak in NFC secure element I/O handling. A local low-privileged user could trigger failed paths that leak callback context memory, potentially reducing availability. The source bundle rates it medium with CVSS 5.5 and does not show active exploitation.
Executive priority
Treat as a normal-priority kernel availability issue unless NFC-enabled multi-user or kiosk-like systems are in scope. Patch through standard kernel maintenance, but do not defer indefinitely on systems where untrusted local users exist.
Technical view
In nfc_genl_se_io, cb_context for APDU exchange should be freed by se_io_cb, but some error paths do not arm bwi_timer, so the callback never frees it. Stable fixes explicitly free cb_context on those paths. Impact is availability only under the provided CVSS vector.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions with NFC support and secure element I/O functionality enabled or reachable by local users. Distro backports may change version conclusions, so validate using vendor kernel advisories and applied patch status.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of exploitation in the wild. The CVSS vector requires local access, low privileges, and no user interaction; it indicates no confidentiality or integrity impact, but high availability impact.
Researcher notes
Evidence supports a CWE-401 memory leak in the NFC generic netlink secure element I/O path. The key uncertainty is practical reachability across distributions and device configurations. Avoid assuming broad internet exposure; the provided vector is local only.
Mitigation direction
Update to a kernel build containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes matching your kernel package.
Prioritize systems where local users can access NFC functionality.
Disable or restrict unnecessary NFC functionality where vendor guidance supports it.
Monitor vendor security notices for any changed exploitation or patch guidance.
Validation and detection
Inventory Linux kernel versions across endpoints, servers, and embedded systems.
Confirm whether NFC and secure element functionality is enabled or exposed locally.
Map installed kernel packages to vendor advisories and stable fix commits.
Review vulnerability scanner findings for CVE-2023-53298 against actual kernel patch level.
Verify patched systems after reboot are running the fixed kernel.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.