[CVE-2026-80993][LOW] net: phylink: correctly validate returned PCS in phylink_inband_caps

[CVE-2026-80993][LOW] net: phylink: correctly validate returned PCS in phylink_inband_caps

[AL-KERNEL]

CVE: CVE-2026-80993
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net: phylink: correctly validate returned PCS in phylink_inband_caps
Commit: b6b533f83461c3730875cf3ed5ff6362dcb67be9
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b6b533f83461c3730875cf3ed5ff6362dcb67be9
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80993
Analysis date: Sat, 12 Sep 2026 02:31:15 -0400
ActionableScore: 2
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-80993	LOW	https://www.kernelcve.org/list/?q=CVE-2026-80993 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:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-252;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'phylink_inband_caps() only checked whether mac_select_pcs() returned NULL, but the callback can also return ERR_PTR for unsupported or failed PCS selection. The returned error pointer could then be passed to phylink_pcs_inband_caps(), where it is treated as a valid phylink_pcs object and dereferenced, causing a kernel crash or oops. For the CVSS the PR:L is used for the paranoid score because some deployments may delegate network device control through CAP_NET_ADMIN or a reduced capability service account, although the normal administrator controlled path is closer to PR:H. The issue is not directly network reachable and is triggered through local control plane or driver configuration paths rather than packet traffic. Impact is denial of service via kernel crash. No direct confidentiality or integrity impact is supported because this is an error pointer dereference without a demonstrated memory corruption primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2)	YES	OOB DANGER SIMPLEFIX NETWORK LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=2
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 2
* Conservative score: 2
* Raw paranoid score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate**::

No floor or cap was applied.

2. Signal breakdown

Positive signals:

* +1 Weak indirect corruption candidate: `mac_select_pcs()` can return `ERR_PTR`, and the caller treated it as a valid `struct phylink_pcs`.
* +1 Reliable kernel crash / strong DoS: `phylink_pcs_inband_caps()` can dereference the invalid PCS pointer and panic or oops the kernel.

Negative / non-awarded signals:

* +0 Real UAF not awarded: no freed object or stale post-lifetime object use is established.
* +0 Controlled reclaim not demonstrated.
* +0 Arbitrary write not demonstrated.
* +0 Confidentiality and integrity impact not awarded: this is an error-pointer dereference, not an established disclosure or write primitive.
* +0 Remote reachability not established: this is not packet-processing input.
* +0 Extra availability not awarded: the same kernel panic is already counted once.
* +0 Race/timing penalty not applied: no race is involved.
* +0 Host-admin penalty not applied: host-admin-equivalent triggering is plausible but not positively established from the supplied patch alone.

3. Reachability analysis

The vulnerable path is in the phylink control/configuration path, not in normal packet receive or transmit processing. A realistic trigger likely requires causing a MAC driver `mac_select_pcs()` callback to return an error pointer for a selected interface mode or failed PCS selection.

The complete privilege boundary is not fully visible in the supplied patch. In normal systems this likely requires network device configuration privileges, such as `CAP_NET_ADMIN`, or a driver/device management path. It is not established that an ordinary unprivileged local user can trigger it. It is also not established that the complete trigger chain is namespace-scoped, because physical phylink-backed devices are usually host-owned and namespace movement alone does not prove access to the relevant hardware/control path.

No prior special boot option or rare hardware requirement is proven, but the issue is limited to systems using affected phylink/MAC/PCS driver paths. No network-packet remote trigger is supported.

4. Primitive and severity interpretation

The exact primitive is an invalid error-pointer dereference: `ERR_PTR` is returned where the caller only checked for `NULL`, then the pointer is passed as if it were a valid `struct phylink_pcs`.

This is not an active structured UAF and not fixed stale storage. It is a Class C crash/DoS primitive. The demonstrated consequence is kernel panic or oops. Stronger consequences such as privilege escalation, arbitrary read/write, or information disclosure are speculative and not supported by the patch.

`ImportantCandidate=NO` because there is no established memory lifetime violation, no controlled corruption, no authorization bypass, and no meaningful exploitation primitive beyond crash. `AutoDowngradeAllowed=YES` because this is a constrained crash-only invalid-pointer issue with no unresolved Class A or strong Class B primitive.

5. One-sentence report phrase

An ERR_PTR returned by mac_select_pcs() can be misinterpreted as a valid phylink_pcs object in phylink_inband_caps(), causing a local control-plane triggered kernel crash without evidence of confidentiality, integrity, or privilege-escalation impact.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: demonstrated impact is DoS-only via invalid error-pointer dereference, with no UAF, no controlled corruption, no remote packet trigger, and no authorization boundary bypass.

7. Call-site confidence

Call-site confidence: medium

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

Patch: net: phylink: correctly validate returned PCS in phylink_inband_caps
Commit: b6b533f83461c3730875cf3ed5ff6362dcb67be9
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b6b533f83461c3730875cf3ed5ff6362dcb67be9

Commit description:

In phylink_inband_caps(), the PCS returned by mac_select_pcs is only
checked if NULL but mac_select_pcs can also return an error pointer.

This can cause a kernel panic as phylink_pcs_inband_caps() only checks
if passed PCS is not NULL and directly dereference ops from the phylink_pcs
struct.

Use the IS_ERR_OR_NULL macro to address both case where the returned
PCS can be NULL or an error pointer and prevent a kernel panic.

Cc: stable@vger.kernel.org
Fixes: df874f9 ("net: phylink: add pcs_inband_caps() method")
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Link: https://patch.msgid.link/20260817213009.13924-1-ansuelsmth@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

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

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

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

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

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

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