CVE-2024-35915: nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet
In the Linux kernel, the following vulnerability has been resolved:
nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet
syzbot reported the following uninit-value access issue [1][2]:
nci_rx_work() parses and processes received packet. When the payload
length is zero, each message type handler reads uninitialized payload
and KMSAN detects this issue. The receipt of a packet with a zero-size
payload is considered unexpected, and therefore, such packets should be
silently discarded.
This patch resolved this issue by checking payload size before calling
each message type handler codes.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35915 is a Linux kernel NFC/NCI bug where malformed zero-length NFC controller packets could make the kernel read uninitialized memory. Public sources describe a kernel fix, but do not provide a CVSS score, confirmed exploitation, or detailed business impact.
Executive priority
Handle through normal kernel patch governance, with higher priority for NFC-enabled endpoints and embedded devices. No source confirms active exploitation or critical severity, so this is not supported as an emergency based on the supplied evidence.
Technical view
In nci_rx_work(), zero-size payloads reached NCI message handlers that expected payload data, causing uninitialized-value reads detected by KMSAN. The upstream fix checks payload size before dispatching handlers and silently discards unexpected zero-payload packets.
Likely exposure
Exposure is most relevant to Linux systems with the NFC/NCI subsystem present and reachable through NFC controller traffic. The CVE record lists multiple Linux kernel versions and stable commits, but the supplied data does not map every distribution package or configuration state.
Exploitation context
The source bundle reports syzbot discovery and KMSAN detection. It does not cite active exploitation, public weaponization, KEV listing, or a practical attack chain. Treat exploitation status as unconfirmed.
Researcher notes
The relevant condition is receipt of an unexpected zero-size NCI payload before handler dispatch. The fix is defensive validation, not a broad NFC redesign. Public evidence is limited to kernel commits, CVE metadata, syzbot/KMSAN context, and Debian advisories.
Mitigation direction
Apply kernel or distribution updates containing the referenced stable fixes.
Review Debian LTS and vendor advisories for package-specific remediation.
Prioritize systems where NFC/NCI support is enabled or required.
Check embedded and appliance vendors for their fixed firmware guidance.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and appliances.
Confirm whether NFC/NCI support is built, loaded, or exposed.
Verify installed kernels include the applicable stable fix commit or vendor backport.
Track Debian or vendor advisory status for each affected platform.
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-2024-35915 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.