{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74455 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74455 is a memory corruption vulnerability in Linux, published on 15 Aug 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-74455 and fix it if it is affected.\n\nWhat it is: CVE-2026-74455 is a memory corruption vulnerability in Linux, published on 15 Aug 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-74455 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-74455/ (Markdown: https://insights.sbomify.com/CVE-2026-74455/index.md)","id":"CVE-2026-74455","markdown":"https://insights.sbomify.com/CVE-2026-74455/index.md","name":"CVE-2026-74455","record":{"aliases":["AZL-96144","BELL-CVE-2026-74455","DEBIAN-CVE-2026-74455","GHSA-fm8j-hx94-qc39","UBUNTU-CVE-2026-74455"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A missing length validation in the Linux kernel peak_usb CAN driver allows attackers with USB access to cause memory corruption, potentially leading to system crashes or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\ncan: peak_usb: validate uCAN receive record lengths\n\npcan_usb_fd_decode_buf() walks uCAN records packed in one USB\nreceive buffer.\n\nRequire each record to contain the fixed header for its type, and verify\nCAN payload bytes before copying them into the skb.","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":"can: peak_usb: validate uCAN receive record lengths","id":"CVE-2026-74455","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"can: peak_usb: peak_usb_start(): fix double free of transfer buffer on URB submit error","id":"CVE-2026-74456"},"packages":[],"prev":{"headline":"drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size","id":"CVE-2026-74454"},"products":["Linux"],"published":"2026-08-15","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-08-19","vendors":["Linux"]},"summary":"A missing length validation in the Linux kernel peak_usb CAN driver allows attackers with USB access to cause memory corruption, potentially leading to system crashes or code execution.","url":"https://insights.sbomify.com/CVE-2026-74455/"}