[CVE-2026-68291][LOW] idpf: fix max_vport related crash on allocation error during init [ Upstream

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

CVE: CVE-2026-68291
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: idpf: fix max_vport related crash on allocation error during init [ Upstream
Commit: 9fbe22b7aff0a65984d78ee6b93e2f8179abd1f5
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9fbe22b7aff0a65984d78ee6b93e2f8179abd1f5
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68291
Analysis date: Mon, 10 Aug 2026 11:20:50 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like. Auto-close candidate
Manual review required: NO

Summary:
`idpf may crash during reset or driver removal after an init allocation failure because max_vports is set before related vport arrays are fully allocated, causing NULL dereference in cleanup paths.`

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

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

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-68291	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:H';**CWE-476;CWE-665;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'idpf could crash after an init allocation failure because adapter max_vports was populated before the vports netdevs and vport_config buffers were fully allocated. Later reset or driver removal paths may use max_vports as a loop bound and dereference NULL or uninitialized vport related arrays, causing a kernel crash in idpf_remove. The realistic impact is local denial of service only. No UAF OOB access information leak or arbitrary write primitive is indicated by the code change. For the CVSS the PR:L is used for paranoid scoring because some deployments may delegate device reset or recovery control to a reduced capability root service account or container admin, while the common case still requires administrator controlled driver load or removal. The issue is not network reachable by ordinary packet traffic and requires a failed initialization state before the crashing cleanup path is reached.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like. Auto-close candidate (with actual score 1)	YES	REMOTE DANGER NULLPTR VIRT INIT NETWORK KERNEL_PANIC_PLUS_UAF 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. Auto-close candidate**::

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The commit includes a concrete NULL pointer dereference in `idpf_remove()` after failed initialization followed by reset or module removal.
* Requires admin/root/CAP_* in typical deployments: -2. The realistic trigger path involves driver load, reset, or `rmmod`, normally requiring root or equivalent device-management privileges.
* Hard or special condition required: -1. The crash requires an allocation failure during init that leaves `max_vports` inconsistent with allocated arrays.
* Rare and difficult-to-reach subsystem/configuration: -1. This is specific to Intel `idpf` hardware and a driver error path, not a broadly exposed kernel interface.

Paranoid adjustment:

* Use 1 instead of 0 if reduced-capability root, delegated device management, or container-admin-like environments can trigger reset or recovery paths without full host-root equivalence.

No added signals:

* No generic memory corruption. The patch and trace show NULL dereference, not UAF, OOB write, double-free, type confusion, or arbitrary write.
* No LPE plausibility. There is no reclaim, controlled overwrite, stale callback, refcount takeover, or attacker-controlled object replacement.
* No network reachability. Ordinary packet traffic does not appear to trigger the bug.
* No confidentiality or integrity impact.

Call-site confidence: high. The trace shows `idpf_remove()` and the diff directly explains the bad loop bound caused by premature `adapter->max_vports` assignment.

## 3. Reachability analysis

The bug is reachable after `idpf_vc_core_init()` sets `adapter->max_vports` before all related `vports`, `netdevs`, and `vport_config` allocations complete. If allocation later fails, cleanup, reset, or driver removal can iterate using a nonzero `max_vports` and dereference NULL state.

Typical exploitation requires local administrative control over the driver or device lifecycle, such as module removal, PCI driver detach, or reset handling. Namespaces or containers only matter if they are granted delegated device-management capabilities, which is not the normal deployment model. The path is not remotely reachable through network packets.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like kernel DoS issue. The realistic impact is a local privileged kernel crash after a failed initialization state. Theoretical memory corruption is not supported by the patch because the failure mode is a NULL pointer dereference caused by inconsistent initialization bookkeeping.

This should not be treated as Important-class without additional evidence of UAF, OOB access, controlled corruption, privilege escalation, or remote reachability.

## 5. One-sentence report phrase

`idpf may crash during reset or driver removal after an init allocation failure because max_vports is set before related vport arrays are fully allocated, causing NULL dereference in cleanup paths.`

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be auto-closed for priority triage purposes because it is a local privileged DoS-only NULL dereference in a driver initialization error path, with no evidence of memory corruption, LPE, sensitive data exposure, or network-triggerable attack surface.

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

Patch: idpf: fix max_vport related crash on allocation error during init [ Upstream
Commit: 9fbe22b7aff0a65984d78ee6b93e2f8179abd1f5
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9fbe22b7aff0a65984d78ee6b93e2f8179abd1f5

Changed files:
  drivers/net/ethernet/intel/idpf/idpf_virtchnl.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=9fbe22b7aff0a65984d78ee6b93e2f8179abd1f5

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

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

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