CVE-2026-63964
CVE CVE-2026-63964EUVD EUVD-2026-45737Published 2026-07-19T14:55:53.000ZLast changed 2026-07-20T06:41:45.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <b41dfc033fe594e152648050e95b9489cd53e9e3; patch: 7.0.12; patch: 5.10.259; patch: 6.12.93; 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <6526f8684f72391138353642af908803ba70795e; patch: 5.15.210; 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <c8460de584fe5415d212cfdd127d4db90835a450; patch: 7.1; patch: 0; 5.2; 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <d7486952bf74e546ee3748fb14b2d07881fa6273; 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <2f395ca1263bd181995eb829f5943a83a20db213; patch: 6.6.143; patch: 6.1.176; 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <a38ed87818b2419090fb1a6338ddce6842b65dfa; patch: 6.18.35; 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <c4ee519b06389e59ba2d6aa722fcc4a02a8bbcbb; 5c9ae5a87573d38cfc4c740aafda2fa6ce06e401 <3f432b8203066c26770fe6ea591361f10021dd6b
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.