[CVE-2026-68133][LOW] ice: fix PTP Call Trace during PTP release

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

CVE: CVE-2026-68133
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: ice: fix PTP Call Trace during PTP release
Commit: 7d517b255f669cedd09830214d55f2f413b34481
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7d517b255f669cedd09830214d55f2f413b34481
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68133
Analysis date: Mon, 10 Aug 2026 09:15:27 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like. Not an Actionable Moderate candidate
Manual review required: NO

Summary:
An Intel ice PTP state-machine bug can place PTP into an invalid error state after PF reset when initialization failed, causing a kernel BUG during later driver unload, but reliable triggering typically requires local device-management privileges and the impact is DoS only.

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

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

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-68133	LOW	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-703;CWE-665;CWE-754;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'An ice PTP state machine bug can leave PTP in an invalid error state after a PF reset when initialization previously ended in ICE_PTP_UNINIT. A later driver unload may run the PTP release path on resources that were not initialized for that state and can hit a kernel BUG in list_debug, causing a local denial of service. For the CVSS the PR:L is used for the paranoid score because some environments can delegate reset or device management capability to a local service account or reduced capability administrator, although typical reliable triggering needs administrative control of the ice device. The issue is not network reachable and is tied to local device reset and unload operations on systems using the Intel ice driver with PTP state affected by PF passthrough or similar setup. Impact is denial of service only. No concrete UAF, OOB access, information leak, or privilege escalation primitive is evident from the patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like. Not an Actionable Moderate candidate (with actual score 1)	YES	REMOTE DANGER INIT SIMPLEFIX NETWORK  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. Not an Actionable Moderate candidate**

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1
  The commit shows a kernel BUG in `lib/list_debug.c` during `ice_ptp_release()` on driver unload.

* Requires admin/root/CAP_* in typical deployments: -2
  Reliable triggering appears to require PF reset plus driver unload or device lifecycle control, which is normally root or administrator controlled.

* Rare or difficult-to-reach configuration: -1
  The observed path depends on Intel `ice` hardware, PTP state handling, PF passthrough or similar setup, and a specific failed initialization state.

Conservative total is below zero, rounded to 0.

Paranoid adjustment:

* Paranoid score: 1
  If device reset or driver lifecycle operations are delegated to a reduced-capability local service account or VM administrator, the full admin penalty can be relaxed, but the issue still remains DoS-only with no demonstrated memory corruption primitive.

No signals applied:

* No remote/network-triggerable path.
* No local unprivileged trigger shown.
* No UAF, OOB write, double-free, type confusion, refcount abuse, callback control, or attacker-controlled reclaim.
* No confidentiality or integrity impact supported.
* No privilege escalation path supported.

## 3. Reachability analysis

The bug is reachable through a local device-management path in the Intel `ice` driver. The described sequence requires PTP initialization to fail into `ICE_PTP_UNINIT`, then a PF reset, then later driver unload or feature teardown. In normal host deployments, these operations require administrative control over the NIC, driver, or PCI device lifecycle.

Namespaces and containers do not normally make this reachable unless a container or service account is explicitly delegated meaningful device-management privileges. The path is not packet-triggered and is not remotely reachable through ordinary network traffic. Realistic exploitation conditions are narrow and tied to hardware, PTP state, and PF passthrough or equivalent reset behavior.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like robustness issue rather than an Important-class vulnerability. The practical impact is a local kernel crash during driver unload or teardown. The patch fixes an invalid PTP state-machine transition, not a concrete memory corruption primitive.

Theoretical impact beyond DoS is not supported by the patch context. The observed failure is a `BUG` from list debugging during release, but there is no evidence of attacker-controlled stale object reuse, writable UAF, object replacement, arbitrary write, information disclosure, or privilege escalation.

## 5. One-sentence report phrase

An Intel ice PTP state-machine bug can place PTP into an invalid error state after PF reset when initialization failed, causing a kernel BUG during later driver unload, but reliable triggering typically requires local device-management privileges and the impact is DoS only.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be handled as a low-priority DoS-only driver robustness fix unless the evaluated product delegates NIC reset or driver lifecycle control to untrusted tenants.

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

Patch: ice: fix PTP Call Trace during PTP release
Commit: 7d517b255f669cedd09830214d55f2f413b34481
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7d517b255f669cedd09830214d55f2f413b34481

Commit description:

If a PF reset occurs when the PTP state is ICE_PTP_UNINIT, then
ice_ptp_rebuild() will update the state to ICE_PTP_ERROR. This will
result in the following PTP release call trace during driver unload:

    kernel BUG at lib/list_debug.c:52!
    ice_ptp_release+0x332/0x3c0 [ice]
    ice_deinit_features.part.0+0x10e/0x120 [ice]
    ice_remove+0x100/0x220 [ice]

This was observed when passing PF1 through to a VM. ice_ptp_init()
fails because ctrl_pf is NULL and sets the state to ICE_PTP_UNINIT.

Fix by detecting the ICE_PTP_UNINIT state in ice_ptp_rebuild() and
returning without error, preventing the invalid state transition to
ICE_PTP_ERROR. The only valid path to ICE_PTP_ERROR is from
ICE_PTP_RESETTING after a failed rebuild.

Fixes: 8293e4c ("ice: introduce PTP state machine")
Cc: stable@vger.kernel.org
Signed-off-by: Paul Greenwalt <paul.greenwalt@intel.com>
Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Tested-by: Rinitha S <sx.rinitha@intel.com> (A Contingent worker at Intel)
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Link: https://patch.msgid.link/20260717185340.3595286-10-anthony.l.nguyen@intel.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  lib/list_debug.c
  drivers/net/ethernet/intel/ice/ice_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=7d517b255f669cedd09830214d55f2f413b34481

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

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

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