[CVE-2026-53086][MODERATE REGULAR] net: bcmgenet: fix racing timeout handler [ Upstream

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

CVE: CVE-2026-53086
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net: bcmgenet: fix racing timeout handler [ Upstream
Commit: e85b0c0a12e967930044608311471b665baa315c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e85b0c0a12e967930044608311471b665baa315c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53086
Analysis date: Wed, 24 Jun 2026 14:57:16 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Ordinary Moderate / Borderline manual review recommended
Manual review required: YES

Summary:
The bcmgenet TX timeout handler could restart and reclaim all TX queues after a single queue timeout, racing with active queues and potentially causing network driver availability impact on affected Broadcom GENET devices.

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

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

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-53086	MODERATE	CHECK	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-362;CWE-667;*CWE-664;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.3';DESCR 'The bcmgenet TX timeout handler could perform global recovery when only one TX queue timed out, including reclaim and wake operations for queues that were still active. This creates race conditions in the network driver TX path and may lead to network disruption, driver malfunction, or kernel availability impact. For the CVSS the PR:N is used in the paranoid vector because an adjacent network attacker may be able to influence traffic conditions without a local account, but reliable triggering is hardware and workload dependent. The issue is not a direct packet parsing bug and no concrete UAF or OOB primitive is visible from the patch. Impact is treated as denial of service rather than confirmed privilege escalation or information disclosure.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Borderline manual review recommended (with actual score 3)	YES	REMOTE INIT SIMPLEFIX RACE NETWORK DMAorINTERRUPT HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	NO	NO	checked

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

ActionableScore=3
ActionableScoreLower=2

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1. A local user may be able to generate outgoing traffic that contributes to TX timeout conditions.
* Availability impact realistic: +1. The bug can disrupt the bcmgenet TX path and network availability.
* Hard or unreliable race / special timing required: -1. The issue depends on a TX timeout and races with still active queues.
* Hardware specific driver path: -1. The bug is limited to Broadcom GENET hardware and is not a common networking core path.

Conservative total: 2

Paranoid additions:

* Firmware or adjacent traffic influenced condition: +1. In a paranoid interpretation, an adjacent network peer or device behavior may help create TX timeout conditions, but this is not a direct remote packet parsing bug.

Paranoid total: 3

No memory corruption score is added. The patch does not show UAF, OOB write, double free, stale callback, refcount misuse, or attacker controlled object reuse.

## 3. Reachability analysis

The most realistic trigger is local traffic generation or a device state that causes one TX queue to time out. The old handler then performed global recovery across all TX queues, racing with queues that were still active.

Remote or adjacent influence is possible only indirectly through traffic and device behavior. This should not be treated as fully network reachable in the same sense as protocol parsing or packet receive bugs.

Namespaces and containers may matter if an untrusted workload can transmit through the affected interface, but the bug is still hardware and workload dependent. No CAP_NET_ADMIN requirement is obvious for merely generating traffic, but reliable reproduction likely needs specific runtime conditions.

## 4. Severity interpretation

This behaves like an ordinary Moderate or borderline actionable Moderate driver DoS. The commit explicitly mentions race conditions, so manual review is reasonable, but the diff only narrows timeout recovery to the affected queue and does not expose a concrete memory corruption primitive.

Theoretical risk is limited to driver state corruption or network disruption. Realistic evidence supports availability impact, not privilege escalation, confidentiality loss, or integrity compromise.

## 5. One-sentence report phrase

The bcmgenet TX timeout handler could restart and reclaim all TX queues after a single queue timeout, racing with active queues and potentially causing network driver availability impact on affected Broadcom GENET devices.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the commit explicitly describes multiple race conditions in a network driver recovery path, but the patch does not show a concrete UAF, OOB write, refcount bug, or privilege escalation primitive, so this should not be auto-escalated to Important without additional evidence.

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

Patch: net: bcmgenet: fix racing timeout handler [ Upstream
Commit: e85b0c0a12e967930044608311471b665baa315c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e85b0c0a12e967930044608311471b665baa315c

Changed files:
  drivers/net/ethernet/broadcom/genet/bcmgenet.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=e85b0c0a12e967930044608311471b665baa315c

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

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

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