Skip to content
Heist/ feed
Back to feed
UnratedFix available

scsi: ufs: core: Fix invalid probe error return value

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix invalid probe error return value After DME Link Startup, the error return value is set to the MIPI UniPro GenericErrorCode which can be 0 (SUCCESS) or 1 (FAILURE). Upon failure during driver probe, the error code 1 is propagated back to the driver probe function which must return a negative value to indicate an error, but 1 is not negative, so the probe is considered to be successful even though it failed. Subsequently, removing the driver results in an oops because it is not in a valid state. This happens because none of the callers of ufshcd_init() expect a non-negative error code. Fix the return value and documentation to match actual usage.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.17.8
CVEs
CVE-2025-68316
Confirmed fixed CVEs
Not specified
Updated in this feed
2 Nov 2026, 18:58 UTC · Revision 1

Source evidence

scsi: ufs: core: Fix invalid probe error return value

core-osv · Original source

Published 16 Dec 2025, 15:39 UTC

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix invalid probe error return value After DME Link Startup, the error return value is set to the MIPI UniPro GenericErrorCode which can be 0 (SUCCESS) or 1 (FAILURE). Upon failure during driver probe, the error code 1 is propagated back to the driver probe function which must return a negative value to indicate an error, but 1 is not negative, so the probe is considered to be successful even though it failed. Subsequently, removing the driver results in an oops because it is not in a valid state. This happens because none of the callers of ufshcd_init() expect a non-negative error code. Fix the return value and documentation to match actual usage.

osv:CVE-2025-68316

Kernel

Fixed versions: 6.17.8

Complete source record
{
  "id": "f9bffccef29a7a63384045c77ec2841457ecf84029583cdf5eae8c08e469eda2",
  "url": "https://osv.dev/vulnerability/CVE-2025-68316",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "scsi: ufs: core: Fix invalid probe error return value",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix invalid probe error return value After DME Link Startup, the error return value is set to the MIPI UniPro GenericErrorCode which can be 0 (SUCCESS) or 1 (FAILURE). Upon failure during driver probe, the error code 1 is propagated back to the driver probe function which must return a negative value to indicate an error, but 1 is not negative, so the probe is considered to be successful even though it failed. Subsequently, removing the driver results in an oops because it is not in a valid state. This happens because none of the callers of ufshcd_init() expect a non-negative error code. Fix the return value and documentation to match actual usage.",
    "evidence": "osv:CVE-2025-68316",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.17.8",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-68316",
      "aliases": [
        "CVE-2025-68316"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "69f5eb78d4b0cc978fe83dd2bfea1b67547290bf"
                },
                {
                  "fixed": "df96dbe1af7f6591c09f862f1226d3619b07e1b6"
                },
                {
                  "fixed": "a2b32bc1d9e359a9f90d0de6af16699facb10935"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68316.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.17.8"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68316.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:22.798374653Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/a2b32bc1d9e359a9f90d0de6af16699facb10935",
        "https://git.kernel.org/stable/c/df96dbe1af7f6591c09f862f1226d3619b07e1b6",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68316.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-68316",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68316.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-68316",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 488888,
  "published_at": "2025-12-16T15:39:46.434+00:00"
}