[CVE-2026-72453][LOW] regcache: Do not overwrite error code when finalizing cache after error [ Upstream

[CVE-2026-72453][LOW] regcache: Do not overwrite error code when finalizing cache after error [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72453
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: regcache: Do not overwrite error code when finalizing cache after error [ Upstream
Commit: 9f171aa115ec76be02c76c5765cd2c865279e34a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9f171aa115ec76be02c76c5765cd2c865279e34a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72453
Analysis date: Sat, 15 Aug 2026 07:01:06 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-72453	LOW	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:U/C:N/I:N/A:H';CWE-703;CWE-252;**CWE-476;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'regcache_init can incorrectly report success after cache population failed because the cleanup path overwrote the original populate() error with the return value from cache_ops exit(). This leaves callers believing the regcache was initialized even though internal cache state may be incomplete, and later regcache access can hit a NULL pointer dereference and crash the kernel. For the CVSS the PR:L is used in the paranoid vector because a reduced capability service, delegated device management path, or local hotplug style workflow may be able to trigger driver reprobe or initialization failure, although normal driver loading is administrative. The issue is not network reachable and depends on a specific driver and regcache backend where populate() fails and exit() returns success. Impact is denial of service via kernel crash, with no supported evidence for information disclosure or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)	YES	NULLPTR INIT SIMPLEFIX  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=2
ActionableScoreLower=1

1. ActionableScore
* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. The commit states that hidden regcache initialization failure can later cause NULL pointer dereferences when the regcache is accessed.
* Firmware-mediated external influence: +1 in paranoid scoring only. Some regmap users are device or firmware backed, so a failed populate callback could depend on device state, but the patch does not show a direct external attacker-controlled path.
* Requires admin/root/CAP_* in typical deployments: -2 for the conservative score. Triggering normally requires driver probe, reprobe, device initialization failure, or privileged device-management control.
* Rare AND difficult-to-reach subsystem/configuration: -1. The bug requires a regcache backend with populate() failure, an exit() callback returning success, and later access to the partially initialized cache.
* No generic memory corruption signal. The described failure mode is NULL pointer dereference, not UAF, double free, OOB write, type confusion, or controlled overwrite.
* No confidentiality or integrity signal. The patch does not support an information leak, arbitrary write, object replacement, or privilege escalation primitive.

3. Reachability analysis
The realistic trigger is local and privileged through driver/device initialization or reprobe paths. A reduced-privilege service, hotplug workflow, or delegated device-management setup could lower this to a local limited-privilege scenario, but that is product-specific and not shown by the patch. The path is not network reachable. Regmap is broadly used, but this exact failure requires a specific cache backend and error path, so practical exposure is narrower than the subsystem size suggests. Call-site confidence: medium, because the changed function is clear but affected caller behavior depends on individual regmap users.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like kernel reliability issue rather than an Important vulnerability. The theoretical impact is a kernel crash from a NULL pointer dereference after a hidden initialization failure. There is no supported evidence for exploitable memory corruption, privilege escalation, information disclosure, or cross-boundary access.

5. One-sentence report phrase
A regcache error-handling bug can hide a populate() failure when exit() returns success, leaving callers with an incompletely initialized cache and potentially causing a later NULL pointer dereference and local DoS.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The issue is a constrained error-path NULL dereference with privileged or highly configuration-dependent reachability and no demonstrated memory corruption or privilege escalation primitive.

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

Patch: regcache: Do not overwrite error code when finalizing cache after error [ Upstream
Commit: 9f171aa115ec76be02c76c5765cd2c865279e34a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9f171aa115ec76be02c76c5765cd2c865279e34a

Changed files:
  drivers/base/regmap/regcache.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=9f171aa115ec76be02c76c5765cd2c865279e34a

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

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

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:H/UI:N/S:U/C:N/I:N/A:H
  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: 1
  Paranoid ActionableScore: 2

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