{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89619 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89619 is a high-severity memory corruption vulnerability in Linux, published on 11 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-89619 and fix it if it is affected.\n\nWhat it is: CVE-2026-89619 is a high-severity memory corruption vulnerability in Linux, published on 11 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-89619 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-89619/ (Markdown: https://insights.sbomify.com/CVE-2026-89619/index.md)","id":"CVE-2026-89619","markdown":"https://insights.sbomify.com/CVE-2026-89619/index.md","name":"CVE-2026-89619","record":{"aliases":["BELL-CVE-2026-89619","DEBIAN-CVE-2026-89619","GHSA-mjmr-px5q-jfhp","UBUNTU-CVE-2026-89619"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A buffer overflow in the Intel THC HID QuickSPI driver allows a malicious device to corrupt kernel memory, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\nHID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer\n\nquickspi_hid_raw_request() receives the caller's buffer length in len, but\nquickspi_get_report() never sees it and copies the whole device-supplied\nresponse into buf regardless:\n\n    memcpy(buf, qsdev-\u003ereport_buf, qsdev-\u003ereport_len);\n\nqsdev-\u003ereport_len comes from the input report the touch controller returns,\nwhile buf is sized to whatever the caller asked hidraw for through\nHIDIOCGFEATURE or HIDIOCGINPUT.  A response larger than that overflows buf\nwith device-controlled content.\n\nThe intel-quicki2c sibling already passes the caller length down to\nquicki2c_get_report() and validates the response against it before the\ncopy.  Do the same here.","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":"HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer","id":"CVE-2026-89619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"HID: intel-thc-hid: intel-quickspi: validate report size before copy","id":"CVE-2026-89620"},"packages":[],"prev":{"headline":"eventfs: Initialize ei-\u003echildren and ei-\u003elist in init_ei()","id":"CVE-2026-89618"},"products":["Linux"],"published":"2026-09-11","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 buffer overflow in the Intel THC HID QuickSPI driver allows a malicious device to corrupt kernel memory, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-89619/"}