From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-89619][MODERATE 7.0] HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer Date: Sat, 12 Sep 2026 02:28:10 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-89619 X-AL-KERNEL-Priority: MODERATE 7.0 X-AL-KERNEL-Severity: MODERATE 7.0 X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: YES X-AL-KERNEL-ActionableScore: 5 X-AL-KERNEL-ActionableScore-Lower: 4 X-AL-KERNEL-Commit: 72706b44b665679d7d60a488d8776a911f1a93f3 List-Id: CVE: CVE-2026-89619 Priority: MODERATE 7.0 AL-KERNEL base severity: MODERATE KPANIC flag: YES Patch: HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer Commit: 72706b44b665679d7d60a488d8776a911f1a93f3 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=72706b44b665679d7d60a488d8776a911f1a93f3 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89619 Analysis date: Sat, 12 Sep 2026 02:28:10 -0400 ActionableScore: 5 ActionableScore lower bound: 4 Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review Manual review required: YES Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-89619 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89619 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: MODERATE 7.0 Manual review required: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-89619 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-89619 CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-787;CWE-122;*CWE-20;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7.8';DESCR 'A kernel buffer overflow in the Intel QuickSPI HID GET_REPORT path occurs because quickspi_get_report copied the full device supplied report length into the callers hidraw buffer without checking the callers requested length. A local user can potentially trigger this through HIDIOCGFEATURE or HIDIOCGINPUT by requesting a smaller buffer than the report returned by the touch controller, causing an out of bounds write in kernel memory. For the CVSS the PR:L reflects that a local user or process must be able to access the affected hidraw interface, while full administrative privileges are not inherently required in permissive device permission setups. The issue is not network reachable. Impact is at least local denial of service via kernel memory corruption and in the paranoid case may allow confidentiality or integrity impact including privilege escalation if the overflow content and heap layout are controllable enough.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5) YES USB SIMPLEFIX ERRORPATH HARDWARE KPANIC INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=5 ActionableScoreLower=4 PrimitiveClass=CLASS_B RealUAF=NO HostAdminRequired=NO NamespaceScopedPrivilege=NO ImportantCandidate=YES ManualReview=REQUIRED AutoDowngradeAllowed=NO 1. ActionableScore * Raw conservative score: 4 * Conservative score: 4 * Raw paranoid score: 5 * Paranoid score: 5 * Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**:: No floor or cap was applied. 2. Signal breakdown Conservative signals: * +1 Constrained kernel buffer overwrite. The patch establishes a real out of bounds write because quickspi_get_report copied qsdev->report_len bytes into a caller buffer sized by hidraw len. * +1 Local below host admin trigger. The vulnerable path is reachable through HIDIOCGFEATURE or HIDIOCGINPUT by a local process with access to the affected hidraw device. Full host administrator privilege is not inherently required. * +1 Weak exploitation concern. The caller can influence the requested buffer size and report request, and the bug writes beyond a kernel buffer. Payload and target selection are still constrained. * +1 Reliable kernel crash or strong DoS. A kernel heap overwrite is a realistic crash and DoS condition. Paranoid adjustment: * +1 Higher interpretation of corruption leverage. The overflow writes device supplied content into kernel memory, and if report contents or heap layout are sufficiently attacker influenced, exploitation may extend beyond crash. This is still not enough to classify as CLASS_A because controlled target selection, arbitrary write, controlled reclaim, or demonstrated LPE is not established. Non-awarded signals: * Controlled reclaim not demonstrated. * Arbitrary or directed kernel write not demonstrated. * RealUAF not present. * Concrete repeated release or refcount mutation not present. * Remote reachability not established. * Namespace scoped privilege not relevant. * Extra Availability not awarded because the crash risk is already counted. * Confidentiality and Integrity are not awarded as separate established signals because no concrete disclosure path, protected object overwrite, credential modification, or LPE chain is demonstrated. 3. Reachability analysis The likely attacker is a local user or local process that can open the affected hidraw interface and issue HIDIOCGFEATURE or HIDIOCGINPUT. The complete trigger does not require host root by design, but it does require access to the relevant Intel QuickSPI HID device node, which may depend on udev permissions, seat policy, input group membership, or a device broker. This is not network reachable. No namespace scoped capability is involved. No prior privileged kernel configuration is required beyond the affected driver and hardware being present. The hardware is specific to Intel THC QuickSPI HID touch controller systems, but the patch does not establish a rare physical-only attack model. No race or hard timing condition is required. 4. Primitive and severity interpretation The exact primitive is a kernel buffer overflow in the GET_REPORT path. The vulnerable copy uses a device supplied report length instead of the caller supplied buffer length. This is an out of bounds write into kernel memory, not a UAF and not a mere NULL dereference. The primitive is classified as CLASS_B because it is a real kernel memory corruption primitive with unresolved exploitation leverage, but the evidence does not establish full attacker control over payload, destination, reclaimed object contents, callback control, or arbitrary kernel read or write. The demonstrated consequence is local kernel memory corruption and likely DoS. The speculative consequence is privilege escalation if report contents and heap placement are sufficiently controllable. ImportantCandidate=YES because local kernel OOB write bugs should not be automatically downgraded when exploitation leverage is unresolved. AutoDowngradeAllowed=NO because automatic closure would discard a concrete kernel memory corruption primitive. 5. One-sentence report phrase A local kernel buffer overflow in the Intel QuickSPI HID GET_REPORT path allows a process with access to the affected hidraw device to request a smaller buffer than the device supplied report length, causing an out of bounds kernel write and requiring manual review for possible impact beyond DoS. 6. Manual review recommendation MANUAL CHECK REQUIRED Reason: this is a concrete kernel out of bounds write reachable from a local device interface, with unresolved exploitability beyond crash depending on hidraw permissions, device response control, and heap layout. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer Commit: 72706b44b665679d7d60a488d8776a911f1a93f3 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=72706b44b665679d7d60a488d8776a911f1a93f3 Commit description: quickspi_hid_raw_request() receives the caller's buffer length in len, but quickspi_get_report() never sees it and copies the whole device-supplied response into buf regardless: memcpy(buf, qsdev->report_buf, qsdev->report_len); qsdev->report_len comes from the input report the touch controller returns, while buf is sized to whatever the caller asked hidraw for through HIDIOCGFEATURE or HIDIOCGINPUT. A response larger than that overflows buf with device-controlled content. The intel-quicki2c sibling already passes the caller length down to quicki2c_get_report() and validates the response against it before the copy. Do the same here. Fixes: 4138f21 ("HID: intel-thc-hid: intel-quickspi: Complete THC QuickSPI driver") Suggested-by: Sashiko AI Cc: stable@vger.kernel.org Assisted-by: Claude:claude-opus-5 Signed-off-by: HyeongJun An Reviewed-by: Even Xu Signed-off-by: Jiri Kosina Signed-off-by: Greg Kroah-Hartman Changed files: drivers/hid/intel-thc-hid/intel-quickspi/quickspi-hid.c drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.h Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=72706b44b665679d7d60a488d8776a911f1a93f3 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-89619 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89619 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H The Best / paranoid CVSS score: 7.8 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: 4 Paranoid ActionableScore: 5 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: MODERATE KPANIC detected for this report: YES Published priority for this report (same as in Subject): MODERATE 7.0 These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).