From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98328][LOW] wifi: mac80211: add HE 6 GHz capability in the scan elems len [ Upstream Date: Sat, 10 Oct 2026 04:57:16 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98328 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: db19d5414227d86cee77a000607a6710d7f36853 List-Id: CVE: CVE-2026-98328 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: wifi: mac80211: add HE 6 GHz capability in the scan elems len [ Upstream Commit: db19d5414227d86cee77a000607a6710d7f36853 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=db19d5414227d86cee77a000607a6710d7f36853 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98328 Analysis date: Sat, 10 Oct 2026 04:57:16 -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-98328 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98328 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-98328 LOW https://www.kernelcve.org/list/?q=CVE-2026-98328 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT LOW AEGIS_AS=0 LEGACY=LOW RESULT=SAME (legacy and Aegis reconciliation agree; DECISION: both 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:N/I:N/A:H';CWE-131;CWE-682;CWE-754;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'mac80211 can underestimate scan_ies_len when HE 6 GHz support is present because the HE 6 GHz Band Capability element is included in probe requests but its size is not reserved. Probe request construction can therefore fail and trigger WARN_ON in __ieee80211_start_scan(). For the CVSS the PR:L reflects that a local user or process must be able to request a WiFi scan, although some systems restrict this operation through CAP_NET_ADMIN or a privileged network service. The issue is not directly network reachable through received wireless traffic. The demonstrated impact is failed scanning and a kernel warning. Availability impact can become high on systems configured with panic_on_warn because the warning may cause a kernel panic. No memory corruption, information disclosure, or privilege escalation primitive is supported by the affected calculation path.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE REMOTE DANGER SIMPLEFIX SYZBOT DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 KPANIC_UNSUPPORTED_REMOVED - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * No floor or cap was applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Memory layout invariant restoration. The patch makes `scan_ies_len` consistent with the HE 6 GHz capability element later emitted into probe requests. * +0 WARN and scan failure. The builder detects insufficient space and fails before the supplied evidence establishes an out-of-bounds access. * +0 Reliable kernel crash. `WARN_ON` alone is not a fatal consequence, and a hypothetical `panic_on_warn` configuration is insufficient for an additional point. * B5-R is not established. There is no confirmed heap OOB write, retry-accumulated index, later consumption of corrupted state, or attacker-controlled retry sequence. * B3-PENDING is not established. No shared or file-backed storage is modified. * B4-PENDING is not established. No authorization decision or mandatory security guard is involved. * No UAF, stale object, repeated release, controlled reclaim, arbitrary write, information disclosure, integrity violation, or privilege-escalation primitive is demonstrated. * Remote reachability is not established. Received wireless traffic does not directly reach the faulty size calculation as an attacker-controlled write primitive. 3. Reachability analysis The vulnerable behavior is reached when a scan is initiated on mac80211 hardware that advertises 6 GHz support. A local process can request scanning through the wireless control plane, but the supplied evidence does not establish whether the complete operation is available to an ordinary user, a network-management service, or an actor with `CAP_NET_ADMIN`. Therefore `HostAdminRequired` and namespace-scoped privilege remain unknown. A 6 GHz-capable wireless device is required, but this is not sufficiently rare to justify a hardware penalty. No race, retry accumulation, special timing, or remote packet trigger is involved. The attacker does not control an overwrite because the demonstrated result is probe-request construction failure followed by a warning. 4. Primitive and severity interpretation The exact defect is an underestimated maximum information-element length. The HE 6 GHz capability element may be generated without its size having been included in `scan_ies_len`. The supplied call-path evidence establishes guarded construction failure and `WARN_ON`, not heap OOB access or corrupted-state consumption. There is no stale storage, active structured-object lifetime violation, cleanup UAF, or repeated lifetime/refcount mutation. The issue is therefore `PrimitiveClass=NONE`. Its demonstrated consequence is a failed scan and kernel warning. Kernel panic under a separately enabled fatal-warning policy is deployment-dependent and is not scored as an established consequence. `ImportantCandidate=NO` and `AutoDowngradeAllowed=YES` because no unresolved corruption, ownership, authorization, or security-boundary primitive remains. 5. One-sentence report phrase mac80211 undercounts the space required for HE 6 GHz probe request elements, causing scan construction to fail and trigger a kernel warning without demonstrated memory corruption or security-boundary impact. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch establishes a detected size-accounting failure rather than an OOB write, UAF, authorization bypass, or other Important-preserving primitive. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: wifi: mac80211: add HE 6 GHz capability in the scan elems len [ Upstream Commit: db19d5414227d86cee77a000607a6710d7f36853 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=db19d5414227d86cee77a000607a6710d7f36853 Changed files: net/mac80211/main.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=db19d5414227d86cee77a000607a6710d7f36853 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98328 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98328 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:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.5 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).