[CVE-2026-64212][MODERATE REGULAR] wifi: iwlwifi: mld: don't dereference a pointer before NULL checking it [ Upstream

[CVE-2026-64212][MODERATE REGULAR] wifi: iwlwifi: mld: don't dereference a pointer before NULL checking it [ Upstream

[AL-KERNEL]

CVE: CVE-2026-64212
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: wifi: iwlwifi: mld: don't dereference a pointer before NULL checking it [ Upstream
Commit: 3a74aaad047353da3344aed32e9042d4f334f926
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3a74aaad047353da3344aed32e9042d4f334f926
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64212
Analysis date: Fri, 24 Jul 2026 12:37:05 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Borderline manual review recommended
Manual review required: YES

Summary:
A NULL pointer dereference in iwl_mld_remove_link can crash the kernel when the iwlwifi MLD link removal path sees a NULL link before the fw_id read, with realistic impact limited to DoS and only a paranoid network-adjacent WiFi trigger concern.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64212 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64212

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-64212	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-252;CWE-754;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.3';DESCR 'A NULL pointer dereference can occur in iwl_mld_remove_link because link fw_id was read before checking whether link is NULL. This can crash the kernel on systems using the iwlwifi MLD link removal path. The realistic trigger is local control over WiFi state or connection teardown, but a network adjacent WiFi trigger may be possible if a malicious access point or nearby radio peer can force the affected MLD link removal state. For the CVSS the PR:N is used only for the paranoid adjacent attack interpretation, where the attacker does not need a local account on the victim but must be in WiFi radio range and able to influence the wireless link state. Impact is denial of service via kernel crash. No direct confidentiality or integrity impact is assigned because this patch shows a NULL dereference rather than a proven UAF write or other memory corruption primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended (with actual score 3)	YES	REMOTE INIT UAF NETWORK  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=3
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 3
* Final recommended bucket: **Borderline manual review recommended**

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1
  A local user or desktop service may be able to influence WiFi connection teardown or link removal state without full root privileges, depending on policy.
* Reliable kernel crash / strong DoS: +1
  The bug is a NULL pointer dereference before the existing NULL check, so the realistic impact is kernel crash or warning plus crash depending on configuration.

Paranoid additional signal:

* Adjacent wireless influence: +1
  A network-adjacent WiFi attacker, such as a malicious AP or nearby radio peer, may be able to influence MLD link state transitions, but the patch does not prove reliable adjacent triggering.

Signals not applied:

* Generic memory corruption: +0
  The patch shows a NULL dereference, not UAF reuse, OOB write, type confusion, double-free, refcount abuse, or controlled overwrite.
* Privilege escalation plausible: +0
  No concrete LPE primitive is visible. The earlier related fix mentions potential UAF, but this patch itself fixes dereference-before-NULL-check and delayed freeing order.
* Confidentiality impact: +0
  No information disclosure path is shown.
* Integrity impact: +0
  No write primitive or policy bypass is shown.
* Broad/default exposure: +0
  iwlwifi is common, but this is the newer MLD link-removal path and likely depends on specific hardware, firmware, and WiFi state.
* Rare subsystem penalty: 0
  Not penalized heavily because iwlwifi is broadly deployed, but MLD-specific reachability limits exposure.

Call-site confidence: medium. The changed function and local lifetime order are visible, but broader call paths that create a NULL link are not included.

## 3. Reachability analysis

The conservative trigger is local interaction with WiFi state, such as connection teardown or link removal through normal userspace networking components. This may be reachable by an unprivileged local desktop user in permissive NetworkManager or similar configurations, but in managed server deployments WiFi control may be restricted.

The paranoid trigger is network-adjacent rather than Internet-remote. A malicious AP or nearby WiFi peer might be able to influence MLD link removal state, but the provided patch does not demonstrate a reliable over-the-air trigger. The issue is not remotely reachable over ordinary IP networking.

The affected path is hardware and configuration dependent. It requires Intel iwlwifi with the MLD code path in use, likely involving newer WiFi capabilities.

## 4. Severity interpretation

This behaves more like an ordinary to borderline Moderate kernel DoS than an Important-class vulnerability. The main demonstrated failure mode is a NULL pointer dereference leading to a crash.

Theoretical concern is slightly elevated because the function performs RCU cleanup and the commit references a previous potential use-after-free fix in the same function. However, this patch does not show attacker-controlled reclaim, stale object reuse, write-after-free, type confusion, callback dispatch, or refcount takeover. Therefore it should not be upgraded to a memory-corruption or LPE candidate based only on this diff.

## 5. One-sentence report phrase

A NULL pointer dereference in iwl_mld_remove_link can crash the kernel when the iwlwifi MLD link removal path sees a NULL link before the fw_id read, with realistic impact limited to DoS and only a paranoid network-adjacent WiFi trigger concern.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the demonstrated primitive is only NULL dereference DoS, but the affected code is a wireless link lifetime path with RCU cleanup and a prior UAF-related fix, so manual review is useful to confirm whether any adjacent-triggered or lifetime-corruption scenario exists beyond the visible crash.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: wifi: iwlwifi: mld: don't dereference a pointer before NULL checking it [ Upstream
Commit: 3a74aaad047353da3344aed32e9042d4f334f926
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3a74aaad047353da3344aed32e9042d4f334f926

Changed files:
  drivers/net/wireless/intel/iwlwifi/mld/link.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=3a74aaad047353da3344aed32e9042d4f334f926

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64212 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64212

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:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.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).