usb: typec: ucsi: ccg: reject firmware images without a ':' record header
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.2
References 8
git.kernel.org
- stable/c/b41dfc033fe594e152648050e95b9489cd53e9e3
- stable/c/2f395ca1263bd181995eb829f5943a83a20db213
- stable/c/6526f8684f72391138353642af908803ba70795e
- stable/c/3f432b8203066c26770fe6ea591361f10021dd6b
- stable/c/c4ee519b06389e59ba2d6aa722fcc4a02a8bbcbb
- stable/c/a38ed87818b2419090fb1a6338ddce6842b65dfa
- stable/c/c8460de584fe5415d212cfdd127d4db90835a450
- stable/c/d7486952bf74e546ee3748fb14b2d07881fa6273