CVE-2026-68438 (GCVE-0-2026-68438)

Vulnerability from cvelistv5 – Published: 2026-08-12 00:07 – Updated: 2026-08-17 05:05
VLAI
Title
smp: Make CSD lock acquisition atomic for debug mode
Summary
In the Linux kernel, the following vulnerability has been resolved: smp: Make CSD lock acquisition atomic for debug mode Commit b0473dcd4b1d ("smp: Improve smp_call_function_single() CSD-lock diagnostics") changed smp_call_function_single() so that, when CSD lock debugging is enabled, async !wait calls use the destination CPU csd_data. That improves diagnostics, but it also removes the single-writer property that made the old csd_lock() safe: multiple CPUs can now prepare the same destination CPU CSD concurrently. csd_lock() currently waits for CSD_FLAG_LOCK to clear and then sets the bit with a non-atomic read-modify-write. Two senders can both see an unlocked CSD, set the bit, overwrite the callback fields, and enqueue the same llist node. Re-adding a node that is already the queue head can make node->next point to itself, leaving the target CPU stuck walking call_single_queue. Later synchronous work, such as a TLB shootdown, can then remain queued and trigger soft-lockup warnings or panics. Keep the single csd_lock() implementation, but when CSD lock debugging is enabled, acquire CSD_FLAG_LOCK with try_cmpxchg_acquire(). This makes the destination CPU CSD a real atomic lock in the only configuration where it can be shared by multiple remote senders, while preserving the existing non-debug fast path.
Severity
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: b0473dcd4b1d7e2e44947e7ac1820c73a268821a , < 282d220bae5fbfc90cf0e3d5b5e42c00ad79f989 (git)
Affected: b0473dcd4b1d7e2e44947e7ac1820c73a268821a , < 35551efb155e3b83445a6c3f66cb498d5efc182c (git)
guessed Create a notification for this product.
Linux Linux Affected: 7.1
Unaffected: 0 , < 7.1 (semver)
Unaffected: 7.1.6 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/smp.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "282d220bae5fbfc90cf0e3d5b5e42c00ad79f989",
              "status": "affected",
              "version": "b0473dcd4b1d7e2e44947e7ac1820c73a268821a",
              "versionType": "git"
            },
            {
              "lessThan": "35551efb155e3b83445a6c3f66cb498d5efc182c",
              "status": "affected",
              "version": "b0473dcd4b1d7e2e44947e7ac1820c73a268821a",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/smp.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.6",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmp: Make CSD lock acquisition atomic for debug mode\n\nCommit b0473dcd4b1d (\"smp: Improve smp_call_function_single()\nCSD-lock diagnostics\") changed smp_call_function_single() so that,\nwhen CSD lock debugging is enabled, async !wait calls use the\ndestination CPU csd_data. That improves diagnostics, but it also removes\nthe single-writer property that made the old csd_lock() safe: multiple\nCPUs can now prepare the same destination CPU CSD concurrently.\n\ncsd_lock() currently waits for CSD_FLAG_LOCK to clear and then sets the\nbit with a non-atomic read-modify-write. Two senders can both see an\nunlocked CSD, set the bit, overwrite the callback fields, and enqueue\nthe same llist node. Re-adding a node that is already the queue head can\nmake node-\u003enext point to itself, leaving the target CPU stuck walking\ncall_single_queue. Later synchronous work, such as a TLB shootdown, can\nthen remain queued and trigger soft-lockup warnings or panics.\n\nKeep the single csd_lock() implementation, but when CSD lock debugging is\nenabled, acquire CSD_FLAG_LOCK with try_cmpxchg_acquire(). This makes the\ndestination CPU CSD a real atomic lock in the only configuration where it\ncan be shared by multiple remote senders, while preserving the existing\nnon-debug fast path."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:05:35.262Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/282d220bae5fbfc90cf0e3d5b5e42c00ad79f989"
        },
        {
          "url": "https://git.kernel.org/stable/c/35551efb155e3b83445a6c3f66cb498d5efc182c"
        }
      ],
      "title": "smp: Make CSD lock acquisition atomic for debug mode",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-68438",
    "datePublished": "2026-08-12T00:07:27.105Z",
    "dateReserved": "2026-07-30T09:28:09.394Z",
    "dateUpdated": "2026-08-17T05:05:35.262Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-68438",
      "date": "2026-08-24",
      "epss": "0.00145",
      "percentile": "0.04023"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-68438\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-08-12T00:17:44.013\",\"lastModified\":\"2026-08-17T06:17:52.890\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsmp: Make CSD lock acquisition atomic for debug mode\\n\\nCommit b0473dcd4b1d (\\\"smp: Improve smp_call_function_single()\\nCSD-lock diagnostics\\\") changed smp_call_function_single() so that,\\nwhen CSD lock debugging is enabled, async !wait calls use the\\ndestination CPU csd_data. That improves diagnostics, but it also removes\\nthe single-writer property that made the old csd_lock() safe: multiple\\nCPUs can now prepare the same destination CPU CSD concurrently.\\n\\ncsd_lock() currently waits for CSD_FLAG_LOCK to clear and then sets the\\nbit with a non-atomic read-modify-write. Two senders can both see an\\nunlocked CSD, set the bit, overwrite the callback fields, and enqueue\\nthe same llist node. Re-adding a node that is already the queue head can\\nmake node-\u003enext point to itself, leaving the target CPU stuck walking\\ncall_single_queue. Later synchronous work, such as a TLB shootdown, can\\nthen remain queued and trigger soft-lockup warnings or panics.\\n\\nKeep the single csd_lock() implementation, but when CSD lock debugging is\\nenabled, acquire CSD_FLAG_LOCK with try_cmpxchg_acquire(). This makes the\\ndestination CPU CSD a real atomic lock in the only configuration where it\\ncan be shared by multiple remote senders, while preserving the existing\\nnon-debug fast path.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"kernel/smp.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"b0473dcd4b1d7e2e44947e7ac1820c73a268821a\",\"lessThan\":\"282d220bae5fbfc90cf0e3d5b5e42c00ad79f989\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"b0473dcd4b1d7e2e44947e7ac1820c73a268821a\",\"lessThan\":\"35551efb155e3b83445a6c3f66cb498d5efc182c\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"kernel/smp.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"7.1\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"7.1\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1.6\",\"lessThanOrEqual\":\"7.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.2\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/282d220bae5fbfc90cf0e3d5b5e42c00ad79f989\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/35551efb155e3b83445a6c3f66cb498d5efc182c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-25T01:20:45+00:00",
      "cve": "CVE-2026-68438",
      "id": "CVE-2026-68438",
      "initial_release_date": "2026-08-12T00:00:00+00:00",
      "product_status:known_not_affected": "276",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: smp: Make CSD lock acquisition atomic for debug mode",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-68438.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-13T01:27:50Z",
      "cve": "CVE-2026-68438",
      "id": "CVE-2026-68438",
      "initial_release_date": "2026-08-12T16:22:00Z",
      "product_status:known_not_affected": "296",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-68438",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-68438.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.