CVE detail
CVE-2026-63964
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: ccg: reject firmware images without a ':' record header do_flash() locates the first .cyacd record with p = strnchr(fw->data, fw->size, ':'); while (p < eof) { s = strnchr(p + 1, eof - p - 1, ':'); ... } If the firmware image contains no ':' byte, strnchr() returns NULL. NULL compares less than the valid kernel pointer eof, so the loop body runs and strnchr() is called with p + 1 == (void *)1 and a length of roughly (unsigned long)eof, causing a wonderful crash. The not_signed_fw fallthrough earlier in do_flash() and the chip-state branches in ccg_fw_update_needed() allow an unsigned blob to reach this loop, so a root user who can place a crafted file under /lib/firmware and write the do_flash sysfs attribute can trigger the oops. Bail out with -EINVAL when the initial strnchr() returns NULL.
Buzz score
Why this CVE is surfacing
This all-time snapshot uses the same composite formula as Trending across a 30-year evidence window, rather than a current rolling window.
Buzz score components · mention 23.0 · diversity 10.0 · KEV 0.0 · OTX 0.0 · PoC 0.0
Why it matters now
Mention timeline
- Total mentions
- 9
- within the 30d window
- Peak daily
- 8
- highest bucket
Evidence
Source links by recency
9 source links · newest first
- CVE-2026-63964 usb: typec: ucsi: ccg: reject firmware images without a ':' record headerMicrosoft MSRC
Information published.
vendormsrc.microsoft.comJul 21, 2026, 8:03 AM No excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PMNo excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PMNo excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PMNo excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PMNo excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PMNo excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PMNo excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PMNo excerpt available.
Patchgit.kernel.orgJul 19, 2026, 4:17 PM
Exploit code
Public exploit repository references
Public PoC repositories are third-party, potentially unsafe artifacts. Treat their code as untrusted and use it only on authorized systems in an isolated, least-privilege environment. cvebuzz does not execute the code or verify that an exploit works.