From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98203][LOW] Input: soc_button_array - check btns_desc->package.count Date: Fri, 09 Oct 2026 04:13:55 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98203 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: c3a94bfedfa2e4c4d37d1181e8db1ab010f1321a List-Id: CVE: CVE-2026-98203 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: Input: soc_button_array - check btns_desc->package.count Commit: c3a94bfedfa2e4c4d37d1181e8db1ab010f1321a Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c3a94bfedfa2e4c4d37d1181e8db1ab010f1321a Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98203 Analysis date: Fri, 09 Oct 2026 04:13:55 -0400 ActionableScore: 2 ActionableScore lower bound: 1 Actionable bucket: Ordinary Moderate Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98203 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98203 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: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-98203 LOW https://www.kernelcve.org/list/?q=CVE-2026-98203 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE AEGIS_AS=1 LEGACY=LOW RESULT=DIFF (independent Legacy and Aegis differ; FINAL: LOW, Aegis: MODERATE) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H';CWE-129;CWE-125;*CWE-20;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.1';DESCR 'An empty ACPI button descriptor package can reach soc_button_get_button_info with package count equal to zero. The function then accesses package element zero even though no element exists, resulting in an out of bounds kernel read. The most likely effects are driver probe failure, invalid interpretation of adjacent memory, or a kernel crash. For the CVSS the PR:H reflects that reliable triggering normally requires administrative control over ACPI table delivery, firmware configuration, or the boot environment. The issue is not network reachable and an ordinary local user cannot normally modify the ACPI package used during device initialization. The demonstrated primitive is an invalid read rather than a use after free or an out of bounds write. Impact is primarily local availability loss, while limited confidentiality impact is retained only in the paranoid assessment because adjacent kernel memory may be read without evidence of a direct disclosure path.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) MAYBE USB SIMPLEFIX HARDWARE - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 2 * Paranoid score: 2 * No floor or cap was applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown Conservative signals: * +1 Weak or indirect corruption candidate. An empty ACPI package reaches an unchecked `elements[0]` access, establishing an out-of-bounds kernel read and invalid structured-object interpretation. * No privilege penalty. Malformed ACPI input is established, but the supplied evidence does not positively resolve whether the complete attacker path requires host administration, firmware control, or another platform-specific mechanism. Paranoid additional signal: * +1 Reliable kernel crash or strong DoS concern. Interpreting memory beyond the empty package as an `acpi_object` may cause invalid subsequent field or pointer consumption during driver initialization, although an actual crash is not shown. Not awarded: * B5-R is not established. There is no heap out-of-bounds write, retry-accumulated offset, attacker-influenced retry sequence, or later consumption of write-corrupted state. * No confidentiality point. No bytes are shown being disclosed to userspace, a device, or the network. * No integrity point. There is no write, lifetime mutation, or modification of protected state. * No UAF, controlled reclaim, arbitrary write, callback influence, or privilege-escalation primitive. * No remote-reachability point. * No extra availability point because the possible kernel crash is the only availability consequence considered. * No hardware rarity penalty. The path is firmware-dependent, but the supplied evidence does not establish uncommon physical hardware as mandatory. 3. Reachability analysis The malformed object is supplied through ACPI during Generic Button Device discovery. An ordinary process cannot directly invoke this package access or modify the relevant ACPI object through a namespace-scoped interface. The complete attacker path is unresolved. Administrative control over ACPI overrides, boot configuration, or firmware may permit triggering, while faulty or malicious firmware can provide the malformed package independently of a runtime host user. Therefore `HostAdminRequired=UNKNOWN` rather than assuming either host-admin or below-host-admin reachability. The operation is not user-namespace or network-namespace scoped. No network trigger, retry loop, runtime ioctl trigger, or repeatable race is established. Prior platform or firmware provisioning is apparently relevant, but the exact attacker-controllable mechanism is not visible. 4. Primitive and severity interpretation The exact primitive is a read from `btns_desc->package.elements[0]` when `package.count` is zero. This is a limited out-of-bounds read and invalid structured-state consumption candidate, not an out-of-bounds write. There is no lifetime transition, stale object, repeated release, refcount mutation, or active-state retirement failure. `RealUAF=NO`. The demonstrated behavior fits `CLASS_C`: invalid kernel memory is read during device initialization, with probe failure or a kernel fault as the credible consequences. A stronger consequence would require evidence that the resulting bogus `acpi_object` fields reach a disclosure, write, or security-sensitive operation. `ImportantCandidate=NO` because the B5-R preservation profile fails at its first requirement and no independent Class A or Class B primitive exists. `AutoDowngradeAllowed=YES` because no unresolved write, lifetime, ownership, or authorization primitive would be discarded. Likely operational severity is Low-like to ordinary Moderate, primarily as a platform initialization robustness or availability issue. 5. One-sentence report phrase An empty ACPI button descriptor package can cause an out-of-bounds kernel read during Generic Button Device initialization, with probe failure or a possible kernel crash as the credible impact and no established write, disclosure, or privilege-escalation primitive. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Review the subsequent uses of `package.elements[0]` to confirm whether malformed type, length, or pointer fields can escape into a stronger operation, but the supplied patch does not justify Important preservation. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: Input: soc_button_array - check btns_desc->package.count Commit: c3a94bfedfa2e4c4d37d1181e8db1ab010f1321a Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c3a94bfedfa2e4c4d37d1181e8db1ab010f1321a Commit description: Check that btns_desc->package.count is not 0 before accessing btns_desc->package.elements[0]. Fixes: 4c3362f ("Input: soc_button_array - add support for ACPI 6.0 Generic Button Device") Cc: stable@vger.kernel.org Reported-by: Shashiko Closes: https://lore.kernel.org/linux-input/20260909091440.3384C1F00A3A@smtp.kernel.org/ Signed-off-by: Hans de Goede Link: https://patch.msgid.link/20260909093934.29411-2-johannes.goede@oss.qualcomm.com Signed-off-by: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman Changed files: drivers/input/misc/soc_button_array.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=c3a94bfedfa2e4c4d37d1181e8db1ab010f1321a ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98203 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98203 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:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H The Best / paranoid CVSS score: 5.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: 2 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: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW 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).