# CVE-2026-63915: nfc: hci: fix out-of-bounds read in HCP header parsing

> A malicious NFC peer can trigger an out-of-bounds read and kernel panic via a zero-byte HCP frame, causing denial of service and potential information disclosure.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-63915, DEBIAN-CVE-2026-63915, GHSA-jmh7-f679-ghx4, ROOT-OS-UBUNTU-2204-CVE-2026-63915, UBUNTU-CVE-2026-63915

## What is CVE-2026-63915?

CVE-2026-63915 is a high-severity memory corruption vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-63915?


## How do I fix CVE-2026-63915?

Apply the vendor's patch.

## Is CVE-2026-63915 being exploited?

There is no known exploitation of CVE-2026-63915 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63915 and fix it if it is affected.

What it is: CVE-2026-63915 is a high-severity memory corruption vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63915 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63915/ (Markdown: https://insights.sbomify.com/CVE-2026-63915/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63915
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63915
- OSV: https://osv.dev/vulnerability/CVE-2026-63915

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63915/
Summaries are generated and may contain mistakes; the official description above is the record.