{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63902 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-63902 is a memory corruption vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-63902 and fix it if it is affected.\n\nWhat it is: CVE-2026-63902 is a memory corruption vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-63902 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-63902/ (Markdown: https://insights.sbomify.com/CVE-2026-63902/index.md)","id":"CVE-2026-63902","markdown":"https://insights.sbomify.com/CVE-2026-63902/index.md","name":"CVE-2026-63902","record":{"aliases":["BELL-CVE-2026-63902","DEBIAN-CVE-2026-63902","GHSA-28gg-7x4r-8gcw","ROOT-OS-UBUNTU-2204-CVE-2026-63902","UBUNTU-CVE-2026-63902"],"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 USB driver","requires_auth":"none","summary":"A local attacker with physical access can trigger an out-of-bounds read in the Cypress M8 USB serial driver, potentially causing a system crash or code execution.","user_interaction":"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\nUSB: serial: cypress_m8: validate interrupt packet headers\n\ncypress_read_int_callback() parses the interrupt-in buffer according to\nthe selected Cypress packet format. Format 1 has a two-byte status/count\nheader and format 2 has a one-byte combined status/count header. The\nusb-serial core sizes the interrupt-in buffer from the endpoint\ndescriptor's wMaxPacketSize, and successful interrupt transfers can\ncomplete short when URB_SHORT_NOT_OK is not set.\n\nCheck that the completed packet contains the selected header before\nreading it. Malformed short reports are ignored and the interrupt URB is\nresubmitted through the existing retry path, preventing out-of-bounds\nheader-byte reads.\n\nKASAN report as below:\nKASAN slab-out-of-bounds in cypress_read_int_callback+0x240/0x7f0\nRead of size 1\nCall trace:\n  cypress_read_int_callback() (drivers/usb/serial/cypress_m8.c:1009)\n  __usb_hcd_giveback_urb()\n  dummy_timer()\n\n[ johan: use constants in header length sanity checks ]","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: serial: cypress_m8: validate interrupt packet headers","id":"CVE-2026-63902","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":"USB: serial: belkin_sa: validate interrupt status length","id":"CVE-2026-63903"},"packages":[],"prev":{"headline":"USB: serial: digi_acceleport: fix memory corruption with small endpoints","id":"CVE-2026-63901"},"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-19","vendors":["Linux"]},"summary":"A local attacker with physical access can trigger an out-of-bounds read in the Cypress M8 USB serial driver, potentially causing a system crash or code execution.","url":"https://insights.sbomify.com/CVE-2026-63902/"}