[CVE-2026-68345][LOW] arm_mpam: guard MBWU state before adding it to garbage [ Upstream

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

CVE: CVE-2026-68345
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: arm_mpam: guard MBWU state before adding it to garbage [ Upstream
Commit: ca1f96334267ab8d47b2c9d535cdc9920fdde269
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ca1f96334267ab8d47b2c9d535cdc9920fdde269
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68345
Analysis date: Mon, 10 Aug 2026 14:49:51 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
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-68345 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68345

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-68345	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-703;CWE-754;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'arm_mpam component configuration teardown can crash because __destroy_component_cfg may pass a NULL mbwu_state pointer to add_to_garbage when a RIS does not have MBWU monitor state allocated. The failure is a NULL pointer dereference during local MPAM or resctrl teardown activity on affected ARM systems. For the CVSS the PR:L is used only for the paranoid score because some deployments may delegate resource control operations to a reduced privilege service or container style administrator, but the normal administrative model is PR:H. The issue is not network reachable and there is no evidence of a UAF, OOB write, information leak, or privilege escalation primitive. Impact is denial of service via kernel crash under hardware and configuration dependent conditions.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	DANGER 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=1

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

2. Signal breakdown
* Reliable kernel crash / strong DoS: +1. Passing NULL mbwu_state to add_to_garbage dereferences NULL and can crash the kernel.
* Requires admin/root/CAP_* in typical deployments: -2. MPAM/resctrl component configuration teardown is normally controlled by privileged kernel or administrator-managed paths.
* Rare AND difficult-to-reach subsystem/configuration: -1. The issue depends on ARM MPAM support, MBWU monitor configuration, and a component teardown path.
* Paranoid local reduced-privilege interpretation: +1. If resource-control operations are delegated to a service, container-style administrator, or reduced-privilege management component, the trigger may be closer to PR:L than PR:H.
* No memory corruption primitive counted. The patch shows a NULL pointer dereference, not UAF, double free, OOB write, stale callback, refcount abuse, or controlled object reuse.
* No confidentiality or integrity impact counted. There is no disclosure path, write primitive, ownership bypass, or privilege escalation evidence.

3. Reachability analysis
The bug is triggered during MPAM component configuration destruction when a RIS lacks allocated MBWU state. In normal deployments this is a privileged local management path, not a network path. Namespace or container effects are only relevant if resctrl/MPAM management is delegated to less privileged actors, which supports a paranoid PR:L interpretation but not a strong unprivileged trigger. The affected path is hardware and configuration dependent and requires ARM MPAM plus relevant monitor/config teardown conditions.

4. Severity interpretation
This behaves like ordinary Moderate or Low-like kernel DoS, not an Important candidate. The theoretical impact is a kernel crash from NULL dereference. Realistic exploitation evidence does not show memory corruption beyond invalid NULL dereference, does not show attacker-controlled reuse, and does not support LPE. Conservative handling can be auto-closed or deprioritized unless the affected product exposes MPAM/resctrl teardown to untrusted delegated users.

5. One-sentence report phrase
A NULL pointer dereference in arm_mpam component teardown can occur when a RIS without MBWU state is added to the garbage list, causing a local hardware-dependent kernel crash with no evidence of privilege escalation or data exposure.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The patch shows a narrow NULL dereference in a rare privileged MPAM teardown path, with no concrete UAF, OOB write, information leak, or privilege escalation primitive.

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

Patch: arm_mpam: guard MBWU state before adding it to garbage [ Upstream
Commit: ca1f96334267ab8d47b2c9d535cdc9920fdde269
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ca1f96334267ab8d47b2c9d535cdc9920fdde269

Changed files:
  drivers/resctrl/mpam_devices.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=ca1f96334267ab8d47b2c9d535cdc9920fdde269

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

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

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