From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93064][MODERATE REGULAR] wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser [ Upstream Date: Fri, 18 Sep 2026 05:27:23 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93064 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: 1af000d75b1c96f7cbdf23f14d0ee1c51b12f8e6 List-Id: CVE: CVE-2026-93064 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser [ Upstream Commit: 1af000d75b1c96f7cbdf23f14d0ee1c51b12f8e6 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1af000d75b1c96f7cbdf23f14d0ee1c51b12f8e6 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93064 Analysis date: Fri, 18 Sep 2026 05:27:23 -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-93064 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93064 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-93064 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-93064 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:L/UI:N/S:U/C:L/I:N/A:N';CWE-193;*CWE-200;CWE-532;BEST CVSS score: '3.3';DESCR 'An off by one error in iwl_mvm_frob_txf_key_iter() can leave the final byte of a matched TXF key unsanitized in an iwlwifi firmware dump while overwriting one byte before the matched key. This is primarily a local information exposure issue involving diagnostic dump data rather than a live kernel memory corruption primitive. For the CVSS the PR:L is used in the paranoid score because a local user or service that can access firmware crash dumps or devcoredump output may receive the remaining key byte without full administrative control. The issue is not directly network reachable. Impact is limited confidentiality loss from possible exposure of key material in dumps, with no supported path to privilege escalation or kernel crash.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3) YES REMOTE SIMPLEFIX NETWORK DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=3 ActionableScoreLower=2 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=UNKNOWN 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 Confidentiality plausible. The sanitizer can leave the final byte of matched TXF key material unsanitized in an iwlwifi firmware dump. * +1 Security-sensitive diagnostic artifact. The exposed byte belongs to key material, so this is more sensitive than ordinary debug metadata. Paranoid additional signal: * +1 Product-specific exposure uncertainty. Access to firmware dumps or devcoredump data may be available to a local diagnostics service or delegated local actor in some deployments, so manual review is useful even though ordinary unprivileged access is not established. Non-awarded signals: * +0 Real UAF. No use-after-free or lifetime violation is established. * +0 Memory corruption. The off-by-one affects where a dump buffer sanitizer starts overwriting and leaves one intended byte unchanged. It does not establish live kernel object corruption. * +0 Reliable crash or DoS. No kernel crash, panic, or availability impact is supported. * +0 Integrity impact. No unauthorized modification of protected state is shown. * +0 Remote reachability. Wi-Fi or networking involvement does not make this directly network-triggerable. * +0 Local unprivileged trigger. Ordinary local-user access to the relevant firmware dump is not established. * +0 Strong LPE or weak LPE. No privilege-escalation primitive, arbitrary write, controlled reclaim, callback influence, or credential manipulation is shown. Negative signals: * No host-admin penalty was applied because host-admin-equivalent access to the complete exposure path is not positively established. * No race or rare-hardware penalty was applied. 3. Reachability analysis The vulnerable operation is in the iwlwifi MVM firmware dump sanitization path. The security-relevant exposure occurs only if a firmware dump containing TXF key material is generated and then made readable to an attacker or to a less-privileged local service. Ordinary remote packet traffic is not enough to establish reachability. The patch does not show a direct network trigger that lets a remote Wi-Fi peer read the dump. A local attacker would need access to firmware crash dump output, devcoredump data, debugfs, logs, or a product-specific diagnostics channel. HostAdminRequired is UNKNOWN because the supplied input does not prove whether the relevant dump data is readable only by host root or by a below-host-admin actor in the evaluated product. NamespaceScopedPrivilege is NO because the issue is not a namespace-scoped capability path. Prior privileged setup may exist if firmware dump access is restricted by debugfs, sysfs permissions, or distro/product diagnostic policy, but that is deployment-specific. 4. Primitive and severity interpretation The exact primitive is limited information exposure caused by an off-by-one error in the sanitizer offset. The old code used `i - keylen` even though `i` points to the last matched byte. This overwrites one byte before the matched key and leaves the final key byte unsanitized. This is not an active structured-object UAF, not fixed stale storage, and not a cleanup/destructor lifetime bug. No concrete repeated release or refcount operation exists. PrimitiveClass is NONE because no corruption, lifetime, ownership, authorization bypass, COW violation, or similar kernel-security primitive is established. The demonstrated consequence is limited confidentiality exposure of one byte of key material in diagnostic dump data. A broader key disclosure is not established from this patch alone. ImportantCandidate is NO because the patch does not support memory corruption, privilege escalation, strong boundary bypass, or substantial disclosure. AutoDowngradeAllowed is YES because the issue can be treated as Low-like or ordinary Moderate after product-specific dump exposure is checked. Manual review is still recommended because the affected data is cryptographic key material. Likely operational severity: Low to borderline Moderate, depending mostly on who can read firmware dumps in the target product. 5. One-sentence report phrase An off by one error in the iwlwifi TXF key sanitizer can leave one byte of key material visible in firmware dump data, requiring local access to such dumps and causing limited confidentiality impact only. 6. Manual review recommendation MANUAL CHECK RECOMMENDED The CVE can likely be downgraded in products where firmware dumps are root-only or disabled, but manual confirmation is recommended because the leaked data is key material and dump access policies vary by product. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser [ Upstream Commit: 1af000d75b1c96f7cbdf23f14d0ee1c51b12f8e6 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1af000d75b1c96f7cbdf23f14d0ee1c51b12f8e6 Changed files: drivers/net/wireless/intel/iwlwifi/mvm/ops.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=1af000d75b1c96f7cbdf23f14d0ee1c51b12f8e6 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93064 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93064 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:L/UI:N/S:U/C:L/I:N/A:N The Best / paranoid CVSS score: 3.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).