{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63964 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-63964 is a 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."},"fix_prompt":"Check this codebase for CVE-2026-63964 and fix it if it is affected.\n\nWhat it is: CVE-2026-63964 is a 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.\nExploitation: There is no known exploitation of CVE-2026-63964 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63964/ (Markdown: https://insights.sbomify.com/CVE-2026-63964/index.md)","id":"CVE-2026-63964","markdown":"https://insights.sbomify.com/CVE-2026-63964/index.md","name":"CVE-2026-63964","record":{"aliases":["AZL-92775","BELL-CVE-2026-63964","DEBIAN-CVE-2026-63964","GHSA-7w55-p3p4-26mv","ROOT-OS-UBUNTU-2204-CVE-2026-63964","UBUNTU-CVE-2026-63964"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB driver","requires_auth":"high_privilege","summary":"A local root user can crash the Linux kernel by providing a malformed firmware image to the UCSI CCG driver due to a null pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: ccg: reject firmware images without a ':' record header\n\ndo_flash() locates the first .cyacd record with\n\n\tp = strnchr(fw-\u003edata, fw-\u003esize, ':');\n\twhile (p \u003c eof) {\n\t\ts = strnchr(p + 1, eof - p - 1, ':');\n\t\t...\n\t}\n\nIf the firmware image contains no ':' byte,  strnchr() returns NULL.\nNULL compares less than the valid kernel pointer eof, so the loop body\nruns and strnchr() is called with p + 1 == (void *)1 and a length of\nroughly (unsigned long)eof, causing a wonderful crash.\n\nThe not_signed_fw fallthrough earlier in do_flash() and the chip-state\nbranches in ccg_fw_update_needed() allow an unsigned blob to reach this\nloop, so a root user who can place a crafted file under /lib/firmware\nand write the do_flash sysfs attribute can trigger the oops.\n\nBail out with -EINVAL when the initial strnchr() returns NULL.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"usb: typec: ucsi: ccg: reject firmware images without a ':' record header","id":"CVE-2026-63964","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"iio: pressure: bmp280: fix stack leak in bmp580 trigger handler","id":"CVE-2026-63965"},"packages":[],"prev":{"headline":"usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers","id":"CVE-2026-63963"},"products":["Linux"],"published":"2026-07-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-07-20","vendors":["Linux"]},"summary":"A local root user can crash the Linux kernel by providing a malformed firmware image to the UCSI CCG driver due to a null pointer dereference.","url":"https://insights.sbomify.com/CVE-2026-63964/"}