[CVE-2026-53008][MODERATE REGULAR] wifi: brcmfmac: Fix error pointer dereference [ Upstream

[CVE-2026-53008][MODERATE REGULAR] wifi: brcmfmac: Fix error pointer dereference [ Upstream

[AL-KERNEL]

CVE: CVE-2026-53008
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: wifi: brcmfmac: Fix error pointer dereference [ Upstream
Commit: cbea71b4480394708f9a6e007a0385acfe5e1ec8
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cbea71b4480394708f9a6e007a0385acfe5e1ec8
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53008
Analysis date: Fri, 26 Jun 2026 14:47:29 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A race in the Intel ice TX timestamp cleanup path can leave TXTIME visible while the timestamp ring pointer is NULL, allowing a privileged local reconfiguration race with TX traffic to crash the kernel.

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

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

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: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-53008	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-362;**CWE-476;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A race in the Intel ice driver can occur when TX timestamp ring cleanup runs concurrently with ice_tx_map. The TXTIME flag could remain visible after tx_ring tstamp_ring was cleared, allowing another CPU to enter the TXTime path and dereference a NULL timestamp ring pointer. This can crash the kernel and cause denial of service. For the CVSS the PR:L is used for the paranoid view because a delegated service account or container root with network administration rights may be able to reconfigure or reset the interface while transmit traffic is active. The issue is not directly network reachable because packet traffic alone does not trigger the cleanup path. Impact is denial of service only based on the visible primitive, with no concrete arbitrary write or information leak shown by the code context.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) 	MAYBE	REMOTE NULLPTR RACE NETWORK HARDWARE TEST  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=1

ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

* Reliable kernel crash / strong DoS: +1
  The visible primitive is a NULL pointer dereference in `ice_tx_map()` when `tx_ring->tstamp_ring` is observed as NULL while TXTIME is still enabled.

* Hard or unreliable race / special timing required: -1
  Triggering requires a race between TX timestamp ring cleanup and the TX mapping path on another CPU.

* Requires admin/root/CAP_NET_ADMIN in typical deployments: -2
  The cleanup/reconfiguration path is normally controlled by privileged network administration or driver/device management operations.

* Rare AND difficult-to-reach subsystem/configuration: -1
  The affected path is specific to the Intel ice driver with TX timestamp / TXTime support, not a default core networking receive or transmit path for all systems.

* Availability impact realistic: not additionally counted
  The crash impact is already counted as strong DoS, and there is no evidence of persistent corruption or broader data loss.

* Generic memory corruption: not counted
  The patch and commit describe a NULL dereference, not UAF reclaim, OOB write, arbitrary write, or controlled object corruption.

## 3. Reachability analysis

The bug is locally triggerable only in practical terms. An attacker would need a way to cause TX timestamp ring cleanup or interface reconfiguration while TX traffic is active. In normal deployments this requires CAP_NET_ADMIN or equivalent host administrative control over the Intel ice interface. Packet traffic alone does not appear sufficient to trigger the cleanup path, so this is not realistically network reachable.

Namespaces or containers may lower the practical privilege boundary if a container root or service account is delegated network administration over the affected device. That supports a paranoid PR:L interpretation for CVSS-style analysis, but it still does not make the issue unprivileged or remotely reachable.

## 4. Severity interpretation

This behaves like an ordinary Moderate / Low-like kernel DoS rather than an Important-class vulnerability. The theoretical concern is a driver race involving pointer lifetime and ordering, but the demonstrated primitive is a NULL pointer dereference only. There is no supported evidence for attacker-controlled memory corruption, information disclosure, privilege escalation, or cross-boundary policy bypass.

## 5. One-sentence report phrase

A race in the Intel ice TX timestamp cleanup path can leave TXTIME visible while the timestamp ring pointer is NULL, allowing a privileged local reconfiguration race with TX traffic to crash the kernel.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: this is a race in a kernel network driver cleanup path, so a short manual review is reasonable, but the current evidence supports DoS-only impact and does not justify Important-class handling.

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

Patch: wifi: brcmfmac: Fix error pointer dereference [ Upstream
Commit: cbea71b4480394708f9a6e007a0385acfe5e1ec8
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cbea71b4480394708f9a6e007a0385acfe5e1ec8

Changed files:
  drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.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=cbea71b4480394708f9a6e007a0385acfe5e1ec8

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

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

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

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: 0
  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: 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).