[CVE-2026-97963][LOW] net: stmmac: initialize ptp_lock at probe time [ Upstream

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

CVE: CVE-2026-97963
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net: stmmac: initialize ptp_lock at probe time [ Upstream
Commit: 420315413b29635de1d4ea4142e410e6465260f3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=420315413b29635de1d4ea4142e410e6465260f3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97963
Analysis date: Fri, 25 Sep 2026 13:54:07 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
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-97963	LOW	https://www.kernelcve.org/list/?q=CVE-2026-97963 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-908;CWE-665;CWE-667;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'An uninitialized rwlock in the stmmac driver can be used when a TAPRIO hardware offload schedule is configured while the network interface is down and has never been opened. tc_taprio_configure invokes the PTP gettime64 callback, and stmmac_get_time then acquires the ptp_lock before the existing initialization path has run. Use of an uninitialized lock is undefined behavior and may cause a driver or kernel hang or crash. The issue is not triggered by packet traffic and is not directly network reachable. For the CVSS the PR:L paranoid assumption applies when a user or service has delegated CAP_NET_ADMIN access to configure a TAPRIO qdisc on the affected interface. In normal host deployments the operation typically requires administrator level network configuration privileges. Impact is primarily denial of service. No concrete memory corruption, information disclosure, integrity modification, or privilege escalation primitive is shown by the patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	YES	REMOTE INIT SIMPLEFIX NETWORK HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

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

ActionableScore=1
ActionableScoreLower=0
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 0
* Conservative score: 0
* Raw paranoid score: 1
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate**::

The conservative score has no positive security-impact signal because the patch establishes use of an uninitialized rwlock but does not demonstrate a crash, memory corruption, disclosure, integrity impact, or privilege escalation. The paranoid score adds one point for a technically plausible driver or kernel hang or crash resulting from undefined locking behavior.

2. Signal breakdown

Conservative signals:

* +0 Uninitialized lock invalid-state defect. The patch establishes that ptp_lock can be acquired before rwlock_init has run, but it does not establish a concrete memory-corruption, lifetime, authorization, or security-boundary primitive.
* +0 Reliable kernel crash or strong DoS not awarded. The supplied commit says the behavior is undefined, but provides no crash trace, panic, lockup report, or evidence that failure is reliable.
* +0 Remote reachability not awarded. The path is reached through local TAPRIO qdisc configuration, not packet processing.
* +0 Local unprivileged trigger not awarded. CAP_NET_ADMIN is relevant, but the complete privilege boundary and whether the affected physical device can be controlled from an attacker namespace are not established.
* +0 Confidentiality and integrity not awarded. There is no demonstrated disclosure, unauthorized modification, stale object, UAF, OOB access, arbitrary write, or security-policy bypass.
* +0 Privilege escalation not awarded. Undefined lock use alone is not an LPE primitive.
* +0 No host-admin penalty applied. Host-admin-equivalent privilege is not positively established by the supplied patch.
* +0 No niche-subsystem penalty applied. TAPRIO offload and compatible hardware are prerequisites, but the evidence does not establish that an attacker cannot reach an already-present affected interface.

Paranoid-only signal:

* +1 Plausible availability impact. Acquiring an uninitialized rwlock can plausibly produce a driver or kernel hang or crash, especially with lock debugging or non-default lock state, but this is not demonstrated as reliable.

3. Reachability analysis

The vulnerable operation is local control-plane configuration. A caller configures a TAPRIO qdisc with hardware offload while the affected stmmac network interface is down and has not previously been opened. The TAPRIO configuration path invokes the PTP gettime64 callback, and stmmac_get_time acquires ptp_lock before its former initialization point.

The relevant qdisc configuration operation normally requires CAP_NET_ADMIN. rtnetlink and qdisc capability checks are generally scoped to the user namespace associated with the target network namespace. However, the complete vulnerable operation also requires an affected stmmac device with PTP and TAPRIO EST offload support. The supplied context does not establish that an ordinary attacker can create, move, or control such a physical device from an attacker-owned namespace.

Therefore, HostAdminRequired is UNKNOWN rather than YES or NO. NamespaceScopedPrivilege is also UNKNOWN because only the qdisc control stage is known to be namespace-aware, while complete access to the physical stmmac device and its offload capability is unresolved. There is no network-packet trigger, no prior privileged setup explicitly established, and no race requirement.

4. Primitive and severity interpretation

The exact primitive is acquisition of an uninitialized rwlock in the stmmac PTP time-read path. This is invalid-state and undefined locking behavior, not a use-after-free, stale-object dereference, repeated release, refcount mutation, OOB access, or controlled memory corruption.

The affected object is a driver-private lock, not active structured stale storage. The issue is not a cleanup or destructor lifetime bug. No first lifetime operation may free an object, and no second operation mutates a dangling object lifetime or refcount.

The appropriate classification is CLASS_C because the supported consequence is invalid-state behavior with at most a plausible availability impact. The patch does not establish useful exploitation leverage beyond a possible driver or kernel fault. ImportantCandidate is NO because no meaningful unresolved memory-corruption, ownership, authorization, or security-boundary primitive exists. AutoDowngradeAllowed is YES because this issue can be handled as an ordinary low-priority correctness and potential DoS fix unless external evidence demonstrates a reliable host-wide crash or a weaker-than-expected privilege boundary.

Likely operational severity is low. The practical exposure depends on deployment of a compatible stmmac device with TAPRIO EST offload and on who can configure qdiscs on that device.

5. One-sentence report phrase

An uninitialized stmmac PTP rwlock can be acquired during TAPRIO offload configuration before the interface has been opened, causing undefined locking behavior and a possible local driver or kernel denial of service.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

No concrete corruption, UAF, authorization bypass, remote trigger, or demonstrated reliable crash is established by the supplied patch context.

7. Call-site confidence

Call-site confidence: medium

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

Patch: net: stmmac: initialize ptp_lock at probe time [ Upstream
Commit: 420315413b29635de1d4ea4142e410e6465260f3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=420315413b29635de1d4ea4142e410e6465260f3

Changed files:
  drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
  drivers/net/ethernet/stmicro/stmmac/stmmac_ptp.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=420315413b29635de1d4ea4142e410e6465260f3

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

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

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

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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