CVE-2026-53232 (GCVE-0-2026-53232)
Vulnerability from cvelistv5 – Published: 2026-06-25 08:39 – Updated: 2026-08-05 12:34
VLAI
EPSS
VEX
Title
net: phy: clean the sfp upstream if phy probing fails
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.
Severity
8.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
298e54fa810e027f1b0800d789eb862592721f08 , < 12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b
(git)
Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 9326b654f90a09eadeb796c82801a5609d57f0c8 (git) Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 3a254779c169954fe23328a1db51f67be374f913 (git) Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 0b27701ce93161d7bbf4b25fa20ca59963b0e20c (git) Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 48774e87bbaa0056819d4b52301e4692e50e3252 (git) |
guessed | |
| Linux | Linux |
Affected:
5.5
Unaffected: 0 , < 5.5 (semver) Unaffected: 6.6.143 , ≤ 6.6.* (semver) Unaffected: 6.12.94 , ≤ 6.12.* (semver) Unaffected: 6.18.36 , ≤ 6.18.* (semver) Unaffected: 7.0.13 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/phy/phy_device.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "9326b654f90a09eadeb796c82801a5609d57f0c8",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "3a254779c169954fe23328a1db51f67be374f913",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "0b27701ce93161d7bbf4b25fa20ca59963b0e20c",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "48774e87bbaa0056819d4b52301e4692e50e3252",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/phy/phy_device.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.5"
},
{
"lessThan": "5.5",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.143",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.94",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.36",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"version": "7.0.13",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.143",
"versionStartIncluding": "5.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.94",
"versionStartIncluding": "5.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.36",
"versionStartIncluding": "5.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0.13",
"versionStartIncluding": "5.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1",
"versionStartIncluding": "5.5",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clean the sfp upstream if phy probing fails\n\nSashiko reported that we don\u0027t call sfp_bus_del_upstream() in the probe\nfailure path, so let\u0027s add it, otherwise the sfp-bus is left with a\ndangling \u0027upstream\u0027 field, that may be used later on during SFP events.\n\nThis issue existed before the generic phylib sfp support, back when\ndrivers were calling phy_sfp_probe themselves."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 8.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:A - The stale upstream pointer is dereferenced from SFP cage events such as module presence and LOS/link changes, which can be driven by a directly connected SFP link partner. It is not reachable through ordinary routed network packets or an unprivileged syscall path.\nAC:L - Once an affected PHY/SFP configuration has hit the failed-probe state, later SFP events reliably call the stale upstream callbacks. There is no attacker-won race or complex timing requirement in the event path.\nPR:N - An adjacent physical/link-layer attacker does not need kernel privileges or authentication to trigger SFP signal events. No CAP_NET_ADMIN or user-namespace route is required for that trigger path.\nUI:N - After the system is in the vulnerable failed-probe state, exploitation is triggered by SFP events without a victim user performing an action. The attacker can induce the relevant link/module event directly.\nS:U - The affected code and resulting impact are within the Linux kernel networking/PHY security authority. There is no VM, IOMMU, or separate-scope boundary crossing.\nC:H - The bug leaves a dangling `phy_device` upstream pointer that later SFP callbacks dereference, creating a kernel use-after-free style condition. Kernel UAF conditions are treated as capable of exposing arbitrary kernel memory.\nI:H - The stale pointer callbacks read and write fields through the freed or invalid `phy_device` and may reach attacker-influenced object contents after reuse. Kernel UAF memory corruption is treated as potentially enabling arbitrary write or code execution.\nA:H - Even without full exploitation, dereferencing the dangling upstream pointer during SFP events can crash or oops the kernel. Kernel crashes are high availability impact."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T12:34:23.514Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b"
},
{
"url": "https://git.kernel.org/stable/c/9326b654f90a09eadeb796c82801a5609d57f0c8"
},
{
"url": "https://git.kernel.org/stable/c/3a254779c169954fe23328a1db51f67be374f913"
},
{
"url": "https://git.kernel.org/stable/c/0b27701ce93161d7bbf4b25fa20ca59963b0e20c"
},
{
"url": "https://git.kernel.org/stable/c/48774e87bbaa0056819d4b52301e4692e50e3252"
}
],
"title": "net: phy: clean the sfp upstream if phy probing fails",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-53232",
"datePublished": "2026-06-25T08:39:30.527Z",
"dateReserved": "2026-06-09T07:44:35.393Z",
"dateUpdated": "2026-08-05T12:34:23.514Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-53232",
"date": "2026-10-03",
"epss": "0.00254",
"percentile": "0.15354"
},
"microsoft_vex": {
"current_release_date": "2026-06-28T01:41:39.000Z",
"cve": "CVE-2026-53232",
"id": "msrc_CVE-2026-53232",
"initial_release_date": "2026-06-02T00:00:00.000Z",
"product_status:known_affected": "2",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "net: phy: clean the sfp upstream if phy probing fails",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-53232.json",
"version": "2"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/phy/phy_device.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "9326b654f90a09eadeb796c82801a5609d57f0c8",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "3a254779c169954fe23328a1db51f67be374f913",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "0b27701ce93161d7bbf4b25fa20ca59963b0e20c",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
},
{
"lessThan": "48774e87bbaa0056819d4b52301e4692e50e3252",
"status": "affected",
"version": "298e54fa810e027f1b0800d789eb862592721f08",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/phy/phy_device.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.5"
},
{
"lessThan": "5.5",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.143",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.94",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.36",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"version": "7.0.13",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "6F0D8DAC-6E14-4C87-8E08-01985E0990CC",
"versionEndExcluding": "7.1",
"versionStartIncluding": "5.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*",
"matchCriteriaId": "B1EF7059-E670-45F4-B422-54C40FA86390",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*",
"matchCriteriaId": "0D38F0BF-A728-4133-A358-D44A2F7EE6D6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*",
"matchCriteriaId": "EC732D08-5F7B-46D9-B154-E60C7F4F0A97",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*",
"matchCriteriaId": "E5910A9D-F60A-409A-B486-FE66BFEBA9B9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*",
"matchCriteriaId": "81DFF19E-9CF8-49C6-8C36-1E4038622933",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:*",
"matchCriteriaId": "B0E8FC71-3952-444C-83E9-718DBBBEC615",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:*",
"matchCriteriaId": "1039E95A-8CC3-4C88-8FF9-5C08EEB861C9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clean the sfp upstream if phy probing fails\n\nSashiko reported that we don\u0027t call sfp_bus_del_upstream() in the probe\nfailure path, so let\u0027s add it, otherwise the sfp-bus is left with a\ndangling \u0027upstream\u0027 field, that may be used later on during SFP events.\n\nThis issue existed before the generic phylib sfp support, back when\ndrivers were calling phy_sfp_probe themselves."
}
],
"id": "CVE-2026-53232",
"lastModified": "2026-07-16T12:18:07.027",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-06-25T09:16:41.107",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0b27701ce93161d7bbf4b25fa20ca59963b0e20c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3a254779c169954fe23328a1db51f67be374f913"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/48774e87bbaa0056819d4b52301e4692e50e3252"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/9326b654f90a09eadeb796c82801a5609d57f0c8"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-07-16T12:08:06+00:00",
"cve": "CVE-2026-53232",
"id": "CVE-2026-53232",
"initial_release_date": "2026-06-25T00:00:00+00:00",
"product_status:known_affected": "246",
"product_status:known_not_affected": "28",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: net: phy: clean the sfp upstream if phy probing fails",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53232.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-09-10T02:38:40Z",
"cve": "CVE-2026-53232",
"id": "CVE-2026-53232",
"initial_release_date": "2026-06-26T02:09:17Z",
"product_status:known_affected": "262",
"product_status:known_not_affected": "125",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-53232",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-53232.json",
"version": "8"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…