CVE-2025-68746 (GCVE-0-2025-68746)
Vulnerability from cvelistv5
Published
2025-12-24 12:09
Modified
2025-12-24 12:09
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Fix timeout handling When the CPU that the QSPI interrupt handler runs on (typically CPU 0) is excessively busy, it can lead to rare cases of the IRQ thread not running before the transfer timeout is reached. While handling the timeouts, any pending transfers are cleaned up and the message that they correspond to is marked as failed, which leaves the curr_xfer field pointing at stale memory. To avoid this, clear curr_xfer to NULL upon timeout and check for this condition when the IRQ thread is finally run. While at it, also make sure to clear interrupts on failure so that new interrupts can be run. A better, more involved, fix would move the interrupt clearing into a hard IRQ handler. Ideally we would also want to signal that the IRQ thread no longer needs to be run after the timeout is hit to avoid the extra check for a valid transfer.
References
Impacted products
Vendor Product Version
Linux Linux Version: 921fc1838fb036f690b8ba52e6a6d3644b475cbb
Version: 921fc1838fb036f690b8ba52e6a6d3644b475cbb
Version: 921fc1838fb036f690b8ba52e6a6d3644b475cbb
Version: 921fc1838fb036f690b8ba52e6a6d3644b475cbb
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi-tegra210-quad.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "551060efb156c50fe33799038ba8145418cfdeef",
              "status": "affected",
              "version": "921fc1838fb036f690b8ba52e6a6d3644b475cbb",
              "versionType": "git"
            },
            {
              "lessThan": "bb0c58be84f907285af45657c1d4847b960a12bf",
              "status": "affected",
              "version": "921fc1838fb036f690b8ba52e6a6d3644b475cbb",
              "versionType": "git"
            },
            {
              "lessThan": "01bbf25c767219b14c3235bfa85906b8d2cb8fbc",
              "status": "affected",
              "version": "921fc1838fb036f690b8ba52e6a6d3644b475cbb",
              "versionType": "git"
            },
            {
              "lessThan": "b4e002d8a7cee3b1d70efad0e222567f92a73000",
              "status": "affected",
              "version": "921fc1838fb036f690b8ba52e6a6d3644b475cbb",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/spi/spi-tegra210-quad.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.12"
            },
            {
              "lessThan": "5.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.63",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.17.*",
              "status": "unaffected",
              "version": "6.17.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.63",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.17.13",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.2",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19-rc1",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: tegra210-quad: Fix timeout handling\n\nWhen the CPU that the QSPI interrupt handler runs on (typically CPU 0)\nis excessively busy, it can lead to rare cases of the IRQ thread not\nrunning before the transfer timeout is reached.\n\nWhile handling the timeouts, any pending transfers are cleaned up and\nthe message that they correspond to is marked as failed, which leaves\nthe curr_xfer field pointing at stale memory.\n\nTo avoid this, clear curr_xfer to NULL upon timeout and check for this\ncondition when the IRQ thread is finally run.\n\nWhile at it, also make sure to clear interrupts on failure so that new\ninterrupts can be run.\n\nA better, more involved, fix would move the interrupt clearing into a\nhard IRQ handler. Ideally we would also want to signal that the IRQ\nthread no longer needs to be run after the timeout is hit to avoid the\nextra check for a valid transfer."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-12-24T12:09:42.213Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/551060efb156c50fe33799038ba8145418cfdeef"
        },
        {
          "url": "https://git.kernel.org/stable/c/bb0c58be84f907285af45657c1d4847b960a12bf"
        },
        {
          "url": "https://git.kernel.org/stable/c/01bbf25c767219b14c3235bfa85906b8d2cb8fbc"
        },
        {
          "url": "https://git.kernel.org/stable/c/b4e002d8a7cee3b1d70efad0e222567f92a73000"
        }
      ],
      "title": "spi: tegra210-quad: Fix timeout handling",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-68746",
    "datePublished": "2025-12-24T12:09:42.213Z",
    "dateReserved": "2025-12-24T10:30:51.031Z",
    "dateUpdated": "2025-12-24T12:09:42.213Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-68746\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-24T13:16:29.533\",\"lastModified\":\"2025-12-24T13:16:29.533\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nspi: tegra210-quad: Fix timeout handling\\n\\nWhen the CPU that the QSPI interrupt handler runs on (typically CPU 0)\\nis excessively busy, it can lead to rare cases of the IRQ thread not\\nrunning before the transfer timeout is reached.\\n\\nWhile handling the timeouts, any pending transfers are cleaned up and\\nthe message that they correspond to is marked as failed, which leaves\\nthe curr_xfer field pointing at stale memory.\\n\\nTo avoid this, clear curr_xfer to NULL upon timeout and check for this\\ncondition when the IRQ thread is finally run.\\n\\nWhile at it, also make sure to clear interrupts on failure so that new\\ninterrupts can be run.\\n\\nA better, more involved, fix would move the interrupt clearing into a\\nhard IRQ handler. Ideally we would also want to signal that the IRQ\\nthread no longer needs to be run after the timeout is hit to avoid the\\nextra check for a valid transfer.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/01bbf25c767219b14c3235bfa85906b8d2cb8fbc\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/551060efb156c50fe33799038ba8145418cfdeef\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b4e002d8a7cee3b1d70efad0e222567f92a73000\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bb0c58be84f907285af45657c1d4847b960a12bf\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.