[CVE-2026-63977][MODERATE 7.0] dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work [ Upstream

[CVE-2026-63977][MODERATE 7.0] dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work [ Upstream

[AL-KERNEL]

CVE: CVE-2026-63977
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work [ Upstream
Commit: e7a33807fb3f87a855993474ac21684ce105927b
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e7a33807fb3f87a855993474ac21684ce105927b
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63977
Analysis date: Sun, 19 Jul 2026 12:09:07 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A race in the zl3073x DPLL change notification workqueue can allow deferred work to run after device teardown and dereference a freed or NULL DPLL device pointer, causing a local kernel crash and raising a limited UAF based privilege escalation concern in delegated device-management environments.

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

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

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-63977	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:H/I:H/A:H';CWE-362;*CWE-416;**CWE-476;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A race condition in the zl3073x DPLL driver can allow change_work to be re-scheduled after cancel_work_sync during device teardown. The work handler may then dereference a freed zl3073x_dpll object or a NULL or stale dpll_dev pointer, which makes this a UAF candidate and not only a simple warning path. For the CVSS the PR:L is used for the paranoid score because a reduced capability root, container root, service account, or delegated DPLL control plane may be able to trigger the configuration path while teardown is controlled by the system. The issue is local and control plane driven, not directly network reachable. Impact is at least denial of service via kernel crash and in the worst defensible case may include confidentiality and integrity impact due to use-after-free memory corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)	YES	LOCK DEADLOCK INIT RACE UAF HARDWARE  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

Conservative signals:

* **Memory corruption, weak/indirect corruption candidate: +1**. The patch explicitly mentions a possible dereference of a freed or NULL `dpll_dev` pointer from delayed `change_work`.
* **Real lifetime corruption: +1**. This is an async workqueue lifetime race around teardown, `cancel_work_sync()`, and object unregister/free.
* **Reliable kernel crash / strong DoS: +1**. A stale or NULL `dpll_dev` dereference can plausibly crash the kernel.
* **Privileged kernel/device-management lifetime path: +1**. The bug is in DPLL device-management code and affects object lifetime during unregister.
* **Hard race / teardown timing: -1**. Triggering depends on rescheduling `change_work` after cancellation during teardown.
* **Requires privileged DPLL/device control in typical deployments: -1**. The path is normally not reachable by a fully unprivileged user, but the penalty is not full `-2` because reduced-capability root, service accounts, or delegated control-plane contexts may be relevant.

Paranoid additions:

* **Weak LPE concern: +1**. The bug is a UAF candidate in an asynchronous workqueue path, not merely a validation failure. No controlled reclaim is shown, so this is not a strong LPE signal.
* **Availability impact realistic: +1**. The failure mode is host-kernel crash or oops during device teardown/configuration, not just a warning.

## 3. Reachability analysis

The likely trigger requires local ability to change DPLL device parameters and race that operation with device teardown or unregister. In typical deployments this implies administrative or device-management privileges, likely root or a process with relevant netlink/device-management capability. It is **not directly network reachable**.

Namespaces and containers may matter if DPLL management is delegated to a reduced-capability service, container root, or orchestration component. In that case the practical PR may be closer to `PR:L` than full host-root, which supports the paranoid score. The affected hardware/driver path is not a broad default kernel path, but once the zl3073x DPLL driver and device are present the bug is in a real control-plane path.

Call-site confidence: **high**, because the patch includes both the scheduling site and the teardown/unregister site.

## 4. Severity interpretation

This behaves above an ordinary Moderate because the patch fixes an actual async lifetime race with a freed or NULL pointer in kernel workqueue context. Realistic demonstrated impact is mainly **local DoS** through kernel crash.

Theoretical memory-corruption impact exists because the stale work item is embedded in an object whose lifetime may have ended, but the patch does not show attacker-controlled reclaim, overwrite, type confusion, refcount takeover, or function-pointer control. Therefore it is best treated as **Actionable Moderate**, with **manual review required**, rather than a clear Strong Important by default.

## 5. One-sentence report phrase

A race in the zl3073x DPLL change notification workqueue can allow deferred work to run after device teardown and dereference a freed or NULL DPLL device pointer, causing a local kernel crash and raising a limited UAF based privilege escalation concern in delegated device-management environments.

## 6. Manual review recommendation

**MANUAL CHECK REQUIRED**

Reason: the patch explicitly describes a race with possible freed-pointer dereference in an async workqueue teardown path. Even though realistic exploitation appears local, timing-dependent, and device-specific, UAF-style lifetime bugs in kernel workqueue code should not be auto-closed without manual review.

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

Patch: dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work [ Upstream
Commit: e7a33807fb3f87a855993474ac21684ce105927b
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e7a33807fb3f87a855993474ac21684ce105927b

Changed files:
  drivers/dpll/zl3073x/dpll.c
  drivers/dpll/zl3073x/dpll.h

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=e7a33807fb3f87a855993474ac21684ce105927b

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

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

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:H/I:H/A:H
  The Best / paranoid CVSS score: 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: 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).