[CVE-2026-53232][MODERATE 7.0] net: phy: clean the sfp upstream if phy probing fails Sashiko reported that we don't call sfp_bus_del_upstream() in the probe failure path, so let's add it, otherwise the sfp-bus is left with a dangling 'upstream' field, that may be used later on during SFP events. This issue existed before the generic phylib sfp support, back when drivers were calling phy_sfp_probe themselves. Reviewed-by: Nicolai Buchwitz <nb@tipi-net.de> Fixes: 298e54f ("net: phy: add core phylib sfp support") Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com> Link: https://patch.msgid.link/20260604092819.723505-2-maxime.chevallier@bootlin.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>

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

CVE: CVE-2026-53232
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net: phy: clean the sfp upstream if phy probing fails Sashiko reported that we don't call sfp_bus_del_upstream() in the probe failure path, so let's add it, otherwise the sfp-bus is left with a dangling 'upstream' field, that may be used later on during SFP events. This issue existed before the generic phylib sfp support, back when drivers were calling phy_sfp_probe themselves. Reviewed-by: Nicolai Buchwitz <nb@tipi-net.de> Fixes: 298e54f ("net: phy: add core phylib sfp support") Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com> Link: https://patch.msgid.link/20260604092819.723505-2-maxime.chevallier@bootlin.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Commit: 48774e87bbaa0056819d4b52301e4692e50e3252
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48774e87bbaa0056819d4b52301e4692e50e3252
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53232
Analysis date: Thu, 25 Jun 2026 09:21:30 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A PHY probe failure can leave a dangling SFP bus upstream pointer that may be used during later SFP events, making this a hardware dependent stale pointer or UAF candidate with realistic kernel crash impact and limited but review worthy privilege escalation concern.

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

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

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 7.0
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-53232	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-404;*CWE-672;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A dangling upstream pointer can remain in the SFP bus when PHY probing fails because the failure path does not remove the upstream object added by sfp_bus_add_upstream. Later SFP events may use that stale upstream pointer after the PHY device probe has failed or after related objects have been released, which makes this a use after free candidate and can cause a kernel crash. For the CVSS the PR:L is used for the paranoid score because reliable triggering may be possible for a local actor with delegated network device control or driver rebinding capability, while typical production triggering is more privileged and hardware dependent. The issue is not reachable through ordinary network packets and generally requires a local control path or physical SFP event on systems with phylib SFP support. Impact is at least local denial of service and worst case may include confidentiality or integrity impact if the stale pointer is reused in a controllable way.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)	YES	SIMPLEFIX NETWORK HARDWARE  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	NO	NO	checked

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

ActionableScore=5
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Real lifetime corruption: +1. The SFP bus can retain a dangling upstream pointer after PHY probe failure.
* Memory corruption, weak or indirect corruption candidate: +1. This is a stale pointer or UAF candidate, but the patch does not show attacker controlled reclaim, overwrite, callback control, or type confusion.
* Reliable kernel crash / strong DoS: +1. Later SFP events may dereference the dangling upstream pointer and crash the kernel.
* Requires admin/root/device management in typical deployments: -2. Reliable triggering normally requires PHY driver probe failure, device bind/unbind, hardware state control, or privileged network device management.
* Rare or hardware dependent condition: -1. The affected path requires phylib SFP support and a probe failure followed by later SFP events.

Paranoid added signals:

* Local delegated trigger concern: +1. In some environments, reduced privilege root, service accounts, or delegated network device management may be able to trigger driver reprobe or SFP related events.
* Privileged kernel/device-management memory corruption path: +1. The stale pointer is in a trusted PHY/SFP device-management path.
* Weak LPE concern: +1. The dangling pointer may be reused later, so limited confidentiality or integrity impact cannot be ruled out without source-level lifetime review, although no strong exploit primitive is demonstrated.

## 3. Reachability analysis

This is not reachable through ordinary network packets. The realistic trigger is local or hardware mediated: a PHY probe must fail after `sfp_bus_add_upstream()`, leaving the SFP bus with a stale upstream pointer, and a later SFP event must use it.

In typical deployments, triggering this requires administrative control over the network device, driver bind or unbind, module reload, device reset, or physical/SFP-module events. Namespaces usually do not make this unprivileged, but delegated device management, container root with device access, or a network management daemon may lower the practical privilege boundary.

The path is relevant mostly to systems using phylib SFP support, such as network appliances, embedded systems, switches, routers, or servers with SFP cages.

## 4. Severity interpretation

This behaves like an actionable Moderate lifetime bug, not a normal low-risk cleanup. The patch explicitly fixes a dangling upstream field that may be used later, which is a concrete stale pointer / UAF candidate.

Realistically, the most likely impact is local DoS via kernel crash. Theoretical memory corruption impact is plausible because the stale pointer may reference released PHY-related objects, but the patch does not demonstrate attacker-controlled reclaim, arbitrary write, callback hijack, or a reliable LPE primitive. Therefore it should not be treated as a strong Important by default, but it should not be auto-closed without review.

## 5. One-sentence report phrase

A PHY probe failure can leave a dangling SFP bus upstream pointer that may be used during later SFP events, making this a hardware dependent stale pointer or UAF candidate with realistic kernel crash impact and limited but review worthy privilege escalation concern.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the bug is a real lifetime cleanup issue with a dangling pointer in a kernel device-management path. Even though exploitation beyond DoS is not demonstrated, stale pointer use after later asynchronous SFP events is enough to require manual review.

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

Patch: net: phy: clean the sfp upstream if phy probing fails Sashiko reported that we don't call sfp_bus_del_upstream() in the probe failure path, so let's add it, otherwise the sfp-bus is left with a dangling 'upstream' field, that may be used later on during SFP events. This issue existed before the generic phylib sfp support, back when drivers were calling phy_sfp_probe themselves. Reviewed-by: Nicolai Buchwitz <nb@tipi-net.de> Fixes: 298e54f ("net: phy: add core phylib sfp support") Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com> Link: https://patch.msgid.link/20260604092819.723505-2-maxime.chevallier@bootlin.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Commit: 48774e87bbaa0056819d4b52301e4692e50e3252
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48774e87bbaa0056819d4b52301e4692e50e3252

Changed files:
  drivers/net/phy/phy_device.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=48774e87bbaa0056819d4b52301e4692e50e3252

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

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

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:H/I:H/A:H
  The Best / paranoid CVSS score: 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: 3
  Paranoid ActionableScore: 5

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 7.0

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