[CVE-2026-98593][LOW] s390/debug: Fix NULL pointer dereference in debug_info_copy() [ Upstream

[CVE-2026-98593][LOW] s390/debug: Fix NULL pointer dereference in debug_info_copy() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98593
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: s390/debug: Fix NULL pointer dereference in debug_info_copy() [ Upstream
Commit: 13decd3b3b3a4d8a2e603fb8c9ffde0c6be3c225
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13decd3b3b3a4d8a2e603fb8c9ffde0c6be3c225
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98593
Analysis date: Sat, 24 Oct 2026 07:06:57 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
A failed s390 debug registration can leave inconsistent bounds that cause a later debug-area copy to dereference NULL and potentially crash the kernel.

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

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

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-98593	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98593 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT LOW AEGIS_AS=1 LEGACY=LOW RESULT=SAME (final reconciliation agrees; DECISION: both LOW)	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-703;BEST CVSS score: '4.7';DESCR 'A failed debug_register_static operation can leave nr_areas and related bounds intact while the areas pointer is NULL. A later debug_info_copy call through a view file open or debug_dump can enter the area copy loop and dereference the NULL pointer, causing a kernel oops or panic. For the CVSS the PR:L value reflects that a local user or process must reach an affected s390 debug view after the required registration failure. AC:H reflects the prerequisite failure state and the need to access the affected debug area. The demonstrated primitive is a NULL pointer invalid read with availability impact only. There is no supported UAF, OOB access, information leak, or write primitive. Automated impact decision path. The original SimpleNet classifier selected MODERATE. 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 to LOW because the CVSS score, vector or bug class 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_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS_AND_CIANNH. The independent weaker Aegis shadow evaluated CVSS 2.5 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was LOW. The shadow agreed with the final production impact and aggregation did not change that impact. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	DANGER NULLPTR INIT SIMPLEFIX HARDWARE LINUS  DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	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 base score: 1.
* Conservative score: 1; no floor or cap applied.
* Raw paranoid score: 1.
* Paranoid score: 1; no additional technically supported effect.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Reliable kernel crash/strong DoS: failed registration leaves `areas == NULL` while `nr_areas` remains nonzero, so the copy loop dereferences a NULL pointer.
* No timing penalty: registration failure and subsequent copying are state prerequisites, not a demonstrated narrow race.
* No UAF, OOB access, write, disclosure, authorization bypass, or protected-state corruption is shown.
* No extra availability point: an oops/panic is the single demonstrated consequence.
* NEW52/B5-R does not apply: there is no retry-accumulated heap OOB write or later consumption of corrupted structured state.
* NEW53/B3-PENDING does not apply: no shared-backing write exists.
* B4-PENDING does not apply: the new condition is a validity check, not restoration of an authorization guard.

3. Reachability analysis

The affected copy can be reached by opening a debug view file or through `debug_dump()`, but only after `debug_register_static()` has failed. The supplied evidence does not establish whether an ordinary user, host UID 0, or effective host administrator can complete that sequence. No namespace-scoped capability path, special timing race, or attacker-controlled failure mechanism is demonstrated. The code is s390-specific, but that alone does not justify a hardware or rarity penalty.

4. Primitive and severity reading

The exact primitive is an invalid read through a NULL `areas` pointer. It is neither stale storage nor an active-object lifetime violation, and no lifetime mutation occurs. The supported effect is an oops or possible panic; non-crash exploitation effects are unsupported. This is CLASS_C, not an Important candidate, and automatic downgrade is allowed because no unresolved corruption or trust-boundary primitive remains.

5. One-sentence report phrase

A failed s390 debug registration can leave inconsistent bounds that cause a later debug-area copy to dereference NULL and potentially crash the kernel.

6. Manual review advice

NO MANUAL CHECK NEEDED

The patch establishes a constrained NULL-dereference availability defect without a write, lifetime, authorization, or cross-boundary primitive.

7. Call-site confidence

Call-site confidence: high

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

Patch: s390/debug: Fix NULL pointer dereference in debug_info_copy() [ Upstream
Commit: 13decd3b3b3a4d8a2e603fb8c9ffde0c6be3c225
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13decd3b3b3a4d8a2e603fb8c9ffde0c6be3c225

Changed files:
  arch/s390/kernel/debug.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=13decd3b3b3a4d8a2e603fb8c9ffde0c6be3c225

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

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

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: Not available
  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: 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).