From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93062][LOW] wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments [ Upstream Date: Thu, 17 Sep 2026 22:36:08 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93062 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: 1 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 11dde137f1258004bd1ed76ea2480a641e1fb753 List-Id: CVE: CVE-2026-93062 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments [ Upstream Commit: 11dde137f1258004bd1ed76ea2480a641e1fb753 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=11dde137f1258004bd1ed76ea2480a641e1fb753 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93062 Analysis date: Thu, 17 Sep 2026 22:36:08 -0400 ActionableScore: 1 ActionableScore lower bound: unknown 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-93062 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93062 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-93062 LOW https://www.kernelcve.org/list/?q=CVE-2026-93062 CHECK WITH IMPACT FROM ORIG NN 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:N/I:N/A:H';CWE-369;*CWE-20;CWE-754;BEST CVSS score: '4.4';DESCR 'iwlwifi can reach a divide by zero in iwl_dbg_tlv_alloc_fragments when the firmware monitor TLV provides req_size 0 or max_frags_num 0. The affected values come from firmware debug monitor configuration rather than normal WiFi packet processing, so a remote wireless peer is not expected to trigger this path directly. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over the driver firmware or debug configuration. Impact is denial of service through a kernel exception or driver initialization failure. No memory corruption primitive is visible, so C:N and I:N are used.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) YES REMOTE SIMPLEFIX NETWORK MEMORY DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=YES NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate**:: No floor or cap changed the score. 2. Signal breakdown * +1 Reliable kernel crash / strong DoS: the missing checks for req_size == 0 and num_frags == 0 can lead to a division by zero in iwl_dbg_tlv_alloc_fragments(), causing a kernel exception or driver initialization failure. * +0 Remote reachable: not awarded. The affected values come from firmware debug monitor configuration, not from normal WiFi packet processing. * +0 Firmware-mediated external influence: not awarded as an attacker-controlled firmware or device input path is not established. * +0 Local unprivileged trigger: not awarded. No ordinary local user path to control the firmware monitor TLV is established. * +0 Memory corruption / UAF / OOB: not awarded. The primitive is division by zero only. * +0 Confidentiality / Integrity: not awarded. There is no disclosure, write primitive, ownership violation, or security-boundary bypass. * +0 Extra Availability: not awarded because the same crash or driver failure is already counted once. * No repeated release/refcount operation exists. No first lifetime-ending release is present. No exact dangling reference survives. No second lifetime/refcount mutation occurs. FLOOR 5 does not apply. 3. Reachability analysis Reliable triggering appears to require control over the iwlwifi firmware debug monitor configuration or driver and firmware setup. That is normally host-admin-equivalent control, so HostAdminRequired=YES. The issue is not namespace scoped. No network namespace, user namespace, or delegated capability path is shown for controlling the relevant firmware monitor TLV values. A remote WiFi peer is not expected to reach this path directly because the vulnerable values are configuration values used during debug TLV fragment allocation, not data parsed from ordinary wireless frames. No special race is involved. The trigger is a deterministic invalid configuration state with zero size or zero fragment count. 4. Primitive and severity interpretation The exact primitive is a division by zero caused by missing validation of req_size and num_frags before fragment allocation. This is not an active structured object UAF, not fixed stale storage, and not a cleanup/destructor lifetime bug. There is no concrete repeated release/refcount operation. The demonstrated consequence is denial of service through a kernel exception or driver initialization failure. A stronger consequence such as privilege escalation, arbitrary write, information disclosure, or controlled memory corruption is not supported by the patch context. PrimitiveClass=NONE because no meaningful corruption, lifetime, ownership, authorization, or security-boundary primitive is established. ImportantCandidate=NO because the issue is DoS-only, host-admin-gated in practical triggering, and lacks unresolved memory-corruption leverage. AutoDowngradeAllowed=YES because automatic closure would not discard a concrete corruption, boundary-bypass, UAF, repeated lifetime mutation, or LPE-relevant primitive. Likely operational severity is Low-like to ordinary Moderate. 5. One-sentence report phrase iwlwifi may hit a division by zero in iwl_dbg_tlv_alloc_fragments when firmware monitor debug configuration provides zero req_size or zero num_frags, causing DoS, but reliable triggering appears to require host-admin-level control over driver or firmware debug configuration. 6. Manual review recommendation NO MANUAL CHECK NEEDED Reason: this is a validation-only division-by-zero DoS with no UAF, memory corruption, network trigger, authorization bypass, or plausible privilege-escalation primitive established. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments [ Upstream Commit: 11dde137f1258004bd1ed76ea2480a641e1fb753 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=11dde137f1258004bd1ed76ea2480a641e1fb753 Changed files: drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.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=11dde137f1258004bd1ed76ea2480a641e1fb753 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93062 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93062 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: Not available The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.4 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: unknown Paranoid ActionableScore: 1 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).