From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-89629][MODERATE REGULAR] HID: corsair-void: Check size of status and firmware events before reading them Date: Fri, 11 Sep 2026 23:04:25 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-89629 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: 3 X-AL-KERNEL-ActionableScore-Lower: 2 X-AL-KERNEL-Commit: 79465a30050dad62b3c9e7796368db75dac6fa0d List-Id: CVE: CVE-2026-89629 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: HID: corsair-void: Check size of status and firmware events before reading them Commit: 79465a30050dad62b3c9e7796368db75dac6fa0d Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=79465a30050dad62b3c9e7796368db75dac6fa0d Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89629 Analysis date: Fri, 11 Sep 2026 23:04:25 -0400 ActionableScore: 3 ActionableScore lower bound: 2 Actionable bucket: Borderline / manual review recommended Manual review required: YES Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-89629 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89629 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-89629 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-89629 CHECK WITH IMPACT FROM ORIG NN IMPORTANT Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L';CWE-125;*CWE-20;CWE-126;Other CVSS 'AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L';BEST CVSS score: '4.3';DESCR 'A malformed short HID status or firmware report for the corsair void driver can cause an out of bounds read because corsair_void_raw_event reads data indexes up to 4 before the report length is validated. An attacker would typically need a malicious or compromised HID device, USB dongle, or another way to supply malformed input reports to the host. For the CVSS the PR:N is used because no host user privileges are required once the malicious physical device can deliver HID reports. The issue is not network reachable and is best modeled as a physical device attack. Impact is limited to a small out of bounds read with possible low confidentiality or integrity effects and possible local driver instability, with no evidence of an out of bounds write, UAF, or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3) SKIP CVE-2026-89629 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE OOB USB SIMPLEFIX IMPROVEONLY LINUS PACKET LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=3 ActionableScoreLower=2 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=NO NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 2 * Conservative score: 2 * Raw paranoid score: 3 * Paranoid score: 3 * Final recommended bucket: **Borderline / manual review recommended**:: No floor or cap changed the score. 2. Signal breakdown Conservative positive signals: * +1 Limited read-only OOB primitive. The handler reads data indexes up to 4 for status and firmware reports before checking that the report size is at least 5. * +1 Device-mediated external input. A malformed HID report can be supplied by a malicious or compromised Corsair Void compatible HID device, USB dongle, or equivalent emulated device. Paranoid additional signal: * +1 Low bounded state impact concern. The out-of-bounds byte can be consumed as status or firmware fields and may affect local driver state or cause instability, but this remains constrained and does not establish a stronger primitive. Non-awarded or limiting signals: * +0 No UAF, double free, stale pointer, refcount corruption, or lifetime primitive is established. * +0 No OOB write or arbitrary write is established. * +0 No controlled reclaim, object replacement, callback control, or privilege escalation path is established. * +0 No user-visible information disclosure path is shown. The OOB read is internal to the HID driver. * +0 No reliable host-wide crash is demonstrated. A warning, KASAN report, or driver instability is plausible, but the patch evidence does not establish a dependable kernel panic. * +0 Remote reachability is not established. This is not a network-triggered issue. * +0 Extra availability was not awarded because no distinct strong DoS consequence is demonstrated. * +0 C/I impact was not awarded beyond the paranoid low bounded state concern because the patch only shows a small read before size validation. 3. Reachability analysis The realistic attacker is a physical or device-side attacker able to provide malformed HID input reports to the host. This could be a malicious Corsair Void compatible device, a spoofed USB HID device, a compromised wireless receiver path, or another mechanism that can inject malformed reports into this driver. No host administrator privilege is required once such a device can deliver reports, so HostAdminRequired is NO. This is not a namespace-scoped issue, and network namespaces or capabilities do not materially apply. There is no direct network exposure. Prior host setup is limited to the vulnerable driver being present and bound to a compatible HID device. The attack requires device attachment or device-path influence, not packet traffic or local syscalls by an ordinary user. No race or timing requirement is evident. 4. Primitive and severity interpretation The exact primitive is a small read-only out-of-bounds access in corsair_void_raw_event due to missing minimum report-size validation. The code reads data[1] through data[4] for status and firmware events, while malformed reports may be shorter. This is not an active structured-object UAF and not fixed stale storage after free. It is a bounded input parsing bug in a HID driver. No concrete repeated release or refcount mutation exists. The demonstrated consequence is invalid kernel memory read during report parsing. The plausible consequences are local driver warning, incorrect driver state, or limited instability. A useful disclosure, arbitrary write, LPE, or host-wide reliable crash is not established. PrimitiveClass is CLASS_C because the behavior is primarily an invalid read / constrained OOB condition without an independently useful corruption primitive. ImportantCandidate is NO because there is no meaningful unresolved exploitation leverage beyond a small OOB read. AutoDowngradeAllowed is YES because no Class A primitive, real UAF, authorization bypass, controlled corruption, or repeated lifetime mutation remains unresolved. Likely operational severity is Low to low Moderate, with manual review recommended mainly because it is still a kernel OOB read reachable from malformed device input. 5. One-sentence report phrase A malformed short status or firmware HID report in the corsair void driver can trigger a small out-of-bounds read during raw event parsing, typically requiring malicious or compromised device input and leading at most to limited driver instability or low impact state confusion. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Reason: this is a kernel out-of-bounds read and should be reviewed once, but the primitive is small, physical/device-mediated, and lacks evidence of disclosure, write corruption, UAF, or privilege escalation. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: HID: corsair-void: Check size of status and firmware events before reading them Commit: 79465a30050dad62b3c9e7796368db75dac6fa0d Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=79465a30050dad62b3c9e7796368db75dac6fa0d Commit description: Malformed status and firmware events could cause an out-of-bounds read since the size wasn't being checked. Check the size and warn on unexpected values to avoid this. Fixes: 6ea2a6f ("HID: corsair-void: Add Corsair Void headset family driver") Cc: stable@vger.kernel.org Signed-off-by: Stuart Hayhurst Signed-off-by: Jiri Kosina Signed-off-by: Greg Kroah-Hartman Changed files: drivers/hid/hid-corsair-void.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=79465a30050dad62b3c9e7796368db75dac6fa0d ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-89629 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89629 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:N/S:U/C:L/I:N/A:L The Best / paranoid CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L The Best / paranoid CVSS score: 4.3 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: 2 Paranoid ActionableScore: 3 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).