Security readout for executives and security teams
Plain-English summary
A local, low-privileged user can trigger an out-of-bounds kernel memory read through Linux NFC socket handling. This may expose sensitive kernel data or crash the system. The supplied CVSS score is 7.1 (high); integrity impact is not identified.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially for shared Linux systems, developer platforms, and hosts running untrusted workloads. It is less urgent where vulnerable kernels are absent or NFC LLCP is unavailable, but those conditions should be verified rather than assumed. No active exploitation is evidenced in the supplied sources.
Technical view
Linux NFC LLCP setsockopt handling used an unsafe copy_from_sockptr() operation, allowing a four-byte slab out-of-bounds read. KASAN and syzbot reproduced the flaw in nfc_llcp_setsockopt(). The kernel fix replaces the operation with copy_safe_from_sockptr().
Likely exposure
Exposure is most likely on affected Linux kernels where NFC LLCP functionality is available and untrusted users or workloads can make local socket calls. The supplied version data identifies affected releases but is insufficiently normalized for reliable range matching; confirm distribution backports and kernel builds individually.
Exploitation context
The supplied evidence shows automated syzbot reproduction and a kernel memory-safety failure. It does not establish public weaponization or active exploitation, and the CVE is not listed as KEV in the bundle. Network-only attackers are not indicated because the CVSS vector requires local access and low privileges.
Researcher notes
The reported KASAN trace identifies a four-byte slab out-of-bounds read at net/nfc/llcp_sock.c:255 during setsockopt. CVSS 3.1 is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. The bundle supplies four stable-kernel fix commits, but does not map each commit clearly to every affected release.
Mitigation direction
Install the vendor-supported kernel update containing the listed fix or an equivalent backport.
Check distribution advisories because package versions may contain fixes without matching upstream version numbers.
Prioritize multi-user systems and hosts running untrusted local workloads.
Follow vendor guidance for any temporary mitigation when immediate kernel replacement is unavailable.
Validation and detection
Record each host's running kernel release, build, architecture, and distribution package version.
Compare installed packages against the relevant distribution security advisory and backport status.
Verify source-based kernels contain one of the listed fixes or an equivalent safe-copy change.
Confirm whether NFC LLCP functionality is present and available to untrusted local users.
Review kernel logs for NFC LLCP-related out-of-bounds reports or unexplained crashes.
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-36915 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.
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.