[CVE-2026-72485][LOW] coresight: platform: defer connection counter increment until alloc succeeds [ Upstream

[CVE-2026-72485][LOW] coresight: platform: defer connection counter increment until alloc succeeds [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72485
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: coresight: platform: defer connection counter increment until alloc succeeds [ Upstream
Commit: 8ca9adc805884d3bb5038082462577f86c2c4a10
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8ca9adc805884d3bb5038082462577f86c2c4a10
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72485
Analysis date: Sat, 15 Aug 2026 16:10:03 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
Coresight platform connection setup can leave connection counters inconsistent after allocation failure, causing cleanup to dereference a NULL or uninitialized pointer and panic the kernel during probe error handling.

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

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

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-72485	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-476;*CWE-457;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'Coresight platform connection setup can leave nr_outconns or nr_inconns incremented even when allocation of the corresponding connection array or entry fails. Cleanup then iterates according to the inflated counter and may dereference a NULL or uninitialized connection pointer, causing a kernel panic instead of a graceful probe failure. For the CVSS the PR:L is used in the paranoid score because a local low privileged user may be able to contribute to allocation failure through memory pressure while probe or reprobe is performed, although direct device probe control is usually administrative. The issue is not network reachable and requires a local hardware and driver initialization context. Impact is denial of service via kernel crash with no supported confidentiality or integrity primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)  SKIP CVE-2026-72485 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	DANGER SIMPLEFIX ERRORPATH HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Triggered signals:

* Reliable kernel crash / strong DoS: +1
  Cleanup may dereference a NULL or uninitialized connection pointer after an allocation failure, causing panic instead of graceful probe failure.

Subtracting signals:

* Requires admin/root/device-management control in typical deployments: -2
  Reliable triggering normally requires driver probe or reprobe control, which is generally administrative.
* Hard or unreliable trigger condition: -1
  The crash depends on allocation failure at a narrow point during Coresight platform setup.
* Rare hardware/configuration exposure: -1
  Coresight is hardware and platform dependent, not a broad default userspace-facing kernel path.

Not awarded:

* No generic strong memory corruption score. The described primitive is NULL or invalid pointer dereference during cleanup, not UAF reclaim, OOB write, double free, or controlled overwrite.
* No LPE score. There is no supported path to attacker-controlled reuse, callback control, refcount takeover, or arbitrary write.
* No confidentiality or integrity impact.

Call-site confidence: high. The commit message explicitly describes the cleanup caller and the dereference consequence.

## 3. Reachability analysis

The affected path is reached during Coresight platform data construction and cleanup after allocation failure. In normal deployments, a user would need administrative influence over device probing, module loading, reprobe, or platform device lifecycle. A low privileged local user might only indirectly increase memory pressure, which is too weak for conservative reachability but can justify the paranoid score of 1. Namespaces or containers do not materially improve reachability unless device management is delegated.

## 4. Severity interpretation

This behaves like a local hardware-specific DoS, not an Important-class vulnerability. Theoretical concern comes from dereferencing an uninitialized or NULL pointer, but the realistic evidence points to panic on an ENOMEM cleanup path. There is no demonstrated privilege escalation, information leak, write primitive, stale lifetime reuse, or security-boundary bypass.

## 5. One-sentence report phrase

Coresight platform connection setup can leave connection counters inconsistent after allocation failure, causing cleanup to dereference a NULL or uninitialized pointer and panic the kernel during probe error handling.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED.

The issue is a constrained probe error-path DoS with rare hardware exposure and no supported LPE or memory-corruption primitive beyond invalid pointer dereference.

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

Patch: coresight: platform: defer connection counter increment until alloc succeeds [ Upstream
Commit: 8ca9adc805884d3bb5038082462577f86c2c4a10
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8ca9adc805884d3bb5038082462577f86c2c4a10

Changed files:
  drivers/hwtracing/coresight/coresight-platform.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=8ca9adc805884d3bb5038082462577f86c2c4a10

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

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

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