[CVE-2026-68331][LOW] dpaa2-eth: put MAC endpoint device on disconnect [ Upstream

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

CVE: CVE-2026-68331
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: dpaa2-eth: put MAC endpoint device on disconnect [ Upstream
Commit: 915012e923316b8b5d5bf8fc771617b47bd7572d
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=915012e923316b8b5d5bf8fc771617b47bd7572d
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68331
Analysis date: Mon, 10 Aug 2026 08:51:17 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A missing put_device() in the DPAA2 Ethernet MAC disconnect path leaks a MAC endpoint device reference on each successful connect and later disconnect cycle, requiring privileged local device lifecycle control and causing only potential resource exhaustion over time.

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

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

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-68331	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-772;CWE-404;*CWE-401;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'The DPAA2 Ethernet MAC disconnect path can leak a reference to the MAC endpoint device because the device returned by fsl_mc_get_endpoint is stored in mac mc_dev but is not released when the MAC object is disconnected and freed. Repeated connect and disconnect cycles can accumulate leaked device references and may prevent full cleanup of the endpoint device or cause resource exhaustion over time. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over driver bind unbind or device lifecycle operations on the DPAA2 platform. The issue is not network reachable and is not triggered by packet traffic. Impact is denial of service through resource leakage only, with no evidence of memory corruption, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	REMOTE SIMPLEFIX LEAK NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	guess

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

* Real lifetime or reference-management issue: +1
  The bug is a missing put_device() for a device reference obtained via fsl_mc_get_endpoint() / device_find_child(). This is a reference leak, not UAF or overwrite.

* Availability impact plausible only over repeated lifecycle cycles: +1 in paranoid view only
  Repeated connect / disconnect or driver lifecycle operations could accumulate leaked references and prevent cleanup or contribute to resource exhaustion.

Subtractors:

* Requires admin/root/device-management privileges in typical deployments: -2
  Reliable triggering normally requires control over DPAA2 device lifecycle, driver bind/unbind, disconnect, or platform device management.

* Rare hardware/platform-specific exposure: -1
  DPAA2 Ethernet is specific to NXP/Freescale DPAA2 platforms and is not a broad/default Linux exposure.

Not triggered:

* No remote/network-triggerable path. Packet traffic does not appear to trigger the leak directly.
* No generic memory corruption. The patch fixes a missing reference drop, not UAF, double free, OOB write, or type confusion.
* No privilege escalation plausibility.
* No confidentiality or integrity impact.

## 3. Reachability analysis

The issue is reachable through DPAA2 Ethernet MAC connect/disconnect lifecycle handling. In typical deployments, an attacker would need administrative control over the device or driver lifecycle, such as driver unbind, device removal, reset, or platform-specific management. Network packets alone should not trigger this path. Namespaces or containers generally do not lower the requirement unless a container or service is explicitly delegated host device-management capabilities, which would be unusual and still privileged.

Call-site confidence: medium. The patch shows the disconnect path and the missing put_device(), but not all external lifecycle callers.

## 4. Severity interpretation

This behaves like a Low-like or ordinary Moderate resource leak. The realistic impact is gradual availability degradation or cleanup failure after repeated privileged lifecycle operations. There is no evidence of attacker-controlled memory corruption, UAF reclaim, stale callback, arbitrary write, information disclosure, or privilege escalation. The paranoid score only accounts for sustained repeated abuse causing stronger resource exhaustion, but it remains below Actionable Moderate.

## 5. One-sentence report phrase

A missing put_device() in the DPAA2 Ethernet MAC disconnect path leaks a MAC endpoint device reference on each successful connect and later disconnect cycle, requiring privileged local device lifecycle control and causing only potential resource exhaustion over time.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This is a platform-specific privileged resource reference leak without memory corruption, network reachability, confidentiality impact, integrity impact, or plausible privilege escalation.

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

Patch: dpaa2-eth: put MAC endpoint device on disconnect [ Upstream
Commit: 915012e923316b8b5d5bf8fc771617b47bd7572d
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=915012e923316b8b5d5bf8fc771617b47bd7572d

Changed files:
  drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.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=915012e923316b8b5d5bf8fc771617b47bd7572d

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

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

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

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