{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-63915",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-63915"
  ],
  "published": "2026-07-19T14:56:29Z",
  "summary": "nfc: hci: fix out-of-bounds read in HCP header parsing",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: hci: fix out-of-bounds read in HCP header parsing\n\nBoth nfc_hci_recv_from_llc() and nci_hci_data_received_cb() read\npacket->header from skb->data at function entry without first checking\nthat the buffer holds at least one byte. A malicious NFC peer can send\na 0-byte HCP frame that passes through the SHDLC layer and reaches\nthese functions, causing an out-of-bounds heap read of packet->header.\nThe same 0-byte frame, if queued as a non-final fragment, also causes\nthe reassembly loop to underflow msg_len to UINT_MAX, triggering\nskb_over_panic() when the reassembled skb is written.\n\nFix this by adding a pskb_may_pull() check at the entry of each\nfunction before packet->header is first accessed. The existing\npskb_may_pull() checks before the reassembled hcp_skb is cast to\nstruct hcp_packet remain in place to guard the 2-byte HCP message\nheader.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.176",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-63915"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ed6d5d97dad0334a7f43d218753429cbe2f70a4f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b99366d74b535d0cadb1ef73e04639415d9ff3b7"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/37382293f174b82a0616c8295e32b1fc8e13d1ed"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c4cc6b3b0013acb3ed0b2b60e57dfae98647fe98"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1905f5ec3641b2b234bb63549c8ca11ab85466eb"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/22d41b176b9989efd21c3b2d3abf6728f05b9d9a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/83b1362edc9d6ae376c6f36da116e2c70f2e70a6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f040e590c035bfd9553fe79ee9585caf1b14d67b"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T13:16:28Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:A - The bug is triggered by malformed HCP frames from a malicious NFC peer over the RF link; NFC is a proximity wireless medium analogous to Bluetooth, requiring the attacker to be within NFC range (~4 cm) of the victim device.\nAC:L - An attacker with commodity NFC hardware can reliably send a 0-byte HCP frame (or fragment sequence) to trigger the out-of-bounds read and the msg_len integer underflow that leads to skb_over_panic(), with no race or special memory layout required.\nPR:N - Exploitation requires no privileges on the victim system; inbound frames are processed in kernel driver/workqueue context with no authentication, and the attacker only needs an active NFC RF session with the victim's controller.\nUI:N - On typical NFC-enabled deployments (Android phones, payment terminals, transit readers), the victim does not need to perform a deliberate administrative action beyond having NFC radio active while an attacker initiates proximity communication.\nS:U - Impact is confined to kernel memory and availability on the victim host; it does not cross a VM, container, or IOMMU security boundary.\nC:H - The vulnerable code dereferences packet->header from skb->data on a zero-length skb, causing an out-of-bounds heap read of at least one byte of adjacent kernel memory.\nI:H - The fragment-reassembly path underflows msg_len when processing zero-length fragments, passing a wrapped length to skb_put_data() and attempting a massive kernel buffer write before panic; combined with the heap out-of-bounds read, this is kernel memory corruption with potential for further exploitation.\nA:H - The integer underflow in HCP fragment reassembly reliably triggers skb_over_panic() (kernel BUG/panic), causing complete loss of kernel availability on affected systems."
    }
  }
}