[CVE-2026-99043][IMPORTANT] ice: fix metadata_dst refcount handling on representor teardown [ Upstream

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

CVE: CVE-2026-99043
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: NO
Patch: ice: fix metadata_dst refcount handling on representor teardown [ Upstream
Commit: 1f263235651775f93c15d90c9f25c3f4a4ef6512
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1f263235651775f93c15d90c9f25c3f4a4ef6512
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99043
Analysis date: Mon, 26 Oct 2026 16:05:21 -0400
ActionableScore: 5
ActionableScore lower bound: unknown
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
ICE representor teardown can directly free a metadata dst still referenced by queued skbs, causing a later host networking operation to use or refcount-mutate the freed object.

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

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

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: IMPORTANT
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-99043	IMPORTANT	https://www.kernelcve.org/list/?q=CVE-2026-99043 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT IMPORTANT AEGIS_AS=6 LEGACY=IMPORTANT RESULT=SAME INDEPENDENT_LEGACY=MODERATE_KPANIC INDEPENDENT_RESULT=DIFF TEMP_KPANIC_MERGE=IMPORTANT_WINS_DISAGREEMENT PRE_MERGE_LEGACY=MODERATE_KPANIC (final reconciliation agrees; DECISION: both IMPORTANT)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;*CWE-672;Other CVSS 'AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7.1';DESCR 'The ICE switchdev representor teardown path can free repr dst through metadata_dst_free even while queued skbs hold references acquired by dst_hold. If the representor is removed while packets remain in a lower device qdisc, later skb processing or reference release can access freed memory and create a race driven use after free with kernel crash and potential memory corruption impact. Reachability requires an ICE switchdev representor, attacker influenced traffic retained in a queue, and concurrent representor teardown. AV:A reflects the VF or representor data path rather than arbitrary Internet reachability. For the CVSS the PR:L value reflects that an attacker needs tenant or local access to drive representor traffic, while teardown commonly depends on a host lifecycle operation. AC:H reflects the required timing window and queue state. The paranoid HHH impact accounts for possible allocator reuse around the stale dst object, but controlled disclosure, arbitrary write, and privilege escalation are not proven. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 7.1 and the production ActionableScore returned 5 with recommendation Actionable Moderate / Strong Important candidate requiring manual review. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to IMPORTANT because the CVSS score, vector or bug class threshold rule was applied. KP and FD specialist checks stage IMPORTANT to MODERATE_KPANIC because KP specialist did not establish a qualifying panic. final reconciliation stage MODERATE_KPANIC to IMPORTANT because KP specialist did not establish a qualifying panic. 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 INCREASED_TO_HIGH_BASED_ON_GUESSCVSS and DECREASED_TO_MODERATE7_BASED_ON_FALSEPOSCHECKOFKP and TEMP_KPANIC_MERGE_IMPORTANT_WINS and KPANIC_UNSUPPORTED_REMOVED. The independent weaker Aegis shadow evaluated CVSS 4.2 and ActionableScore 6 with primitive class CLASS_B and manual review REQUIRED. Its independently reconciled impact was IMPORTANT. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is IMPORTANT.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)	MAYBE	REMOTE INIT UAF NETWORK HARDWARE QDISC PACKET INCREASED_TO_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATE7_BASED_ON_FALSEPOSCHECKOFKP TEMP_KPANIC_MERGE_IMPORTANT_WINS KPANIC_UNSUPPORTED_REMOVED	-	-	checked

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

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

1. ActionableScore

* Raw base score: 4.
* Conservative score: 5. REAL UAF FLOOR 5 applies because direct free can end the object lifetime while the exact referenced object survives and later receives a lifetime/refcount mutation.
* Raw paranoid score: 5.
* Paranoid score: 5.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

* +2 Real UAF: `metadata_dst_free()` directly frees `repr->dst` while queued skbs retain references obtained through `dst_hold()`.
* +1 Concrete repeated lifetime/refcount operation: the freed exact `dst_entry` remains attached to skbs and a later skb dst release can perform `dst_release()`/refcount mutation on storage whose lifetime has ended.
* +1 Reliable kernel crash/strong DoS: later processing or release of the stale dst plausibly faults or corrupts allocator state.
* Paranoid +1: the later release is itself a write-like refcount mutation through possibly freed storage, not merely a stale read.
* No timing penalty: overlap with teardown and queued traffic is required, but the evidence does not establish a narrow, uncontrollable, one-shot race.
* No remote, local-unprivileged, structured-reuse, controlled-reclaim, arbitrary-write, confidentiality, integrity, or extra availability points are awarded.

Repeated-release findings: the first direct free unquestionably ends lifetime; the exact held dst references survive; later reference release mutates lifetime state. The dedicated +1 and FLOOR 5 apply. No separate Weak LPE or structured-leverage point is added for that same mutation.

3. Reachability analysis

The vulnerable configuration requires ICE switchdev representors and queued lower-device traffic during representor teardown. A VF or representor-side actor can influence traffic and queue occupancy, but the evidence does not show that this actor can independently initiate teardown. The trigger may therefore be compound with a host lifecycle/control-plane operation. Effective host-admin need, namespace capability scope, and a complete below-host-admin trigger remain unknown. ICE hardware and prior switchdev setup are prerequisites, but no physical-attacker or rare-hardware penalty is justified. Race repeatability is unresolved.

4. Primitive and severity reading

This is an active structured-object UAF, not fixed stale storage: a refcounted metadata dst is freed despite live skb ownership and is later consumed or released by the networking stack. It is stronger than an ordinary cleanup stale dereference because the later operation can mutate the freed dst refcount. This supports CLASS_B, not CLASS_A: controlled reclaim, attacker-shaped replacement contents, directed write, disclosure, or LPE are not shown.

The representor/VF-to-host networking boundary is credible, but the complete attacker-controlled trigger is unresolved. The concrete post-lifetime mutation nevertheless leaves material exploit leverage unknown, requiring Important-candidate review and prohibiting automatic downgrade.

5. One-sentence report phrase

ICE representor teardown can directly free a metadata dst still referenced by queued skbs, causing a later host networking operation to use or refcount-mutate the freed object.

6. Manual review advice

MANUAL CHECK REQUIRED

Review the queued-skb consumers, allocator reuse window, teardown authority, and whether a VF or delegated networking actor can induce the complete sequence.

7. Call-site confidence

Call-site confidence: medium

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

Patch: ice: fix metadata_dst refcount handling on representor teardown [ Upstream
Commit: 1f263235651775f93c15d90c9f25c3f4a4ef6512
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1f263235651775f93c15d90c9f25c3f4a4ef6512

Changed files:
  drivers/net/ethernet/intel/ice/ice_eswitch.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=1f263235651775f93c15d90c9f25c3f4a4ef6512

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

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

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:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7.1

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: 5

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: IMPORTANT
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): IMPORTANT

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