CVE-2026-63915

HIGHCVSS 8.8/10EPSS 0.34%

Last modified

CVE-2026-63915 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 0.34% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
8.8/10

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

EPSS Probability
0.34%

27.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < ed6d5d97dad0334a7f43d218753429cbe2f70a4f; >= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < b99366d74b535d0cadb1ef73e04639415d9ff3b7; >= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < 37382293f174b82a0616c8295e32b1fc8e13d1ed; >= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < c4cc6b3b0013acb3ed0b2b60e57dfae98647fe98; >= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < 1905f5ec3641b2b234bb63549c8ca11ab85466eb; >= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < 22d41b176b9989efd21c3b2d3abf6728f05b9d9a; >= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < 83b1362edc9d6ae376c6f36da116e2c70f2e70a6; >= 8b8d2e08bf0d50193931afd27482a59376b66b2b, < f040e590c035bfd9553fe79ee9585caf1b14d67b
LinuxLinux3.5

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-63915?
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.
How severe is CVE-2026-63915?
CVE-2026-63915 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.34% probability of exploitation in the next 30 days.
How do I fix CVE-2026-63915?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-63915?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST