[CVE-2026-74264][MODERATE 7.0] net: watchdog: fix refcount tracking races [ Upstream

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

CVE: CVE-2026-74264
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net: watchdog: fix refcount tracking races [ Upstream
Commit: 446fe8ce699ce0a4d702f7b0fcdb50de340b9260
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=446fe8ce699ce0a4d702f7b0fcdb50de340b9260
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74264
Analysis date: Sun, 16 Aug 2026 01:37:24 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A race in netdev watchdog refcount tracking can corrupt ref_tracker list state during concurrent watchdog up, down, and timer execution, causing a kernel BUG and local DoS, with manual review recommended because the bug involves lifetime corruption in common netdev code.

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

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

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 7.0
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-74264	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';CWE-362;CWE-667;*CWE-416;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'A race in netdev watchdog refcount tracking can occur between netdev_watchdog_up(), dev_watchdog(), and netdev_watchdog_down() because watchdog_dev_tracker ownership was not synchronized. Concurrent paths can overwrite or release the same tracking state and then ref_tracker_free can hit list_del corruption, leading to a kernel BUG or panic. For the CVSS the PR:L is used for the paranoid score because reliable triggering can be possible for a local user or container context with delegated network administration over netdev state, rather than full host root in all deployments. The issue is not directly network reachable through packet input, although link state changes, TX timeouts, or virtual netdev management can influence the affected control path. Impact is at least denial of service, and the race plus list corruption makes limited confidentiality or integrity impact a manual-review concern, but there is no demonstrated arbitrary write primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)	YES	LOCK DANGER INIT RACE UAF KERNEL_PANIC_PLUS_UAF TIMER HARDWARE LINUS QDISC SYZBOT  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

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

ActionableScore=5
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**

## 2. Signal breakdown

Paranoid score signals:

* Memory corruption, weak/indirect corruption candidate: +1. The race can corrupt ref_tracker list state through concurrent overwrite or release of watchdog_dev_tracker, but no controlled overwrite, reclaim, type confusion, or callback control is shown.
* Real lifetime corruption: +1. The bug is a refcount tracker lifetime and ownership race involving netdev_hold and netdev_put state.
* Reliable kernel crash / strong DoS: +1. syzbot observed list_del corruption followed by kernel BUG and Oops.
* Broad/default/common subsystem: +1. The affected code is in generic netdev watchdog and qdisc/device activation paths, not a rare driver-only path.
* Privileged kernel/device-management memory corruption path: +1. The corruption occurs in trusted netdev lifecycle and watchdog reference tracking code.
* Hard or unreliable race / special timing required: -1. The bug depends on concurrent watchdog up, down, and timer execution.
* Requires CAP_NET_ADMIN in typical deployments: 0 to -2 depending on environment. Conservative scoring applies the privilege penalty. Paranoid scoring reduces it because delegated network administration, containers, or user namespace setups can make netdev state manipulation reachable from less trusted contexts.

Conservative score uses the same core corruption and DoS signals but applies the typical CAP_NET_ADMIN penalty more strictly, resulting in ActionableScoreLower=3.

## 3. Reachability analysis

The bug is not directly network reachable through ordinary packet input. It is triggered through netdev control paths involving carrier changes, watchdog timer scheduling, device activation, deactivation, and linkwatch workqueue processing. In typical host deployments, reliable triggering likely requires CAP_NET_ADMIN or control over virtual or physical netdev state.

Namespaces and containers matter. If an untrusted user can obtain network administration over a net namespace, create or manipulate virtual devices, or indirectly drive carrier and activation paths, the effective privilege requirement can be closer to local low privilege than full host root. The path is part of common networking core infrastructure, but the exact trigger requires a race and suitable netdev watchdog activity.

Call-site confidence: high. The patch shows the affected call paths in dev_watchdog, netdev_watchdog_up, netdev_watchdog_down, netif_carrier_on, and initialization of the new synchronization fields.

## 4. Severity interpretation

This is stronger than an ordinary low-risk DoS because the observed crash comes from ref_tracker list corruption caused by a real synchronization and lifetime bug. However, it should not be treated as an Important-class LPE based on the provided evidence alone. The patch and trace show list corruption and a kernel crash, but do not show attacker-controlled reclaim, object replacement, type confusion, arbitrary write, or callback dispatch.

Realistic impact is local or delegated-admin DoS. Theoretical memory-safety concern exists because the race corrupts lifetime-tracking list state, so manual review is justified. The best practical bucket is Actionable Moderate at minimum, not a strong Important candidate unless additional evidence demonstrates controlled reuse or escalation.

## 5. One-sentence report phrase

A race in netdev watchdog refcount tracking can corrupt ref_tracker list state during concurrent watchdog up, down, and timer execution, causing a kernel BUG and local DoS, with manual review recommended because the bug involves lifetime corruption in common netdev code.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: this is a race with refcount tracking and list corruption in generic networking code. The demonstrated impact is DoS, but the lifetime-corruption nature and possible delegated network-admin reachability make it unsuitable for automatic closure.

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

Patch: net: watchdog: fix refcount tracking races [ Upstream
Commit: 446fe8ce699ce0a4d702f7b0fcdb50de340b9260
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=446fe8ce699ce0a4d702f7b0fcdb50de340b9260

Changed files:
  lib/list_debug.c
  include/linux/list.h
  lib/ref_tracker.c
  include/linux/netdevice.h
  net/sched/sch_generic.c
  net/core/link_watch.c
  kernel/workqueue.c
  kernel/kthread.c
  arch/x86/kernel/process.c
  arch/x86/entry/entry_64.S
  net/core/dev.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=446fe8ce699ce0a4d702f7b0fcdb50de340b9260

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

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

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

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: 3
  Paranoid ActionableScore: 5

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 7.0

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