[CVE-2026-98404][LOW] drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() [ Upstream

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

CVE: CVE-2026-98404
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() [ Upstream
Commit: 975f3cf302bb7d7336df4c630a7c07e12780ad10
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=975f3cf302bb7d7336df4c630a7c07e12780ad10
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98404
Analysis date: Thu, 15 Oct 2026 05:20:14 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
A NULL return from virtio_gpu_user_framebuffer_create() can bypass error-pointer handling in drm_mode_addfb2() and cause a local kernel NULL-pointer dereference and denial of service.

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

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

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: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-98404	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98404 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=0 LEGACY=LOW RESULT=DIFF TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (independent Legacy and Aegis differ; FINAL: LOW, 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:U/C:N/I:N/A:H';**CWE-476;CWE-703;CWE-253;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'virtio_gpu_user_framebuffer_create() can return NULL after framebuffer initialization fails even though the DRM caller expects either a valid framebuffer pointer or ERR_PTR(). drm_mode_addfb2 can therefore treat the result as successful and later dereference the NULL framebuffer pointer. A local process may trigger the vulnerable path through DRM framebuffer creation if it can access the relevant /dev/dri/card device and satisfy the required DRM authorization. For the CVSS the PR:L value is used because local code execution and access to the DRM device interface are required, but full administrative control is not necessarily required. The issue is not network reachable. Impact is a local denial of service through a kernel Oops or crash, potentially with high availability impact when panic_on_oops is enabled. The supplied code does not show a UAF, OOB access, information disclosure, or write primitive that would support confidentiality, integrity, or privilege escalation impact. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 5.5 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE to LOW because the ActionableScore threshold rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH and DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3. The independent weaker Aegis shadow evaluated CVSS 4.3 and ActionableScore 0 with primitive class CLASS_C and manual review NO. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	NULLPTR VIRT SIMPLEFIX HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	guess

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

ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

## 1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* No floor or cap was applied.
* Final recommended bucket: **Ordinary Moderate**::

## 2. Signal breakdown

Positive signals:

* +1 Reliable kernel crash / strong DoS. Returning `NULL` instead of `ERR_PTR(ret)` allows `drm_mode_addfb2()` to accept the result as non-error and subsequently dereference a NULL framebuffer pointer, causing a kernel Oops and potentially a panic.
* +0 Weak corruption concern. The established operation is an invalid NULL dereference without a useful corruption primitive.

Negative signals:

* No negative points. Host-admin privilege, rare hardware, and difficult timing are not established and therefore are not used as penalties.

Material signals not awarded:

* No UAF, stale lifetime reference, repeated release, or refcount mutation is established.
* No heap OOB read or write is established. The B5-R retry-accumulated OOB profile does not apply.
* No shared-backing write or ownership violation is established. B3-PENDING does not apply.
* No controlled reclaim, arbitrary write, object replacement, callback influence, or structured stale-object consumption is demonstrated.
* No authorization decision changes from DENY to ALLOW. B4-PENDING does not apply.
* No confidentiality, integrity, privilege-escalation, or protected-resource impact is supported.
* No remote reachability is established.
* No extra Availability point is awarded because it would duplicate the same NULL-dereference crash.

## 3. Reachability analysis

The likely entry point is a local DRM framebuffer-creation operation against a virtio-gpu device, normally through the relevant `/dev/dri/card*` node. A process must reach `drm_mode_addfb2()` and cause `virtio_gpu_framebuffer_init()` to return an error.

The supplied evidence does not establish whether an ordinary logged-in user can complete this operation, whether DRM master or authenticated-client status is required, or whether only a compositor, display service, or administrator can reach the complete failing path. Therefore `HostAdminRequired` remains `UNKNOWN`. Numeric host UID 0 is also not established as necessary.

No namespace-scoped capability chain is shown. Virtio-gpu availability requires a virtual GPU configured for the affected guest, but this is a deployment prerequisite rather than evidence of rare physical hardware. There is no race or special timing requirement.

## 4. Primitive and severity interpretation

The exact defect is a return-value contract violation. The driver returns `NULL` after framebuffer initialization fails, while the caller expects either a valid framebuffer pointer or an encoded error pointer. Since `NULL` is not recognized by `IS_ERR()`, later code can dereference it.

This is `CLASS_C`: invalid-state consumption followed by a NULL pointer dereference. It is not an active-object UAF, fixed stale storage, repeated lifetime mutation, OOB access, or authorization bypass.

The demonstrated consequence is a local kernel Oops or crash. A system-wide panic is possible under configurations such as `panic_on_oops`, but that does not create an independent corruption primitive. There is no supported path to confidentiality loss, integrity modification, or privilege escalation.

`ImportantCandidate=NO` because no Important-preserving corruption, ownership, lifetime, or security-boundary primitive exists. `AutoDowngradeAllowed=YES` because the established behavior is constrained to crash/DoS and leaves no meaningful unresolved exploitation leverage.

## 5. One-sentence report phrase

A NULL return from virtio_gpu_user_framebuffer_create() can bypass error-pointer handling in drm_mode_addfb2() and cause a local kernel NULL-pointer dereference and denial of service.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch establishes a straightforward NULL-pointer dereference without UAF, OOB access, authorization bypass, write primitive, or unresolved exploitation leverage.

## 7. Call-site confidence

Call-site confidence: medium

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

Patch: drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() [ Upstream
Commit: 975f3cf302bb7d7336df4c630a7c07e12780ad10
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=975f3cf302bb7d7336df4c630a7c07e12780ad10

Changed files:
  drivers/gpu/drm/virtio/virtgpu_display.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=975f3cf302bb7d7336df4c630a7c07e12780ad10

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

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

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

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

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

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