[CVE-2026-64162][LOW] idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() [ Upstream

[CVE-2026-64162][LOW] idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-64162
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() [ Upstream
Commit: eb5991d4c8ba2e8153dfcda3e66a9608377b7dce
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=eb5991d4c8ba2e8153dfcda3e66a9608377b7dce
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64162
Analysis date: Sun, 19 Jul 2026 14:49:54 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
idpf PTP initialization can schedule the aux worker before read_dev_clk_lock is initialized, allowing a local privileged or delegated device-management actor to trigger a lockdep warning and possible DoS on panic_on_warn systems.

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

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

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-64162	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	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-665;CWE-362;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'idpf PTP initialization can schedule the PTP aux worker before read_dev_clk_lock is initialized. The worker may run immediately and enter the clock read path, where spin_lock is taken on an uninitialized lock and lockdep reports a non-static key warning. For the CVSS the PR:L is used in the paranoid interpretation only when a reduced privilege service, container root, or delegated device management role can trigger idpf reset or driver recovery without full host administrator control. The issue is not network reachable and is triggered through local device initialization or reset paths rather than packet traffic. Impact is primarily denial of service or warning based failure, especially on systems where warnings are treated as fatal. No UAF, OOB access, information leak, or arbitrary write primitive is indicated by the code change.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	REMOTE LOCK INIT NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	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

Triggered positive signals:

* Availability impact realistic: +1 only in paranoid interpretation. The issue can become a DoS if lockdep warning paths are configured to panic or if the warning disrupts recovery, but the patch primarily shows a lockdep warning rather than a normal crash.
* Local reduced-privilege trigger: +1 only as a paranoid assumption. This applies only if a delegated device-management service, container root, or reduced-capability operator can trigger idpf reset or recovery.

Negative or limiting signals:

* Requires admin/root/CAP level control in typical deployments: -2 conservative. Reliable triggering normally requires driver load, device reset, or control of the Intel idpf device.
* Hard timing / initialization race: -1. The worker must run after scheduling but before the spinlock is initialized.
* Rare hardware / driver-specific condition: -1 conservative. The affected path requires idpf hardware and PTP initialization.
* WARN_ON continuation rule: no strong DoS point by default. The described failure is a lockdep non-static key warning, not a demonstrated Oops, UAF, double-free, OOB write, or arbitrary write.

Not awarded:

* No remote/network-triggerable signal. Packet traffic does not directly reach this initialization ordering bug.
* No memory corruption signal. The patch moves spin_lock_init earlier and does not show UAF, OOB access, double-free, type confusion, or attacker-controlled overwrite.
* No privilege escalation signal. There is no concrete primitive for LPE.
* No confidentiality or integrity impact. No leak or write primitive is indicated.

Call-site confidence: high. The commit message provides the worker path and the diff shows the initialization order change in idpf_ptp_init().

## 3. Reachability analysis

The bug is triggered through local device initialization or reset paths in the idpf driver with PTP support. In typical deployments this requires administrative control over the driver or PCI network device, so conservative reachability is privileged local only. Namespaces or containers only matter if device reset or driver recovery is delegated to a less privileged environment, which is why the paranoid score considers PR:L style reachability. The path is not network reachable through ordinary packet traffic. Realistic exploitation conditions are narrow and depend on timing of the PTP aux worker plus the affected idpf/PTP configuration.

## 4. Severity interpretation

This behaves like a Low-like or ordinary Moderate reliability bug, not an Important-class vulnerability. The theoretical concern is an uninitialized spinlock being taken by a worker, but the demonstrated effect is a lockdep warning. There is no evidence of exploitable memory corruption, object lifetime misuse, privilege escalation, or sensitive data exposure. Manual escalation is not justified unless the target product treats warnings as fatal and exposes device reset to untrusted local users.

## 5. One-sentence report phrase

idpf PTP initialization can schedule the aux worker before read_dev_clk_lock is initialized, allowing a local privileged or delegated device-management actor to trigger a lockdep warning and possible DoS on panic_on_warn systems.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: the issue is driver-specific, local, timing-dependent, normally privileged, and the patch shows an initialization ordering fix with no concrete memory corruption or privilege escalation primitive.

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

Patch: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() [ Upstream
Commit: eb5991d4c8ba2e8153dfcda3e66a9608377b7dce
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=eb5991d4c8ba2e8153dfcda3e66a9608377b7dce

Changed files:
  drivers/net/ethernet/intel/idpf/idpf_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=eb5991d4c8ba2e8153dfcda3e66a9608377b7dce

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

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

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