[CVE-2026-72144][MODERATE REGULAR] platform/x86: dell-laptop: fix missing cleanups in init error path [ Upstream

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

CVE: CVE-2026-72144
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: platform/x86: dell-laptop: fix missing cleanups in init error path [ Upstream
Commit: e4908b3bed755f73870416b971e162a8d0ef0aef
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e4908b3bed755f73870416b971e162a8d0ef0aef
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72144
Analysis date: Sun, 16 Aug 2026 03:34:15 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like with manual review recommended
Manual review required: YES

Summary:
A failed `dell_laptop` initialization path could leave notifier, debugfs, and LED resources registered after the driver returns an error, creating inconsistent driver state and a constrained stale-object risk, but exploitation appears local, privileged, and hardware/error-path dependent.

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

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

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

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

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

CVE-2026-72144	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';CWE-459;*CWE-772;*CWE-416;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.2';DESCR 'dell_laptop init error handling can leave the notifier, debugfs directory, keyboard backlight LED, and optional touchpad LED registered after dell_init() returns an error. This creates inconsistent driver state after a failed initialization and may later expose stale registered objects or callbacks if the module load fails and resources are released. For the CVSS the PR:H is used for the paranoid score because reliable triggering normally requires administrative control over module loading, platform driver initialization, or fault injection on Dell specific hardware. The issue is not network reachable and is not triggered by packet traffic. Impact is primarily local denial of service or resource leakage, with limited confidentiality or integrity impact considered only as a conservative use after free candidate that should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like with manual review recommended (with actual score 2)  SKIP CVE-2026-72144 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 9c656b07997f518ab407dd990aaf55f358337bd6 YES  NO NO unknown 	MAYBE	INIT SIMPLEFIX ERRORPATH DEBUGFS  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like with manual review recommended**

## 2. Signal breakdown

Conservative signals:

* Availability impact plausible: +1
  Failed init can leave kernel-visible driver resources registered, causing resource leakage or inconsistent device state.

Paranoid additional signals:

* Weak/indirect corruption candidate: +1
  A notifier or LED/debugfs object left registered after failed module initialization may become a stale registered object or callback candidate.
* Real lifetime corruption: +1
  The patch fixes missing cleanup of registered resources on an init failure path, which is a lifetime-management issue.
* Privileged device-management lifetime path: +1
  The affected code is driver initialization and cleanup logic in a platform driver, but attacker control is weak.

Negative signals:

* Requires admin/root/CAP in typical deployments: -2
  Reliable triggering normally requires module loading, platform driver initialization control, or fault injection.
* No remote or network reachability: +0
  This is not packet-triggered and has no remote interface.
* No demonstrated strong primitive: +0
  The patch does not show controlled reclaim, arbitrary write, type confusion, or attacker-controlled callback dispatch.

## 3. Reachability analysis

The bug is locally reachable only in constrained conditions. A typical attacker would need administrative control over module loading or a way to force a later LED or backlight registration failure during `dell_init()`. The path is hardware and platform dependent because it applies to the Dell laptop platform driver. Containers and namespaces do not normally reduce the required privileges, because this is not an ordinary unprivileged syscall or network data path. Call-site confidence: high, because the patch directly shows the failing init unwind path and the missing cleanup calls.

## 4. Severity interpretation

This behaves more like an ordinary Moderate or Low-like issue than an Important-class vulnerability. The realistic impact is resource leakage or local DoS due to inconsistent driver state after failed initialization. The theoretical concern is a stale registered notifier or callback after failed module init, but the patch does not demonstrate reclaim control, writable UAF, object replacement, or privilege escalation. Therefore the paranoid score is only slightly elevated for manual-review sensitivity.

## 5. One-sentence report phrase

A failed `dell_laptop` initialization path could leave notifier, debugfs, and LED resources registered after the driver returns an error, creating inconsistent driver state and a constrained stale-object risk, but exploitation appears local, privileged, and hardware/error-path dependent.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: the score is low, but missing cleanup of registered notifiers or callbacks after failed module initialization can sometimes turn into a stale callback or UAF-style condition, so a focused manual check of module unload and callback lifetime is justified.

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

Patch: platform/x86: dell-laptop: fix missing cleanups in init error path [ Upstream
Commit: e4908b3bed755f73870416b971e162a8d0ef0aef
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e4908b3bed755f73870416b971e162a8d0ef0aef

Changed files:
  drivers/platform/x86/dell/dell-laptop.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=e4908b3bed755f73870416b971e162a8d0ef0aef

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

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

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

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