CVE-2026-53232

Description

A flaw was found in the Linux kernel's network PHY (Physical Layer) driver. When a PHY probing operation fails, the system does not properly clean up the SFP (Small Form-Factor Pluggable) upstream connection. This oversight leaves a dangling reference in the SFP bus, which could be accessed later during SFP events. This improper resource management may lead to system instability or unexpected behavior.

Statement

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.

Mitigation

Mitigation for this issue is either not available or the currently available options don't 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 HatNVDcve.org
Base Score4.8N/A8.8
Attack VectorAdjacent NetworkN/AAdjacent Network
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.