[CVE-2026-68292][LOW] ice: prevent tstamp ring allocation for non-PF VSI types [ Upstream

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

CVE: CVE-2026-68292
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: ice: prevent tstamp ring allocation for non-PF VSI types [ Upstream
Commit: 684d4d0bda95a3fb21b3e29ff0f668f657707b54
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=684d4d0bda95a3fb21b3e29ff0f668f657707b54
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68292
Analysis date: Mon, 10 Aug 2026 19:08:20 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A logic error in the Intel ice driver can cause a small `tstamp_ring` memory leak for CTRL VSI rings after ETF offload and PCI reset rebuilds, but exploitation normally requires administrative device control and the impact is limited to slow resource leakage.

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

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

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-68292	LOW	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:N/I:N/A:L';*CWE-401;*CWE-772;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '2.5';DESCR 'A small memory leak in the Intel ice driver can occur when ETF txtime offload is enabled on a PF Tx queue and a later PCI reset rebuilds a CTRL VSI queue with the same queue index. ice_is_txtime_ena checks pf txtime_txqs by queue index without validating that the ring belongs to a PF VSI, so a CTRL VSI ring can be misclassified as txtime enabled and receive a tstamp_ring allocation. CTRL VSI rings have no netdev, so cleanup returns before freeing that allocation. The leak is about 64 bytes per PCI reset and does not indicate UAF, OOB access, arbitrary write, information disclosure, or privilege escalation. For the CVSS the PR:L is used only for the paranoid score because some environments may delegate reset or network administration capability to a reduced capability root, service account, or container admin. Typical deployments are closer to PR:H because enabling ETF and triggering PCI reset are administrative operations. The issue is not network reachable. Impact is limited denial of service risk through slow resource leakage under repeated resets.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-68292 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE LEAK NETWORK TEST  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	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

Positive signals:

* Availability impact possible: +1 in paranoid scoring only. Repeated PCI resets can leak 64 bytes per reset, but this is very slow and not a realistic immediate system-wide DoS.
* Resource leak class: memory leak of `tstamp_ring`, but no extra score beyond limited availability concern because there is no memory corruption primitive.

Negative signals:

* Requires admin/root/CAP_* in typical deployments: -2. Enabling ETF txtime offload and triggering PCI reset are normally administrative operations.
* Rare hardware or configuration dependency: -1. Requires Intel ice hardware with ETF support and a specific PF/CTRL VSI reset rebuild scenario.
* No memory corruption primitive: no UAF, OOB write, double free, type confusion, arbitrary write, or stale callback is shown.
* No confidentiality or integrity impact: the leaked object is small and not exposed back to userspace.

Call-site confidence: high. The commit describes the relevant call chain: `ice_is_txtime_ena()` -> `ice_vsi_cfg_txq()` allocation -> `ice_clean_tx_ring()` early return before `ice_free_tx_tstamp_ring()`.

## 3. Reachability analysis

The bug is locally reachable through device configuration and reset behavior, not through network packet traffic. In typical deployments, the attacker would need administrative control over the ice device configuration and reset path. Namespace or container delegation could lower practical privilege in unusual environments where a service account or container admin can manipulate NIC reset or advanced qdisc offload state, but this is not the default assumption. The affected path is hardware and feature dependent and requires ETF txtime offload plus repeated PCI reset rebuilds.

## 4. Severity interpretation

This behaves like a Low or ordinary Moderate resource leak, not an Important-class kernel vulnerability. The theoretical impact is resource exhaustion, but the demonstrated leak is only 64 bytes per PCI reset and requires privileged, repeated reset operations. There is no evidence of memory corruption, privilege escalation, sensitive data disclosure, or a remotely reachable trigger.

## 5. One-sentence report phrase

A logic error in the Intel ice driver can cause a small `tstamp_ring` memory leak for CTRL VSI rings after ETF offload and PCI reset rebuilds, but exploitation normally requires administrative device control and the impact is limited to slow resource leakage.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be auto-closed for urgent security triage because it is a tiny privileged-only memory leak with no concrete corruption, disclosure, privilege escalation, or network reachability.

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

Patch: ice: prevent tstamp ring allocation for non-PF VSI types [ Upstream
Commit: 684d4d0bda95a3fb21b3e29ff0f668f657707b54
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=684d4d0bda95a3fb21b3e29ff0f668f657707b54

Changed files:
  drivers/net/ethernet/intel/ice/ice.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=684d4d0bda95a3fb21b3e29ff0f668f657707b54

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

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

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:L
  The Best / paranoid CVSS score: 2.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).