CVE-2026-63915
nfc: hci: fix out-of-bounds read in HCP header parsing
Description
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, triggering skb_over_panic() when the reassembled skb is written. Fix this by adding a pskb_may_pull() check at the entry of each function before packet->header is first accessed. The existing pskb_may_pull() checks before the reassembled hcp_skb is cast to struct hcp_packet remain in place to guard the 2-byte HCP message header.
INFO
Published Date :
July 19, 2026, 4:17 p.m.
Last Modified :
July 27, 2026, 5:44 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Update the Linux kernel to the patched version.
- Ensure skb buffers are properly checked before access.
- Verify the SHDLC layer handles zero-byte frames correctly.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-63915.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-63915 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-63915
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-63915 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-63915 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 20, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 19, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': 'ed6d5d97dad0334a7f43d218753429cbe2f70a4f', 'versionType': 'git'}, {'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': 'b99366d74b535d0cadb1ef73e04639415d9ff3b7', 'versionType': 'git'}, {'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': '37382293f174b82a0616c8295e32b1fc8e13d1ed', 'versionType': 'git'}, {'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': 'c4cc6b3b0013acb3ed0b2b60e57dfae98647fe98', 'versionType': 'git'}, {'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': '1905f5ec3641b2b234bb63549c8ca11ab85466eb', 'versionType': 'git'}, {'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': '22d41b176b9989efd21c3b2d3abf6728f05b9d9a', 'versionType': 'git'}, {'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': '83b1362edc9d6ae376c6f36da116e2c70f2e70a6', 'versionType': 'git'}, {'status': 'affected', 'version': '8b8d2e08bf0d50193931afd27482a59376b66b2b', 'lessThan': 'f040e590c035bfd9553fe79ee9585caf1b14d67b', 'versionType': 'git'}], 'programFiles': ['net/nfc/hci/core.c', 'net/nfc/nci/hci.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3.5'}, {'status': 'unaffected', 'version': '0', 'lessThan': '3.5', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/nfc/hci/core.c', 'net/nfc/nci/hci.c'], 'defaultStatus': 'affected'}] Added Description 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, triggering skb_over_panic() when the reassembled skb is written. Fix this by adding a pskb_may_pull() check at the entry of each function before packet->header is first accessed. The existing pskb_may_pull() checks before the reassembled hcp_skb is cast to struct hcp_packet remain in place to guard the 2-byte HCP message header. Added Reference https://git.kernel.org/stable/c/1905f5ec3641b2b234bb63549c8ca11ab85466eb Added Reference https://git.kernel.org/stable/c/22d41b176b9989efd21c3b2d3abf6728f05b9d9a Added Reference https://git.kernel.org/stable/c/37382293f174b82a0616c8295e32b1fc8e13d1ed Added Reference https://git.kernel.org/stable/c/83b1362edc9d6ae376c6f36da116e2c70f2e70a6 Added Reference https://git.kernel.org/stable/c/b99366d74b535d0cadb1ef73e04639415d9ff3b7 Added Reference https://git.kernel.org/stable/c/c4cc6b3b0013acb3ed0b2b60e57dfae98647fe98 Added Reference https://git.kernel.org/stable/c/ed6d5d97dad0334a7f43d218753429cbe2f70a4f Added Reference https://git.kernel.org/stable/c/f040e590c035bfd9553fe79ee9585caf1b14d67b