[CVE-2026-68362][MODERATE REGULAR] wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-68362
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin [ Upstream
Commit: e517e207300edcf7f3a8f6c45f9155c0e419ffb9
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e517e207300edcf7f3a8f6c45f9155c0e419ffb9
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68362
Analysis date: Mon, 10 Aug 2026 13:49:38 -0400
ActionableScore: 3
ActionableScore lower bound: 1
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
An ath11k firmware ready error can leave the driver falsely marked as registered, causing a later SSR restart to dereference uninitialized SRNG state and crash the kernel, with practical exposure depending on whether firmware failure or restart can be triggered by adjacent WiFi conditions.

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

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

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-68362	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-703;CWE-665;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.3';DESCR 'ath11k can enter an inconsistent registered state when ATH11K_QMI_EVENT_FW_READY sets ATH11K_FLAG_REGISTERED even though ath11k_core_qmi_firmware_ready() failed. A later subsystem restart can follow the registered restart path and dereference uninitialized srng members in ath11k_hal_srng_access_begin, causing a kernel crash. For the CVSS the PR:N is used for the paranoid score only for deployments where an adjacent WiFi attacker can trigger firmware failure or SSR without a local account. The base case is local administrative control of driver load, device reset, or firmware recovery, so remote public Internet exposure is not expected. Impact is denial of service only because the patch context shows a NULL pointer dereference and not a UAF, OOB write, information leak, or arbitrary write primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 2)	YES	REMOTE DANGER NULLPTR INIT NETWORK LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	NO	NO	checked

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

ActionableScore=3
ActionableScoreLower=1

## 1. ActionableScore

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

## 2. Signal breakdown

Paranoid signals:

* Firmware-mediated external influence: +1
  A non-local attacker may plausibly influence WiFi firmware behavior or trigger firmware restart conditions, but the patch does not prove direct packet-level reachability.

* Reliable kernel crash / strong DoS: +1
  The commit gives a concrete NULL pointer dereference call trace in `ath11k_hal_srng_access_begin()` during SSR restart.

* Broad/default/common subsystem exposure: +1
  WiFi drivers are common, but this is limited to affected ath11k hardware and firmware paths, so this is a weak exposure signal.

Conservative suppressors:

* Requires admin/root/device-management control in typical deployments: -2
  The reliable base trigger appears to involve driver load, firmware-ready failure, device restart, or SSR handling, which is normally controlled by kernel/device/administrator paths.

Not counted:

* No generic memory corruption signal.
  The patch shows NULL pointer dereference from uninitialized SRNG state, not UAF, OOB write, double free, type confusion, or arbitrary write.

* No privilege escalation signal.
  There is no concrete reclaim, overwrite, stale callback, refcount manipulation, or attacker-controlled object replacement.

* No confidentiality or integrity signal.
  The demonstrated impact is kernel crash only.

## 3. Reachability analysis

The conservative trigger is local or device-management related: failed firmware ready handling followed by subsystem restart. In normal deployments, an ordinary local user usually cannot directly force this path without privileged device control.

The paranoid trigger is adjacent or firmware-mediated: if malformed WiFi activity or environmental conditions can crash or reset the firmware, then an attacker near the WiFi interface might indirectly reach the bad restart path. This is not general network reachability and should not be treated as AV:N. Namespaces do not materially lower the privilege requirement unless the environment delegates real WiFi device control into a container.

The path is default only on systems using affected ath11k hardware and firmware, especially the tested WCN6750 class. Call-site confidence: high for the crash path because the commit includes both the failing call trace and the exact state flag misuse.

## 4. Severity interpretation

This behaves like an ordinary Moderate to borderline actionable Moderate issue. The realistic impact is DoS via kernel crash. The theoretical concern is that WiFi firmware or SSR paths may be externally influenced, but the patch does not show a memory corruption primitive or LPE path.

The paranoid score is raised only to avoid auto-closing a potentially adjacent-triggerable WiFi kernel crash. It is not an Important candidate based on the provided evidence.

## 5. One-sentence report phrase

An ath11k firmware ready error can leave the driver falsely marked as registered, causing a later SSR restart to dereference uninitialized SRNG state and crash the kernel, with practical exposure depending on whether firmware failure or restart can be triggered by adjacent WiFi conditions.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: confirmed impact is DoS-only NULL dereference, but manual review is useful to determine whether affected hardware allows reliable adjacent WiFi or firmware-mediated triggering.

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

Patch: wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin [ Upstream
Commit: e517e207300edcf7f3a8f6c45f9155c0e419ffb9
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e517e207300edcf7f3a8f6c45f9155c0e419ffb9

Changed files:
  drivers/net/wireless/ath/ath11k/qmi.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=e517e207300edcf7f3a8f6c45f9155c0e419ffb9

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

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

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:H/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: 1
  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).