[CVE-2026-99287][IMPORTANT] xen-netback: Zero out sring pointers on unmap

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

CVE: CVE-2026-99287
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: NO
Patch: xen-netback: Zero out sring pointers on unmap
Commit: 87fd475dc4e354088f6534285388e7b061f54b35
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=87fd475dc4e354088f6534285388e7b061f54b35
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99287
Analysis date: Tue, 10 Nov 2026 22:03:51 -0400
ActionableScore: 5
ActionableScore lower bound: unknown
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
A malicious Xen frontend can induce failed ring mapping cleanup that unmaps a ring twice through a retained stale pointer, potentially crashing the host networking backend.

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

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

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-99287	IMPORTANT	https://www.kernelcve.org/list/?q=CVE-2026-99287 CHECK WITH IMPACT FROM ORIG NN IMPORTANT | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=4 LEGACY=IMPORTANT RESULT=DIFF INDEPENDENT_LEGACY=IMPORTANT INDEPENDENT_RESULT=DIFF TEMP_KPANIC_MERGE=IMPORTANT_WINS_DISAGREEMENT PRE_MERGE_LEGACY=IMPORTANT (final Legacy and Aegis differ; FINAL: IMPORTANT, Aegis: MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H';CWE-415;*CWE-672;*CWE-664;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H';BEST CVSS score: '8.8';DESCR 'xen-netback can retain non NULL tx or rx sring pointers after a failed frontend ring mapping has already unmapped them. Later disconnect cleanup can pass the same stale pointers to xenbus_unmap_ring_vfree again, creating a double unmap or double free condition in the backend kernel and potentially crashing the host networking domain. For the CVSS the PR:L value is selected because exploitation requires control of an untrusted Xen guest frontend or its ring setup but does not require dom0 privileges. The base impact is host availability loss. The concrete memory lifetime primitive and the guest-to-host trust boundary support paranoid CIA HHH, although an information leak or arbitrary write is not proven. Automated impact decision path. The original SimpleNet classifier selected IMPORTANT. The primary LLM estimated paranoid CVSS 8.8 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 final reconciliation stage IMPORTANT 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 produced a review artifact and its decision was processed by the applicable downgrade and preservation rules. Exact triggered rule markers were TEMP_KPANIC_MERGE_IMPORTANT_WINS and KPANIC_UNSUPPORTED_REMOVED. The independent weaker Aegis shadow evaluated CVSS 3.4 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 IMPORTANT.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)	MAYBE	SIMPLEFIX LEAK NETWORK LINUS TEMP_KPANIC_MERGE_IMPORTANT_WINS 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 the first unmap can end the mapping lifetime, the exact stale pointer survives, and cleanup performs a second lifetime-ending unmap.
* Raw paranoid score: 5.
* Paranoid score: 5.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

* +2 — Real lifetime violation: `xenbus_unmap_ring_vfree()` unmaps/frees the ring mapping, but the non-NULL `sring` pointer remains reachable.
* +1 — Concrete repeated release: disconnect cleanup passes the exact same stale pointer to a second `xenbus_unmap_ring_vfree()`.
* +1 — Reliable host DoS: the supplied XSA evidence supports a backend/network-domain crash from the double unmap/free.
* Paranoid +1 — The second unmap is itself a write-like mapping/lifetime operation through an address whose original mapping lifetime has ended.
* No additional availability point: it would duplicate the host crash.
* No controlled reclaim, arbitrary write, disclosure, callback control, or LPE is shown. The legacy CIA:H interpretation is not sufficient evidence for those effects.
* This is not B5-R: no retry-accumulated index or heap OOB write is shown.
* B4-PENDING is inapplicable because no authorization decision changes from DENY to ALLOW.

Repeated-release checks: the first unmap can terminate the mapping; the same pointer survives; the second operation is a real unmap/free; dedicated +1 and FLOOR 5 apply.

3. Reachability analysis

The supplied XSA summary grounds the trigger in an untrusted Xen frontend controlling guest ring setup, without dom0 or host-administrator privilege. Xen/domain provisioning is prior host setup, but the vulnerable failure and disconnect path is guest-invocable afterward. This is not a Linux namespace-capability path. The sequence is ordered error cleanup rather than a timing race; exact trigger reliability is not established.

4. Primitive and severity reading

This is a CLASS_B double-unmap/use-after-lifetime primitive involving active Xen ring mappings, not merely a stale read. It differs from an ordinary cleanup fault because the second operation again mutates mapping lifetime state through the dangling pointer. Host crash is supported; useful post-free corruption, guest-to-host arbitrary memory access, confidentiality loss, and privilege escalation remain unproven. The concrete repeated lifetime mutation across the guest/backend boundary requires Important-versus-Moderate review and prohibits automatic downgrade.

5. One-sentence report phrase

A malicious Xen frontend can induce failed ring mapping cleanup that unmaps a ring twice through a retained stale pointer, potentially crashing the host networking backend.

6. Manual review advice

MANUAL CHECK REQUIRED

Review `xenbus_unmap_ring_vfree()` internals and allocator/mapping side effects to determine whether the second unmap provides leverage beyond host denial of service.

7. Call-site confidence

Call-site confidence: high

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

Patch: xen-netback: Zero out sring pointers on unmap
Commit: 87fd475dc4e354088f6534285388e7b061f54b35
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=87fd475dc4e354088f6534285388e7b061f54b35

Commit description:

If xenvif_map_frontend_data_rings() fails when a ring is already mapped,
it unmaps them via xenvif_unmap_frontend_data_rings() which keeps the
ring pointers unchanged. xenvif_connect_data()'s cleanup path calls
xenvif_disconnect_queue() which in turn calls
xenvif_unmap_frontend_data_rings() again, which will attempt to unmap the
pointers a second time.

Zero out the ring pointers after they are unmapped to avoid this issue.

This is XSA-532

Fixes: 2ac061c ("xen/netback: cleanup init and deinit code")
Signed-off-by: Tu Dinh <ngoc-tu.dinh@vates.tech>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/net/xen-netback/netback.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=87fd475dc4e354088f6534285388e7b061f54b35

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

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

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

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