From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-80774][MODERATE REGULAR] HID: asus: fix missing hid_is_usb() check [ Upstream Date: Fri, 04 Sep 2026 12:12: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-80774 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: 3 X-AL-KERNEL-Commit: bdb2e0a2a359e473ca5619e35adee89028697239 List-Id: CVE: CVE-2026-80774 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: HID: asus: fix missing hid_is_usb() check [ Upstream Commit: bdb2e0a2a359e473ca5619e35adee89028697239 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bdb2e0a2a359e473ca5619e35adee89028697239 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80774 Analysis date: Fri, 04 Sep 2026 12:12:10 -0400 ActionableScore: 4 ActionableScore lower bound: 3 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-80774 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80774 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-80774 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-80774 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:L/I:L/A:H';CWE-843;*CWE-20;**CWE-476;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '6.6';DESCR 'A type confusion issue in the HID asus driver can occur because to_usb_interface() is called without first verifying that the HID device is backed by a real USB parent. A local user able to create a crafted UHID device can present a device as BUS_USB while the parent object is not a USB interface, causing the driver to interpret the wrong kernel object type and potentially trigger an ASAN splat or kernel crash. For the CVSS the PR:L is used because reliable triggering requires local access to UHID or an equivalent virtual HID creation interface, but does not normally require full administrator privileges if that device node is delegated. The issue is not network reachable and the direct impact is local denial of service. For the paranoid score, limited confidentiality or integrity impact is kept because the primitive is a kernel type confusion and invalid object interpretation, but no direct arbitrary write primitive is evident from the patch.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 4) SKIP CVE-2026-80774 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE USB WARNONLY SIMPLEFIX HARDWARE LINUS INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=4 ActionableScoreLower=3 PrimitiveClass=CLASS_B RealUAF=NO HostAdminRequired=NO NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 3 * Conservative score: 3 * Raw paranoid score: 4 * Paranoid score: 4 * Final recommended bucket: **Borderline / manual review recommended**:: No floor or cap changed the score. 2. Signal breakdown Conservative positive signals: * +1: Weak indirect corruption candidate. The bug is a concrete type confusion / invalid object interpretation because `to_usb_interface()` is used on a HID parent that may not be a real USB interface. * +1: Reliable crash or strong DoS concern. The commit states that a kernel splat is currently triggerable in an ASAN build, and the invalid cast can plausibly fault in normal kernels. * +1: Below-host-admin local reachability. The trigger is through UHID-created devices, which is a local device-interface path rather than a host-admin-only kernel configuration path. Paranoid additional signal: * +1: Weak exploitation concern. The stale assumption about object type leads to USB-specific helpers consuming a non-USB kernel object as if it were `struct usb_interface` / `struct usb_device`. This is more meaningful than a plain NULL dereference, but still not enough for Class A. Non-awarded signals: * +0: RealUAF not awarded. No freed object or post-lifetime stale reference is established. * +0: Concrete repeated release/refcount not awarded. There is no first release followed by a second lifetime mutation on the same dangling reference. * +0: Controlled reclaim not demonstrated. * +0: Arbitrary or directed kernel write not demonstrated. * +0: Confidentiality and integrity impact not awarded conservatively. The patch supports invalid structured interpretation, not a demonstrated read-back, disclosure, or unauthorized write. * +0: Remote reachability not established. This is not triggered by network packets. * +0: Extra availability not awarded. The same splat/crash is already counted once. Negative signals: * No host-admin penalty applied because host-admin-equivalent privilege is not positively established. * No rare-hardware penalty applied. The vulnerable path is HID ASUS driver logic reachable through UHID emulation, not a physical-only device requirement. * No race penalty applied. The bug is not a timing race. 3. Reachability analysis The evaluated attacker is a local user or local process able to create a crafted UHID device. The important condition is access to UHID or an equivalent virtual HID creation interface. That is below full host administrator privilege when the device node is exposed or delegated, but it is still a local interface and not a remote network vector. Namespace-scoped privilege is not established. The trigger is not shown to depend on an attacker-created user or network namespace, and no namespace capability chain is needed for the core issue. No prior host setup is clearly required beyond the ASUS HID driver being present and the relevant device matching path being reachable. The attacker can influence the synthetic HID device identity through UHID. No special physical hardware is required for the synthetic-device trigger described in the commit. No race or narrow timing window is involved. 4. Primitive and severity interpretation The exact primitive is a kernel type confusion / invalid structured object interpretation. The code assumes that `hdev->dev.parent` is a USB interface and applies `to_usb_interface()` without confirming `hid_is_usb(hdev)`. UHID can create a HID device that reports BUS_USB while not having a real USB parent, so the ASUS driver may interpret the wrong kernel object type as USB-specific state. This is not a UAF and not a repeated-release/refcount bug. It is an active structured-object misuse, but the demonstrated consequence is an ASAN splat / plausible kernel crash. There is no shown controlled reclaim, object replacement, arbitrary read/write, callback control, or privilege escalation. PrimitiveClass is CLASS_B because a real kernel type-confusion primitive exists and deserves review, but the evidence does not establish a strong Important-preserving primitive. ImportantCandidate is NO because exploitation leverage beyond crash remains weak and unsupported. AutoDowngradeAllowed is YES because this looks like a constrained local crash/type-confusion issue without demonstrated UAF, boundary bypass, or controlled corruption. Operational severity is borderline Moderate, with manual review recommended due to the type confusion nature. 5. One-sentence report phrase A local UHID user can create a HID device that appears to be USB without a real USB parent, causing the ASUS HID driver to apply USB interface helpers to the wrong kernel object type and potentially trigger a kernel splat or crash. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Reason: the demonstrated impact is mainly local DoS, but the root cause is concrete kernel type confusion rather than a simple NULL dereference or resource leak. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: HID: asus: fix missing hid_is_usb() check [ Upstream Commit: bdb2e0a2a359e473ca5619e35adee89028697239 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bdb2e0a2a359e473ca5619e35adee89028697239 Changed files: drivers/hid/hid-asus.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=bdb2e0a2a359e473ca5619e35adee89028697239 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80774 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80774 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:N/I:N/A:H The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H The Best / paranoid CVSS score: 6.6 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: 3 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).