From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-80604][MODERATE REGULAR] HID: core: Fix OOB read in hid_get_report for numbered reports [ Upstream Date: Fri, 28 Aug 2026 06:03:06 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-80604 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 4 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: f8896b684e246f3f00f45ba2b6803ae59b9cc768 List-Id: CVE: CVE-2026-80604 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: HID: core: Fix OOB read in hid_get_report for numbered reports [ Upstream Commit: f8896b684e246f3f00f45ba2b6803ae59b9cc768 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f8896b684e246f3f00f45ba2b6803ae59b9cc768 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80604 Analysis date: Fri, 28 Aug 2026 06:03:06 -0400 ActionableScore: 4 ActionableScore lower bound: 1 Actionable bucket: Borderline manual review recommended, not Strong Important by default Manual review required: YES Summary: A zero length numbered HID report can reach hid_get_report before length validation, causing an OOB read of data(0) and potentially a kernel panic when a malicious or faulty HID device or adjacent HID transport supplies malformed input. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80604 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80604 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 REGULAR 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-80604 MODERATE CHECK WITH IMPACT FROM ORIG NN IMPORTANT Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H';CWE-125;*CWE-20;CWE-754;Other CVSS 'AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H';BEST CVSS score: '7.1';DESCR 'A numbered HID report can reach hid_get_report with size 0 before input length validation, causing an out of bounds read of data(0) while extracting the report ID. A malicious or faulty HID device can trigger this through the HID input path and may cause a kernel crash or warning depending on memory layout and transport behavior. For the CVSS the PR:N because the attacker does not need privileges on the target once the malicious HID input can be delivered. The base vector treats this mainly as a physical device attack with user involvement for device connection or pairing. The paranoid vector treats wireless or already connected HID transports as adjacent and uses C:L because this is an OOB read, while integrity remains N because no write primitive is shown. Impact is mainly denial of service via kernel crash. YES REQUIRES MANUAL CHECK';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended, not Strong Important by default (with actual score 3) SKIP CVE-2026-80604 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE OOB DANGER USB SIMPLEFIX IMPROVEONLY LINUS DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN6 DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 - - guess ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=4 ActionableScoreLower=1 ## 1. ActionableScore * Conservative score: 1 * Paranoid score: 4 * Final recommended bucket: **Borderline manual review recommended, not Strong Important by default**:: ## 2. Signal breakdown Conservative signals: * Device mediated external influence: +1. A malicious or malformed HID device can supply the malformed numbered report. * Reliable kernel crash / strong DoS: +1. The commit explicitly says size 0 can cause an OOB read or kernel panic. * Broad/default/common subsystem: +1. HID core is a common kernel subsystem. * Physical-only or device-presence condition: -2. The conservative trigger requires a malicious or faulty HID device to be attached or accepted. Conservative total: 1 Paranoid signals: * Device mediated external influence: +1. The input can originate from an external HID transport. * Reliable kernel crash / strong DoS: +1. Kernel panic is explicitly described. * Confidentiality impact plausible: +1. The primitive is an OOB read, but no disclosure path is shown, so this is only paranoid C:L reasoning. * Broad/default/common subsystem: +1. HID core is widely enabled and used. * No physical-only penalty in paranoid mode. Wireless HID or already paired devices can make the attack adjacent rather than purely physical. Paranoid total: 4 Not awarded: * No generic strong memory corruption. This is read-only OOB, not OOB write, UAF, double-free, or type confusion. * No LPE bonus. The patch does not show reclaim, overwrite, callback control, refcount takeover, or privilege boundary bypass. * No integrity impact. There is no write primitive. ## 3. Reachability analysis A malicious HID device, faulty HID firmware, or potentially an adjacent wireless HID transport could trigger the malformed numbered report path. Local code execution on the victim is not required if the attacker can deliver HID input through an accepted device path. Namespaces and containers are mostly irrelevant because the vulnerable path is in the host HID input stack. HID support is commonly enabled, but realistic exploitation depends on device attachment, pairing, or control of a HID transport, so this is not ordinary network reachable. Call-site confidence: medium. The affected function and immediate dereference pattern are visible, but the full set of HID transport callers is not included in the supplied patch. ## 4. Severity interpretation This behaves more like a Moderate HID input validation memory-safety issue than an Important-class kernel vulnerability. The realistic impact is kernel crash or warning from an OOB read. The theoretical concern is limited confidentiality exposure from an OOB read, but the patch does not support arbitrary readout, write corruption, or privilege escalation. ## 5. One-sentence report phrase A zero length numbered HID report can reach hid_get_report before length validation, causing an OOB read of data(0) and potentially a kernel panic when a malicious or faulty HID device or adjacent HID transport supplies malformed input. ## 6. Manual review recommendation MANUAL CHECK RECOMMENDED Reason: this is a memory-safety bug in a common HID core path with external device influence and possible kernel panic, but there is no supported write primitive or privilege escalation path in the patch. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: HID: core: Fix OOB read in hid_get_report for numbered reports [ Upstream Commit: f8896b684e246f3f00f45ba2b6803ae59b9cc768 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f8896b684e246f3f00f45ba2b6803ae59b9cc768 Changed files: drivers/hid/hid-core.c 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=f8896b684e246f3f00f45ba2b6803ae59b9cc768 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80604 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80604 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:P/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H The Best / paranoid CVSS vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H The Best / paranoid CVSS score: 7.1 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: 1 Paranoid ActionableScore: 4 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: NO Published priority for this report (same as in Subject): MODERATE REGULAR 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).