CVE-2026-53232 json
net: phy: clean the sfp upstream if phy probing fails
published 2026-06-25 4 mo ago modified 2026-10-30 9 d ago also EUVD-2026-39323
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.143, 6.12.94, 6.18.36, 7.0.13, 7.1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.13-1
debian advisories DEBIAN-CVE-2026-53232
- linux Ubuntu 24.04 LTS 6.8.0-146.146
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 24.04 LTS 6.8.0-1066.69
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1070.78
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1011.11
- linux-gke Ubuntu 24.04 LTS 6.8.0-1065.73
- linux-gke Ubuntu 26.04 LTS 7.0.0-1006.7
ubuntu advisories UBUNTU-CVE-2026-53232
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/18c7c311323b19a353c3042180982e0ce5fa7e5f commit
- git.kernel.org/stable/c/12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b commit
- git.kernel.org/stable/c/9326b654f90a09eadeb796c82801a5609d57f0c8 commit
- git.kernel.org/stable/c/3a254779c169954fe23328a1db51f67be374f913 commit
- git.kernel.org/stable/c/0b27701ce93161d7bbf4b25fa20ca59963b0e20c commit
- git.kernel.org/stable/c/48774e87bbaa0056819d4b52301e4692e50e3252 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-53232 updated cvss 4.8
kernel: net: phy: clean the sfp upstream if phy probing fails
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
- git.kernel.org /stable/c/18c7c311323b19a353c3042180982e0ce5fa7e5f
- git.kernel.org /stable/c/12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b
- git.kernel.org /stable/c/9326b654f90a09eadeb796c82801a5609d57f0c8
- git.kernel.org /stable/c/3a254779c169954fe23328a1db51f67be374f913
- git.kernel.org /stable/c/0b27701ce93161d7bbf4b25fa20ca59963b0e20c
-
git.kernel.org
/stable/c/48774e87bbaa0056819d4b52301e4692e50e3252
patch
Sources
- CVE List CVE-2026-53232
- NVD CVE-2026-53232
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.