[CVE-2026-99044][MODERATE 7.0] ice: fix use-after-free in dynamic port cleanup [ Upstream

[CVE-2026-99044][MODERATE 7.0] ice: fix use-after-free in dynamic port cleanup [ Upstream

[AL-KERNEL]

CVE: CVE-2026-99044
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: ice: fix use-after-free in dynamic port cleanup [ Upstream
Commit: 7c1344df1ae0579f57b97647e5203b06496ce10c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7c1344df1ae0579f57b97647e5203b06496ce10c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99044
Analysis date: Tue, 27 Oct 2026 03:07:40 -0400
ActionableScore: 4
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
Dynamic ICE port cleanup reads a freed VSI index and may erase the wrong xarray entry, causing a crash or corrupted driver bookkeeping without a shown controlled-reuse primitive.

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

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

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-99044	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-99044 CHECK WITH IMPACT FROM ORIG NN IMPORTANT | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=4 LEGACY=MODERATE_KPANIC RESULT=SAME V39_AEGIS_ONE_STEP_UP=MODERATE->MODERATE_KPANIC (final reconciliation agrees; DECISION: both MODERATE_KPANIC)	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-416;*CWE-672;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'ice_dealloc_dynamic_port freed dyn_port vsi before reading its idx for xa_erase. This is a concrete use after free read. If the freed VSI memory is reused before the read, the cleanup can erase the wrong xarray entry and may leave a dangling dyn_port entry that is accessed later. The immediate demonstrated impact is a local kernel crash or corrupted driver bookkeeping. A secondary stale pointer use could plausibly produce broader memory corruption, but confidentiality impact, integrity impact, and privilege escalation are not proven by this small patch alone. For the CVSS the PR:H value is used for the base score because reliable triggering normally requires privileged devlink subfunction or dynamic port management. For the CVSS the PR:L value is used for the paranoid score because network administration can be delegated to a service account or restricted management process lacking full root control. AC:H reflects the timing dependent memory reuse needed to turn the direct stale read into persistent xarray corruption. Automated impact decision path. The original SimpleNet classifier selected IMPORTANT. The primary LLM estimated paranoid CVSS 7 and the production ActionableScore returned 4 with recommendation Borderline / manual review recommended. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were ActionableScore thresholds stage IMPORTANT to MODERATE_KPANIC because the ActionableScore threshold rule was applied. KP and FD specialist checks stage MODERATE_KPANIC to MODERATE because KP specialist did not establish a qualifying panic. final reconciliation stage MODERATE to MODERATE_KPANIC because the cross model evidence reconciliation rule was applied. The legacy KP specialist produced a review artifact and its decision was processed by the applicable KP rules. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN5 and DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 3.3 and ActionableScore 4 with primitive class CLASS_B and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is MODERATE_KPANIC.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 4)	MAYBE	REMOTE INIT UAF NETWORK  DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN5 DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP KPANIC V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=4
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw base score: 3.
* Conservative score: 4. Applied the real-UAF floor: 3 -> 4 because a freed structured VSI is read and its index drives `xa_erase()`, while host-admin-only reachability is not positively established.
* Raw paranoid score: 4.
* Paranoid score: 4. The additional point reflects the technically defensible wrong-xarray-entry path; no stronger reclaim or corruption primitive is assumed.
* Final recommended bucket: **Borderline / manual review recommended**::

2. Signal breakdown

* +2: Concrete UAF. `ice_vsi_free(dyn_port->vsi)` can end the VSI lifetime before `dyn_port->vsi->idx` is read.
* +1: Plausible kernel crash/strong DoS from dereferencing freed VSI storage, supported by the supplied triage evidence.
* Paranoid +1: The stale `idx` is consumed by `xa_erase()`, so reuse between free and read can select the wrong dynamic-port entry and corrupt driver bookkeeping.
* No repeated-release point: there is no second `put`, free, or refcount mutation on the VSI.
* No structured-leverage point: attacker-controlled reclaim, replacement contents, or stale `idx` value is not shown.
* No C/I, arbitrary-write, disclosure, or LPE point. A later dangling entry is plausible but no concrete subsequent consumer is supplied.
* NEW52/B5-R does not apply: no retry-accumulated heap OOB write exists.
* B3-PENDING and B4-PENDING do not apply.

3. Reachability analysis

The vulnerable path is dynamic devlink-port cleanup. Creation and deletion of Intel ICE subfunctions normally involve privileged device-management operations, but the supplied evidence does not establish the exact capability check, its user-namespace scope, or a complete delegated trigger. Therefore both effective host-admin requirement and namespace-scoped reachability remain unknown. No ordinary-user trigger, special timing control, or attacker-directed heap reuse is proven.

4. Primitive and severity reading

This is an active structured-object UAF read: the freed VSI’s `idx` is used for an xarray mutation during cleanup. It is stronger than a shallow stale dereference because an altered index can erase the wrong active entry, but the patch does not prove controlled reuse or a later dereference of any resulting dangling entry. It is therefore constrained CLASS_B, with crash and bookkeeping corruption shown or plausibly supported, but no Important-grade exploitation primitive. Auto-downgrade remains allowed, subject to manual confirmation of devlink privilege and downstream xarray consumers.

5. One-sentence report phrase

Dynamic ICE port cleanup reads a freed VSI index and may erase the wrong xarray entry, causing a crash or corrupted driver bookkeeping without a shown controlled-reuse primitive.

6. Manual review advice

MANUAL CHECK RECOMMENDED

Confirm the devlink privilege boundary and whether a wrongly retained dynamic-port entry is later consumed after VSI destruction.

7. Call-site confidence

Call-site confidence: high

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

Patch: ice: fix use-after-free in dynamic port cleanup [ Upstream
Commit: 7c1344df1ae0579f57b97647e5203b06496ce10c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7c1344df1ae0579f57b97647e5203b06496ce10c

Changed files:
  drivers/net/ethernet/intel/ice/devlink/devlink_port.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=7c1344df1ae0579f57b97647e5203b06496ce10c

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

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

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: unknown
  Paranoid ActionableScore: 4

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