cve.bz

CVE-2026-53232 linux linux kernel: Use After Free

8.8 highEPSS 0.3%Fix available

High (8.8) in linux linux kernel. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: net: phy: clean the sfp upstream if phy probing fails Sashiko reported that we don't call sfp_bus_del_upstream() in the probe failure path, so let's add it, otherwise the sfp-bus is left with a dangling 'upstream' field, that may be used later on during SFP events. This issue existed before the generic phylib sfp support, back when drivers were calling phy_sfp_probe themselves.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53232 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53232?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53232?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53232 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.5 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.143
Linux6.126.12.94
Linux6.186.18.36
Linux7.07.0.13
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-53232
Debian13linux6.12.94-1DEBIAN-CVE-2026-53232
Debian14linux7.0.13-1DEBIAN-CVE-2026-53232
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-53232
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-53232
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-53232
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 47 moreno fix listedUBUNTU-CVE-2026-53232
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1066.69~22.04.1UBUNTU-CVE-2026-53232 USN-8903-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1068.75~22.04.1UBUNTU-CVE-2026-53232 USN-8904-1
Ubuntu22.04:LTSlinux-gcp-6.8, linux-azure-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-53232 USN-8904-1 USN-8905-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-53232 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1066.67~22.04.1UBUNTU-CVE-2026-53232 USN-8906-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-146.146.1~22.04.1UBUNTU-CVE-2026-53232 USN-8903-2
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1064.67~22.04.1UBUNTU-CVE-2026-53232 USN-8903-2
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-53232 USN-9025-1
47 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.144.1-1AZL-90777
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-53232
Alpaquita25linux-lts6.12.95-r0BELL-CVE-2026-53232
Alpaquitastreamlinux-lts6.18.38-r0BELL-CVE-2026-53232

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's 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.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-53232.

References

Check your stackJSON