[CVE-2026-53231][LOW] net: phy: don't try to setup PHY-driven SFP cages when using genphy [ Upstream

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

CVE: CVE-2026-53231
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net: phy: don't try to setup PHY-driven SFP cages when using genphy [ Upstream
Commit: ef8d739eee6f85303cbecebc01eb72f063de74e0
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ef8d739eee6f85303cbecebc01eb72f063de74e0
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53231
Analysis date: Mon, 29 Jun 2026 11:01:29 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like. Auto-close candidate unless the affected platform uses genphy with PHY-driven SFP cages
Manual review required: NO

Summary:
A genphy PHY setup path can deadlock on RTNL when unsupported PHY-driven SFP probing calls sfp_bus_add_upstream, causing a local network control-plane DoS on affected hardware configurations.

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

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

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-53231	LOW	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:N/I:N/A:H';*CWE-833;CWE-667;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 'A deadlock in the PHY setup path can occur when genphy attempts to run PHY driven SFP probing. The genphy binding path already runs with RTNL involvement, and calling sfp_bus_add_upstream from this path can deadlock on RTNL. This can stall PHY probing or network device setup and can block later network configuration operations. For the CVSS the PR:L is used only for the paranoid score because a reduced capability network management service or container with delegated device control might be able to trigger reprobe like operations. The issue is not directly network reachable and is not caused by packet processing. Impact is denial of service only through a stuck RTNL or network control path, with no evidence of memory corruption, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like. Auto-close candidate unless the affected platform uses genphy with PHY-driven SFP cages (with actual score 1)  SKIP CVE-2026-53231  SKIP The Fixes patch not applied yet, so unlikely that actual: bad869b5e41a08424ff130fd6bb41b854be70095 YES  NO NO unknown 	MAYBE	DEADLOCK SIMPLEFIX NETWORK LINUS  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. Auto-close candidate unless the affected platform uses genphy with PHY-driven SFP cages**

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The commit says the issue was reproduced and leads to an RTNL deadlock.
* Requires admin/root/CAP_NET_ADMIN or equivalent device-management control in typical deployments: -2. A reliable trigger generally requires PHY probing, driver binding, device setup, or hardware management.
* Rare AND difficult-to-reach subsystem/configuration: -1. The condition requires genphy plus PHY-driven SFP cage probing, not ordinary packet traffic.

Conservative total is below zero, clamped to 0.

Paranoid signals:

* Reliable kernel crash / strong DoS: +1. RTNL deadlock can stall network device setup and network control-plane operations.
* No full admin penalty in the paranoid interpretation. A reduced-capability network-management service, init system component, or delegated container environment might be able to trigger reprobe-like behavior without full host-root equivalence.
* No memory corruption, no UAF, no OOB access, no confidentiality impact, no integrity impact, and no remote packet-triggered path are supported by the patch.

Paranoid total: 1.

## 3. Reachability analysis

The bug is triggered during PHY setup when genphy incorrectly attempts PHY-driven SFP probing. It is not reachable from normal network packet processing and is not remotely triggerable by sending traffic. In typical deployments, triggering requires local administrative control over driver/device setup or a boot/probe path on affected hardware. Namespaces or containers only matter if device or network-management capabilities are explicitly delegated. The affected path is configuration and hardware dependent, not a broad default attack surface.

## 4. Severity interpretation

This behaves like a Low-like or ordinary Moderate availability issue, not an Important-class vulnerability. The realistic impact is a local or boot-time network control-plane deadlock on RTNL. There is no evidence of memory corruption, privilege escalation, sensitive data exposure, or cross-boundary policy bypass. The theoretical worst case is a stronger local DoS if an attacker can repeatedly force reprobe or device setup on affected hardware, but the patch does not support escalation beyond availability.

## 5. One-sentence report phrase

A genphy PHY setup path can deadlock on RTNL when unsupported PHY-driven SFP probing calls sfp_bus_add_upstream, causing a local network control-plane DoS on affected hardware configurations.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This is a reproduced deadlock but remains DoS-only, hardware/configuration dependent, not packet-reachable, and not supported by any memory corruption or privilege-escalation primitive.

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

Patch: net: phy: don't try to setup PHY-driven SFP cages when using genphy [ Upstream
Commit: ef8d739eee6f85303cbecebc01eb72f063de74e0
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ef8d739eee6f85303cbecebc01eb72f063de74e0

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

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

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

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