CVE-2026-80993
Description
A flaw was found in the Linux kernel's net: phylink component. The phylink_inband_caps() function does not correctly validate the return value from mac_select_pcs, which can return an error pointer instead of a valid Physical Coding Sublayer (PCS) object. This oversight can lead to dereferencing an invalid pointer, causing a kernel panic. A kernel panic results in a system crash, leading to a Denial of Service (DoS).
Statement
A low impact flaw was found in the Linux kernel's networking phylink subsystem. In phylink_inband_caps(), the Physical Coding Sublayer (PCS) pointer returned by the mac_select_pcs callback was only checked against NULL, even though mac_select_pcs can also return an error pointer. phylink_pcs_inband_caps() subsequently dereferences such an unvalidated pointer, which can cause a kernel panic that crashes the system and results in a local denial of service. Exploiting this flaw requires local access to a system and the ability to exercise the affected phylink/network device configuration code path; there is no impact on confidentiality or integrity (Red Hat CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Within Red Hat's product portfolio, the flaw affects the kernel and kernel-rt packages in current Red Hat Enterprise Linux 9 and 10 update streams and the RHEL CoreOS kernel shipped in recent OpenShift Container Platform 4 releases. Earlier Red Hat Enterprise Linux and OpenShift streams are not affected because the vulnerable code is not present in the kernel versions they ship. For the affected products the fix is deferred given the low security impact of this flaw; the residual risk is that a local user able to trigger the affected code path can cause a kernel panic and deny service to the system.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart
NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.
Integrity,Confidentiality
Technical Impact: Execute Unauthorized Code or Commands; Read Memory; Modify Memory
In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.