[CVE-2026-98156][MODERATE 7.0] drm/virtio: use the DMA API for resource backing on Xen [ Upstream

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

CVE: CVE-2026-98156
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: drm/virtio: use the DMA API for resource backing on Xen [ Upstream
Commit: 93c557e947ef0040004b1ac6a1c1265d79a957e1
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=93c557e947ef0040004b1ac6a1c1265d79a957e1
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98156
Analysis date: Fri, 25 Sep 2026 12:13:12 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-98156	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98156 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:C/C:H/I:N/A:N';*CWE-200;CWE-668;CWE-284;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N';BEST CVSS score: '5.6';DESCR 'A Xen PV guest using virtio GPU can provide guest physical addresses as resource backing when DMA mapping is required. The host may interpret these addresses as machine addresses belonging to another Xen domain and can scan out unrelated memory. This can violate Xen domain isolation and may expose data from other domains through the graphics resource path. For the CVSS the PR:L is selected because an attacker needs local code execution in the affected Xen PV guest and access to the virtio GPU DRM interface. The issue is not directly network reachable. AC:H is selected because exploitation requires the specific Xen PV and virtio GPU configuration where guest physical addresses are not identity mapped. Impact is confirmed as cross domain information exposure. Integrity impact is not established by the patch context. ';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)	YES	OOB DANGER VIRT DMAorINTERRUPT HARDWARE LINUS KPANIC MEMORY  KPANIC INCREASED_TO_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATE7_BASED_ON_FALSEPOSCHECKOFKP	YES	NO	checked

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

ActionableScore=5
ActionableScoreLower=4
PrimitiveClass=CLASS_A
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=YES
ManualReview=REQUIRED
AutoDowngradeAllowed=NO

1. ActionableScore

* Raw conservative score: 4
* Conservative score: 4
* Raw paranoid score: 5
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

The paranoid score is emitted because the patch establishes a cross-domain address-translation error and actual scanout of unrelated domain memory, while the exact ability of a malicious guest graphics client to reliably capture selected victim data is not fully shown.

2. Signal breakdown

Conservative signals:

* +2 Strong attacker-influenced semantic reinterpretation. Guest physical addresses for virtio GPU resource backing are consumed by the host as machine addresses. This is a material translation-domain mismatch involving active memory backing descriptors.
* +1 Cross-domain isolation violation. The patch explicitly states that addresses can resolve to pages belonging to another Xen domain.
* +1 Confidentiality consequence. The host scans out unrelated memory through the GPU resource path. This is a concrete disclosure-oriented consequence, not merely an internal invalid read.

Paranoid-only signal:

* +1 Practical sensitive-memory exposure concern. The erroneous address is used for framebuffer backing and scanout, providing an output path for unrelated memory. The patch does not prove reliable selection or extraction of arbitrary victim pages, so this is not scored as arbitrary host read or integrity compromise.

Important non-awarded signals:

* No UAF, double free, refcount misuse, or stale-object lifetime primitive is established.
* No arbitrary or directed host memory write is established.
* No integrity impact is awarded. The supplied context describes host scanout and DMA-address correctness, but does not demonstrate writes into memory owned by another Xen domain.
* No local-unprivileged-trigger bonus is awarded. The supplied patch does not establish that the complete affected DRM resource creation and scanout path is available to an ordinary guest user without DRM authorization, render-node access, DRM master privileges, compositor cooperation, or another delegated graphics capability.
* No remote-reachability bonus is awarded. This is not directly reachable from network traffic.
* No legacy or niche-subsystem penalty is applied. Xen PV is a specific deployment condition, but the supplied evidence does not establish that it is unreachable to the relevant attacker once the affected PV guest configuration exists.

3. Reachability analysis

The affected execution environment is a Xen PV domain using virtio GPU, where guest physical addresses are not identity mapped to host machine addresses. The reported reproduction additionally uses virtio-vga with no negotiated VIRTIO_F_ACCESS_PLATFORM feature.

The likely attacker model is a process inside the affected Xen PV guest that can create or submit virtio GPU resources. However, the supplied patch does not show the exact DRM ioctl permissions, whether a render node is accessible, whether a DRM master or compositor is required for the relevant scanout operation, or whether an ordinary logged-in user can complete the full sequence.

Therefore HostAdminRequired is UNKNOWN rather than YES or NO. A host administrator is not positively shown to be required, but below-host-admin reachability for the complete graphics operation is also not proven. NamespaceScopedPrivilege is UNKNOWN because this is a Xen and DRM resource-backing path, not a demonstrated namespace-scoped capability path.

The issue is not directly network-triggerable. A remote attacker could only reach it indirectly after obtaining code execution or graphics-resource control inside an affected Xen PV guest.

4. Primitive and severity interpretation

The exact primitive is an address-domain confusion in virtio GPU resource backing. The Linux guest kernel supplies guest physical addresses through sg_phys when it should provide DMA-mapped addresses. In a Xen PV guest, those guest physical addresses can be interpreted by the host as machine addresses for unrelated Xen-domain pages.

This is not a UAF or cleanup-only defect. It is an active resource-backing and DMA ownership violation involving memory descriptors used by the host graphics backend. The patch directly confirms that the host scans out unrelated memory, which establishes a meaningful cross-domain confidentiality and isolation concern.

The issue is classified as CLASS_A because it establishes a concrete semantic address-translation mismatch across a virtualization isolation boundary. It does not establish arbitrary read, arbitrary write, controlled corruption, guest-to-host privilege escalation, or integrity compromise.

ImportantCandidate is YES because the patch establishes a real cross-domain memory exposure primitive whose practical extractability and affected victim-domain scope need manual review. AutoDowngradeAllowed is NO because automatically treating this as an ordinary graphics correctness issue could discard a virtualization isolation failure involving memory owned by another domain.

Likely operational severity is actionable Moderate at minimum. It may be Important in environments where untrusted guest users can access the relevant virtio GPU resource path and can observe the resulting framebuffer output.

5. One-sentence report phrase

A Xen PV virtio GPU address-translation error can cause guest physical framebuffer backing addresses to be interpreted as host machine addresses, potentially exposing memory belonging to another Xen domain through GPU scanout.

6. Manual review recommendation

MANUAL CHECK REQUIRED

The patch establishes cross-domain memory exposure through an active virtio GPU resource-backing path, but the complete guest-user DRM authorization and data-observation path requires environment-specific verification.

7. Call-site confidence

Call-site confidence: medium

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

Patch: drm/virtio: use the DMA API for resource backing on Xen [ Upstream
Commit: 93c557e947ef0040004b1ac6a1c1265d79a957e1
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=93c557e947ef0040004b1ac6a1c1265d79a957e1

Changed files:
  drivers/gpu/drm/virtio/virtgpu_drv.h
  drivers/virtio/virtio_ring.c
  drivers/gpu/drm/virtio/virtgpu_object.c
  drivers/gpu/drm/virtio/virtgpu_vq.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=93c557e947ef0040004b1ac6a1c1265d79a957e1

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

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

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

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