SECUFOCUSNOW
Home›CVE index›CVE-2026-63915
Review reviewHigh

CVE-2026-63915

Linux

In the Linux kernel, the following vulnerability has been resolved: nfc: hci: fix out-of-bounds read in HCP header parsing Both nfc_hci_recv_from_llc() and nci_hci_data_received_cb() read packet->header from skb->data at function entry without first checking that the buffer holds at least one byte. A malicious NFC peer can send a 0-byte HCP frame that passes through the SHDLC layer and reaches these functions, causing an out-of-bounds heap read of packet->header. The same 0-byte frame, if queued as a non-final fragment, also causes the reassembly loop to underflow msg_len to UINT_MAX, trigg...

CVSS
8.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 8.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: nfc: hci: fix out-of-bounds read in HCP header parsing Both nfc_hci_recv_from_llc() and nci_hci_data_received_cb() read packet->header from skb->data at function entry without first checking that the buffer holds at least one byte. A malicious NFC peer can send a 0-byte HCP frame that passes through the SHDLC layer and reaches these functions, causing an out-of-bounds heap read of packet->header. The same 0-byte frame, if queued as a non-final fragment, also causes the reassembly loop to underflow msg_len to UINT_MAX, trigg...

Affected product and versions

Product
Linux
Affected versions
>= 8b8d2e08bf0d50193931afd27482a59376b66b2b < ed6d5d97dad0334a7f43d218753429cbe2f70a4f, >= 8b8d2e08bf0d50193931afd27482a59376b66b2b < b99366d74b535d0cadb1ef73e04639415d9ff3b7, >= 8b8d2e08bf0d50193931afd27482a59376b66b2b < 37382293f174b82a0616c8295e32b1fc8e13d1ed, >= 8b8d2e08bf0d50193931afd27482a59376b66b2b < c4cc6b3b0013acb3ed0b2b60e57dfae98647fe98, >= 8b8d2e08bf0d50193931afd27482a59376b66b2b < 1905f5ec3641b2b234bb63549c8ca11ab85466eb, >= 8b8d2e08bf0d50193931afd27482a59376b66b2b < 22d41b176b9989efd21c3b2d3abf6728f05b9d9a, >= 8b8d2e08bf0d50193931afd27482a59376b66b2b < 83b1362edc9d6ae376c6f36da116e2c70f2e70a6, >= 8b8d2e08bf0d50193931afd27482a59376b66b2b < f040e590c035bfd9553fe79ee9585caf1b14d67b, >= 3.5
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available