[CVE-2026-100081][IMPORTANT] xen-netback: defer xenvif_mcast_addr_list_free()

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

CVE: CVE-2026-100081
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: NO
Patch: xen-netback: defer xenvif_mcast_addr_list_free()
Commit: 96e05a8ce243e2207704e2e7a6e7d1172730f515
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=96e05a8ce243e2207704e2e7a6e7d1172730f515
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-100081
Analysis date: Fri, 06 Nov 2026 22:07:40 -0400
ActionableScore: 5
ActionableScore lower bound: unknown
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
A Xen guest can race backend disconnect against multicast-list processing, leaving host xen-netback to traverse or modify prematurely freed active list state.

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

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

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-100081	IMPORTANT	https://www.kernelcve.org/list/?q=CVE-2026-100081 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT IMPORTANT AEGIS_AS=6 LEGACY=IMPORTANT RESULT=SAME INDEPENDENT_LEGACY=MODERATE_KPANIC INDEPENDENT_RESULT=DIFF TEMP_KPANIC_MERGE=IMPORTANT_HARD_VETO 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 'A race in Xen netback teardown allowed xenvif_mcast_addr_list_free to run while xenvif_start_xmit could still look up multicast entries or xenvif_tx_action could modify them. This creates a guest influenced use after free and possible list corruption in the host kernel. A malicious Xen guest may attempt to trigger the race by maintaining network activity and multicast state while causing backend disconnect. For the CVSS the PR:L value is selected because the attacker needs control of a guest frontend but does not require host administrative privileges. AC:H reflects the need to hit a teardown and packet processing race window. Impact is at least host denial of service through a kernel crash and may include confidentiality or integrity impact if the use after free becomes exploitable across the guest to host boundary. Automated impact decision path. The original SimpleNet classifier selected LOW. 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 LOW to MODERATE_KPANIC because the ActionableScore threshold rule was applied. final reconciliation stage MODERATE_KPANIC to IMPORTANT because a specific evidence based protection or manual review veto was applied and 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_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 and TEMP_KPANIC_MERGE_IMPORTANT_VETO and KPANIC_UNSUPPORTED_REMOVED. The independent weaker Aegis shadow evaluated CVSS 4.9 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	LOCK INIT SIMPLEFIX RACE LEAK ERRORPATH NETWORK LINUS INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 TEMP_KPANIC_MERGE_IMPORTANT_VETO KPANIC_UNSUPPORTED_REMOVED	-	-	checked

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

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

1. ActionableScore

* Raw base score: 4.
* Conservative score: 5. REAL UAF FLOOR 5 applies because guest-influenced active multicast-list state is traversed or modified after premature teardown.
* Raw paranoid score: 4.
* Paranoid score: 5. No additional speculative exploit point.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

* +2 — Real active-object UAF: `xenvif_mcast_addr_list_free()` could free multicast entries before concurrent `xenvif_start_xmit()` lookup or `xenvif_tx_action()` add/remove processing finished.
* +1 — Structured stale-object leverage: later host networking operations traverse or mutate the freed multicast-list state; this is deeper than an immediate cleanup dereference.
* +1 — Attacker-influenced lifetime/state sequence: a guest frontend can maintain packet and multicast activity around backend disconnect.
* +1 — Plausible host kernel crash/DoS from stale list access or list corruption.
* -1 — The supplied evidence specifically identifies a high-complexity teardown/packet-processing race window.
* No separate availability point: it would duplicate the same crash.
* No controlled reclaim, attacker-selected target, arbitrary write, disclosure, or LPE is shown.
* No concrete repeated release/refcount operation exists; FLOOR 5 instead follows active structured processing and guest-influenced lifetime activity.
* The guest-to-host boundary warrants review, but no directed host-memory corruption or escape is proven.

3. Reachability analysis

The assessed attacker controls a Xen guest frontend, not host UID 0 or a host administrator. Guest networking and multicast state reach host `xen-netback`; the supplied summary also grounds attempting backend disconnect while traffic remains active. No Linux namespace capability is involved and no special physical hardware is required beyond a Xen deployment. Triggering requires a teardown race, so reliability is uncertain and AC:H is supported.

4. Primitive and severity reading

This is a host-kernel UAF of an active structured multicast list, not fixed stale storage. The premature free occurs in disconnect processing, but stale use remains possible in ordinary TX/RX lookup and list-modification paths until `synchronize_net()` completes. The fix moves freeing after that synchronization point.

The shown effects are stale traversal/mutation, possible list corruption, and host crash. Controlled replacement, arbitrary read/write, confidentiality impact, and guest escape remain unproven. Nevertheless, attacker-influenced active state is consumed by the more-privileged host networking backend across a specific guest/host boundary. Under the active-state trust-boundary rule this remains a CLASS_B Important candidate requiring manual review and cannot be automatically downgraded.

No authorization decision is changed, so B4-PENDING does not apply.

5. One-sentence report phrase

A Xen guest can race backend disconnect against multicast-list processing, leaving host xen-netback to traverse or modify prematurely freed active list state.

6. Manual review advice

MANUAL CHECK REQUIRED

Review stale-list mutation, reclaim opportunities, and whether the guest can reliably induce disconnect without VMM cooperation.

7. Call-site confidence

Call-site confidence: high

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

Patch: xen-netback: defer xenvif_mcast_addr_list_free()
Commit: 96e05a8ce243e2207704e2e7a6e7d1172730f515
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=96e05a8ce243e2207704e2e7a6e7d1172730f515

Commit description:

In order for the function to legitimately avoid locking/RCU, it needs to
run after all TX/RX processing has finished/stopped: Lookups happen from
xenvif_start_xmit(), while adds/removes happen from xenvif_tx_action()
(called out of xenvif_poll()).

Move the call out of xenvif_disconnect_data() (the call to the function
from connect()'s error path doesn't require any cleaning up there), and
put it past the synchronization point in backend_disconnect().

This is XSA-527 / CVE-2026-100081 .

Fixes: b17075d ("xen-netback: fix race condition on XenBus disconnect")
Reported-by: kerhunt <kerhunt@proton.me>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/net/xen-netback/interface.c
  drivers/net/xen-netback/xenbus.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=96e05a8ce243e2207704e2e7a6e7d1172730f515

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

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

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