[CVE-2026-98523][MODERATE REGULAR] drm/client: fix restore of partially initialized client [ Upstream

[CVE-2026-98523][MODERATE REGULAR] drm/client: fix restore of partially initialized client [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98523
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: drm/client: fix restore of partially initialized client [ Upstream
Commit: 11edd5b6735d2e1069ddce672b1836713647f7fb
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=11edd5b6735d2e1069ddce672b1836713647f7fb
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98523
Analysis date: Mon, 19 Oct 2026 02:59:13 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
A partially initialized DRM fbdev client can remain registered after probe failure and later cause a NULL-pointer dereference during DRM file release, resulting in a kernel Oops or configuration-dependent host denial of service.

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

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

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 REGULAR
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-98523	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98523 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=0 LEGACY=MODERATE RESULT=DIFF V39_AEGIS_ONE_STEP_UP=LOW->MODERATE TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-665;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A partially initialized DRM fbdev client can remain registered after the initial framebuffer configuration fails and cleanup clears fb_helper info. A later close of a DRM file descriptor can invoke the restore path, submit incomplete modeset state, and dereference missing fbdev state at address 0x8. This can produce a kernel warning and an Oops, and it may cause a host wide denial of service when panic_on_oops is enabled or when the failing path leaves critical DRM state unusable. For the CVSS the PR:L value is selected because a local user or process must have permission to open and close the affected DRM device. AC:H is selected because triggering also depends on a prior fbdev initialization failure that is not shown to be reliably controlled by the user. The issue is not network reachable. The demonstrated primitive is a NULL pointer dereference rather than a UAF, OOB access, or controlled memory write, so confidentiality and integrity impact are not supported. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.7 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. final reconciliation stage LOW to MODERATE because the cross model evidence reconciliation 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 and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 5.3 and ActionableScore 0 with primitive class CLASS_C and manual review RECOMMENDED. 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 MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	DANGER NULLPTR INIT HARDWARE LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED	-	-	checked

======================================================================
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 or strong DoS. The supplied trace establishes a kernel NULL-pointer dereference at address 0x8 following a warning. This produces an Oops and can become host-wide denial of service with `panic_on_oops`.
* No separate availability point was awarded because the warning, Oops, and possible panic are manifestations of the same fault.

Negative signals:

* No negative points were applied. The prior initialization failure is a prerequisite, but the evidence does not establish a narrow timing race or rare hardware requirement.

Important non-awarded signals:

* No UAF, stale post-lifetime reference, double release, OOB access, refcount mutation, or controlled reclaim is established.
* No attacker-controlled write, payload, target, or active-state corruption is demonstrated.
* No confidentiality, integrity, privilege-escalation, or authorization-bypass signal is supported.
* Local-unprivileged reachability was not awarded because access to a DRM file descriptor alone does not establish control over the preceding fbdev initialization failure.
* V33 does not apply because attacker-influenced corruption of active structured state is not established.
* NEW52 B5-R does not apply because there is no heap OOB write or retry-accumulated index.
* NEW53 B3-PENDING does not apply because there is no write to shared or file-backed storage.
* NEW54 B4-PENDING does not apply because no mandatory authorization decision changes from DENY to ALLOW.

3. Reachability analysis

A process holding an affected DRM file descriptor can reach `drm_release()` by closing the descriptor. However, exploitation also requires a device-global partially initialized fbdev client left registered after `drm_fb_helper_initial_config()` fails.

The supplied evidence does not establish that an ordinary logged-in user, DRM render-node user, DRM master, compositor, delegated display service, or host administrator can deliberately cause that initialization failure. It also does not establish which actor controls the complete sequence. Therefore, `HostAdminRequired` remains `UNKNOWN`, and no local-unprivileged-trigger point is awarded.

No namespace capability is involved in the visible path, but complete namespace-scoped reachability is not established. There is no network trigger, timing race, special boot option, or positively established rare-hardware prerequisite.

4. Primitive and severity interpretation

The exact primitive is an invalid NULL-pointer read through incompletely initialized fbdev state. The client object remains registered, but the evidence does not show that it or `fb_helper->info` is used after free. The NULL assignment is expected cleanup state, making this an invalid-state restoration bug rather than a lifetime violation.

The vulnerable operation occurs in a release-triggered restore callback and submits incomplete modeset state before reaching the NULL dereference. The demonstrated consequence is a warning followed by an Oops. A host panic is configuration-dependent. No independently useful effect remains after excluding the crash.

This is `CLASS_C`, not Class B or Class A. `ImportantCandidate=NO` because no corruption, ownership, authorization, or security-boundary primitive is established. `AutoDowngradeAllowed=YES` because the evidence supports a constrained crash-only defect without unresolved exploitation leverage.

Operationally, this is Low-like to ordinary Moderate. Systems configured with `panic_on_oops` may experience complete host denial of service, but that does not create a separate integrity primitive.

5. One-sentence report phrase

A partially initialized DRM fbdev client can remain registered after probe failure and later cause a NULL-pointer dereference during DRM file release, resulting in a kernel Oops or configuration-dependent host denial of service.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch establishes a direct NULL-state guard for a crash-only restore path, with no UAF, OOB write, authorization bypass, shared-backing modification, or unresolved cross-boundary corruption primitive.

7. Call-site confidence

Call-site confidence: high

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

Patch: drm/client: fix restore of partially initialized client [ Upstream
Commit: 11edd5b6735d2e1069ddce672b1836713647f7fb
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=11edd5b6735d2e1069ddce672b1836713647f7fb

Changed files:
  drivers/gpu/drm/drm_atomic.c
  drivers/gpu/drm/drm_fbdev_client.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=11edd5b6735d2e1069ddce672b1836713647f7fb

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

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

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

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

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