[CVE-2026-68333][LOW] dpaa2-switch: put MAC endpoint device on disconnect [ Upstream

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

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

Summary:
A missing `put_device()` in the DPAA2 switch MAC disconnect path leaks endpoint device references across connect and disconnect cycles, potentially causing resource retention or cleanup failure on affected hardware.

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

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

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-68333	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	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-401;CWE-404;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'dpaa2 switch leaked a MAC endpoint device reference on disconnect because the endpoint returned by fsl_mc_get_endpoint was kept in the MAC object but was not released when that object was freed. Repeated connect and disconnect cycles can keep device references alive and may eventually cause resource retention, failed cleanup, or availability degradation on systems using this Freescale DPAA2 switch driver. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over the hardware, driver lifecycle, or switch port management. The issue is not directly network reachable and does not provide a memory corruption primitive. Impact is denial of service or cleanup failure only, with no supported confidentiality or integrity impact.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)  SKIP CVE-2026-68333 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 84cba72956fddf29ba666f885c39ed147024c125 YES  NO NO unknown 	MAYBE	REMOTE SIMPLEFIX LEAK NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=0

## 1. ActionableScore

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

## 2. Signal breakdown

Triggered signals:

* Real lifetime corruption / refcount lifetime bug: +1
  The patch fixes a missing `put_device()` for `mac->mc_dev`, so the bug is a leaked device reference.

* Availability impact realistic: +1
  Repeated connect and disconnect cycles may retain device references and cause cleanup failure or resource retention.

Negative signals:

* Requires admin/root/CAP_NET_ADMIN or equivalent device-management control in typical deployments: -2
  Reliable triggering normally requires control over DPAA2 switch port lifecycle, driver management, or privileged network/device configuration.

* Rare hardware/device-specific subsystem: -1
  The affected code is specific to Freescale/NXP DPAA2 switch hardware and is not a broad default Linux path.

No triggered signals:

* No remote/network-triggerable path.
* No UAF after free, double free, OOB write, arbitrary write, type confusion, or attacker-controlled reclaim.
* No plausible confidentiality or integrity impact.
* No practical LPE path.

## 3. Reachability analysis

The bug is reachable through DPAA2 switch MAC connect/disconnect lifecycle handling. In normal deployments, this is controlled by privileged device-management operations, hardware events, or administrative networking configuration. Ordinary local users should not be able to trigger reliable repeated cycles. Namespaces or containers do not normally reduce this to an unprivileged trigger unless a deployment explicitly delegates relevant device or network administration capabilities. The affected hardware is specialized, so exposure is narrow.

## 4. Severity interpretation

This behaves like an ordinary Low-like or weak Moderate resource-lifetime bug, not an Important-class vulnerability. The patch fixes a leaked reference, not a memory corruption primitive. The realistic impact is resource retention or cleanup failure after repeated privileged operations. Theoretical availability degradation exists, but there is no evidence of privilege escalation, sensitive data exposure, or kernel memory corruption beyond reference leakage.

## 5. One-sentence report phrase

A missing `put_device()` in the DPAA2 switch MAC disconnect path leaks endpoint device references across connect and disconnect cycles, potentially causing resource retention or cleanup failure on affected hardware.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be auto-closed for practical triage unless the affected product heavily relies on DPAA2 switch hotplug or exposes switch lifecycle control to reduced-privilege tenants.

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

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

Changed files:
  drivers/net/ethernet/freescale/dpaa2/dpaa2-switch.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=1f4ca61b7a93de3dfa5161bcd38ecb99bb091c38

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

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

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: unknown
  Paranoid ActionableScore: 0

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