{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93190 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93190 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 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-93190 and fix it if it is affected.\n\nWhat it is: CVE-2026-93190 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 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-93190 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-93190/ (Markdown: https://insights.sbomify.com/CVE-2026-93190/index.md)","id":"CVE-2026-93190","markdown":"https://insights.sbomify.com/CVE-2026-93190/index.md","name":"CVE-2026-93190","record":{"aliases":["BELL-CVE-2026-93190","DEBIAN-CVE-2026-93190","GHSA-fw4r-5v3q-p28x","UBUNTU-CVE-2026-93190"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A missing bounds check in the ChromeOS EC Type-C driver allows out-of-bounds writes, potentially leading to memory corruption or system crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count\n\ncros_typec_register_partner_pdos() copies the partner PDOs from the EC\nTYPEC_STATUS response into the fixed caps_desc.pdo[PDO_MAX_OBJECTS] array.\n\n\tmemcpy(caps_desc.pdo, resp-\u003esource_cap_pdos,\n\t       sizeof(u32) * resp-\u003esource_cap_count);\n\t...\n\tmemcpy(caps_desc.pdo, resp-\u003esink_cap_pdos,\n\t       sizeof(u32) * resp-\u003esink_cap_count);\n\nPDO_MAX_OBJECTS is 7. source_cap_count and sink_cap_count are u8 fields\nfrom the EC. The only check is that they are not both zero. If either is\nlarger than 7, the memcpy writes past the end of the array on the stack.\nA count of 255 overflows it by about 1 KB. The EC source arrays are only\nseven entries wide. A larger count reads past them too.\n\nThe ChromeOS EC firmware caps these counts today, so a compliant setup\ndoes not hit this. The kernel should still validate these values rather\nthan trust them.\n\nValidate the counts in cros_typec_register_partner_pdos() next to the\nmemcpy. Skip the PDO registration if either count is above PDO_MAX_OBJECTS.\nThe rest of cros_typec_handle_status() still runs so events are handled\nand cleared.","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":"platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count","id":"CVE-2026-93190","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"smack: fix incorrect task context in smack_msg_queue_msgrcv","id":"CVE-2026-93191"},"packages":[],"prev":{"headline":"HID: core: quiesce input in hid_hw_stop() to prevent use-after-free","id":"CVE-2026-93189"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A missing bounds check in the ChromeOS EC Type-C driver allows out-of-bounds writes, potentially leading to memory corruption or system crashes.","url":"https://insights.sbomify.com/CVE-2026-93190/"}