Vulnerability-Lookup

GHSA-GRRC-M4H5-R55J

Vulnerability from github – Published: 2026-06-25 09:31 – Updated: 2026-07-16 12:32

Details

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)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-53232"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-25T09:16:41Z",
    "severity": "HIGH"
  },
  "details": "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": "GHSA-grrc-m4h5-r55j",
  "modified": "2026-07-16T12:32:26Z",
  "published": "2026-06-25T09:31:21Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53232"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0b27701ce93161d7bbf4b25fa20ca59963b0e20c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3a254779c169954fe23328a1db51f67be374f913"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/48774e87bbaa0056819d4b52301e4692e50e3252"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9326b654f90a09eadeb796c82801a5609d57f0c8"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-53232 (GCVE-0-2026-53232)

Vulnerability from cvelistv5 – Published: 2026-06-25 08:39 – Updated: 2026-08-05 12:34

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)


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

Assigner

Linux mitre root

References

5 references

URL	Tags
https://git.kernel.org/stable/c/12fb84dc4dc8eb47e…
https://git.kernel.org/stable/c/9326b654f90a09ead…
https://git.kernel.org/stable/c/3a254779c169954fe…
https://git.kernel.org/stable/c/0b27701ce93161d7b…
https://git.kernel.org/stable/c/48774e87bbaa00568…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b (git) Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 9326b654f90a09eadeb796c82801a5609d57f0c8 (git) Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 3a254779c169954fe23328a1db51f67be374f913 (git) Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 0b27701ce93161d7bbf4b25fa20ca59963b0e20c (git) Affected: 298e54fa810e027f1b0800d789eb862592721f08 , < 48774e87bbaa0056819d4b52301e4692e50e3252 (git)
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)

Show details on NVD website

JSON

To clipboard

{
  "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"
}

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.

Detection rules are retrieved from Rulezet.

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.

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.

Action not permitted

GHSA-GRRC-M4H5-R55J

CVE-2026-53232 (GCVE-0-2026-53232)

Tags

Sightings

Nomenclature

Related by attack behaviour