System crash via zero-byte NFC HCP frame
Published Jul 19, 2026 · Updated Jul 19, 2026
Out-of-bounds read in affected Linux Kernel releases allows physically proximate attackers to crash a system via a zero-byte HCP frame. The two receive callbacks dereference packet->header before confirming that skb->data contains one byte, while non-final fragments can underflow msg_len before reassembly writes. Exploitation requires NFC hardware and proximity to send the crafted peer frame; the bounded operational result is an skb_over_panic kernel crash.
Summary
What happened
Out-of-bounds read in affected Linux Kernel releases allows physically proximate attackers to crash a system via a zero-byte HCP frame. The two receive callbacks dereference packet->header before confirming that skb->data contains one byte, while non-final fragments can underflow msg_len before reassembly writes. Exploitation requires NFC hardware and proximity to send the crafted peer frame; the bounded operational result is an skb_over_panic kernel crash.
The record
- CVE
- CVE-2026-63915
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.5
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <1905f5ec3641b2b234bb63549c8ca11ab85466eb
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <22d41b176b9989efd21c3b2d3abf6728f05b9d9a
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <37382293f174b82a0616c8295e32b1fc8e13d1ed
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <83b1362edc9d6ae376c6f36da116e2c70f2e70a6
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <b99366d74b535d0cadb1ef73e04639415d9ff3b7
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <c4cc6b3b0013acb3ed0b2b60e57dfae98647fe98
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <ed6d5d97dad0334a7f43d218753429cbe2f70a4f
- Affected versionversion=8b8d2e08bf0d50193931afd27482a59376b66b2b <f040e590c035bfd9553fe79ee9585caf1b14d67b
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo