[CVE-2026-98563][IMPORTANT] net: phylink: record the PHY only once bringup cannot fail [ Upstream

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

CVE: CVE-2026-98563
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: YES
Patch: net: phylink: record the PHY only once bringup cannot fail [ Upstream
Commit: 4e7a4af364c2048bafb213bf0ef4a89dcbe1bfd4
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4e7a4af364c2048bafb213bf0ef4a89dcbe1bfd4
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98563
Analysis date: Sun, 18 Oct 2026 22:40:25 -0400
ActionableScore: 5
ActionableScore lower bound: unknown
Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review
Manual review required: YES

Summary:
A failed phylink PHY bringup can leave `pl->phydev` referencing a freed active `phy_device`, allowing later resolve, ethtool, or disconnect paths to perform stale reads and a concrete second detach that may corrupt lifetime state or crash the kernel.

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

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

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: IMPORTANT
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-98563	IMPORTANT	https://www.kernelcve.org/list/?q=CVE-2026-98563 CHECK WITH IMPACT FROM ORIG NN IMPORTANT | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=4 LEGACY=IMPORTANT RESULT=DIFF INDEPENDENT_LEGACY=IMPORTANT INDEPENDENT_RESULT=DIFF TEMP_KPANIC_MERGE=IMPORTANT_WINS_DISAGREEMENT PRE_MERGE_LEGACY=IMPORTANT (final Legacy and Aegis differ; FINAL: IMPORTANT, Aegis: MODERATE_KPANIC)	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-672;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A failed PHY bringup can leave pl phydev pointing to a detached phy_device because the pointer is published before the final fallible MDIO operation. In the SFP path, error cleanup can remove and free that phy_device while phylink_resolve and ethtool helpers continue to read the stale pointer. A later disconnect can also pass the stale object to phy_disconnect and repeat reference releases that were already performed by the first phy_detach. Impact is at least a local denial of service through a kernel fault and the confirmed use after free may permit confidentiality, integrity, or privilege escalation impact if the freed object can be reclaimed with controlled data. For the CVSS the PR:L reflects a paranoid case where a local user or reduced capability service can reach an ethtool path after the failed PHY connection state has occurred. Reliable creation of that state may still require network administration access, SFP or DSA activity, a delayed PHY driver, and a real MDIO failure. The issue is not directly network reachable through ordinary packets and AC:H reflects the required failure state and lifecycle timing. Automated impact decision path. The original SimpleNet classifier selected IMPORTANT. The primary LLM estimated paranoid CVSS 7 and the production ActionableScore returned 5 with recommendation Actionable Moderate / Strong Important candidate requiring manual review. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. No severity changing production threshold or specialist override was recorded. The legacy KP specialist produced a review artifact and its decision was processed by the applicable KP rules. The legacy FD or DH downgrade specialist produced a review artifact and its decision was processed by the applicable downgrade and preservation rules. Exact triggered rule markers were TEMP_KPANIC_MERGE_IMPORTANT_WINS. The independent weaker Aegis shadow evaluated CVSS 1.9 and ActionableScore 4 with primitive class CLASS_B and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is IMPORTANT.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5)	MAYBE	LOCK DANGER UAF NETWORK DMAorINTERRUPT LINUS KPANIC  TEMP_KPANIC_MERGE_IMPORTANT_WINS	-	-	checked

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

ActionableScore=5
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=YES
ManualReview=REQUIRED
AutoDowngradeAllowed=NO
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw conservative score: 4
* Conservative score: 5
* Raw paranoid score: 5
* Paranoid score: 5
* Applied conservative FLOOR 5: 4 -> 5 because the first detach and free can end the PHY lifetime, the exact stale pointer survives, and a later disconnect performs another lifetime-mutating detach.
* Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**::

2. Signal breakdown

* +2 Real UAF: the SFP error path can execute `phy_device_remove()` and `phy_device_free()` while `pl->phydev` continues to reference that freed `phy_device`.
* +1 Concrete repeated release/refcount operation: the initial unwind calls `phy_detach()`, while a later `phylink_disconnect_phy()` passes the same stale pointer to `phy_disconnect()`, which performs a second `phy_detach()` and drops references already released.
* +1 Reliable kernel crash or strong DoS: `phylink_resolve()`, ethtool helpers, or disconnect processing can dereference or mutate the lifetime state of the freed PHY.
* +1 Paranoid repeated-refcount leverage: the second detach is a concrete write-like lifetime or reference mutation through storage whose original object lifetime may already have ended.
* First release can end lifetime: YES. The SFP path additionally performs explicit remove and free operations.
* Exact same reference survives: YES. `pl->phydev` is not cleared during failed bringup cleanup.
* Second operation mutates lifetime or refcount: YES. `phy_disconnect()` reaches another `phy_detach()`.
* Dedicated repeated-release +1 awarded: YES.
* Paranoid repeated-refcount +1 awarded: YES.
* FLOOR 5 applied: YES, to the conservative score only.
* Structured stale-object leverage not separately awarded: the stale reads by resolve and ethtool are concrete, but attacker-controlled reclaim or meaningful influence over replacement contents is not established.
* Weak LPE not separately awarded because the concrete second lifetime mutation is already scored.
* Controlled reclaim, arbitrary write, callback control, disclosure, and privilege escalation are not demonstrated.
* No extra Availability point was awarded because it would duplicate the same kernel-fault consequence.
* No remote-reachability point was awarded. Ordinary network packets do not directly trigger the failed PHY bringup sequence.
* No hardware penalty was applied merely because SFP, PHY, DSA, and MDIO are involved. The supplied evidence does not establish physical-only or genuinely rare hardware.
* No race penalty was applied. This is an ordered failed-initialization and cleanup sequence rather than a demonstrated narrow race.
* B5-R does not apply because no retry-accumulated heap OOB write exists.
* B3-PENDING does not apply because no shared-backing write exists.
* V32, V33, and V34 do not apply because no checksum metadata or cross-boundary skb header corruption is involved.
* B4-PENDING does not apply because no authorization decision changes from DENY to ALLOW.

3. Reachability analysis

The vulnerable state requires a failed PHY bringup after `pl->phydev` has been published. The documented SFP path can then free the PHY while retaining the stale pointer. A later resolver, ethtool query, or disconnect consumes that pointer.

The complete attacker privilege is unresolved. Triggering the initial condition may require SFP or DSA activity, delayed PHY-driver binding, and a genuine MDIO failure. The evidence does not establish that an ordinary user, namespace-scoped `CAP_NET_ADMIN`, or delegated service can produce the complete sequence. It also does not positively establish that host-admin-equivalent privilege is mandatory.

There is no evidence that all required operations work inside an attacker-created user or network namespace. No remote packet-only path is established. This is not a timing race, although successful triggering depends on a particular initialization failure and later use or disconnect.

4. Primitive and severity interpretation

The exact primitive is an active structured-object UAF. `pl->phydev` escapes failed initialization and can point to a freed `struct phy_device`. This is not fixed stale storage because later phylink and ethtool processing treats the address as a live PHY object.

The issue contains both broader active use and a concrete repeated lifetime operation:

A. The stale object is read by `phylink_resolve()` and ethtool helpers.

B. A later disconnect passes the same potentially dangling reference to `phy_disconnect()`, causing another `phy_detach()` and repeated release of references.

Category B is stronger than an ordinary cleanup-only stale dereference because the second operation actively mutates lifetime state through a potentially freed object. It remains CLASS_B rather than CLASS_A because controlled reclaim, refcount takeover, directed corruption, arbitrary kernel read or write, and LPE are not established.

The demonstrated consequences are permanent `EBUSY` in one connection path, UAF reads in the SFP path, repeated reference release, and a plausible kernel crash. A non-crash exploitation path remains unresolved rather than proven. ImportantCandidate is YES and AutoDowngradeAllowed is NO because automatically reducing this to crash-only behavior would discard the concrete second lifetime mutation.

5. One-sentence report phrase

A failed phylink PHY bringup can leave `pl->phydev` referencing a freed active `phy_device`, allowing later resolve, ethtool, or disconnect paths to perform stale reads and a concrete second detach that may corrupt lifetime state or crash the kernel.

6. Manual review recommendation

MANUAL CHECK REQUIRED

Review PHY allocation and reuse, the exact reference changes performed by both detach operations, stale-field consumption in `phylink_resolve()` and ethtool handlers, and whether the second detach can affect reclaimed slab storage before an immediate fault.

7. Call-site confidence

Call-site confidence: high

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

Patch: net: phylink: record the PHY only once bringup cannot fail [ Upstream
Commit: 4e7a4af364c2048bafb213bf0ef4a89dcbe1bfd4
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4e7a4af364c2048bafb213bf0ef4a89dcbe1bfd4

Changed files:
  drivers/net/phy/phylink.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=4e7a4af364c2048bafb213bf0ef4a89dcbe1bfd4

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

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

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: unknown
  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: IMPORTANT
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): IMPORTANT

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