CVE-2026-68438 (GCVE-0-2026-68438)
Vulnerability from cvelistv5
Published
2026-08-12 00:07
Modified
2026-08-17 05:05
Severity ?
VLAI Severity ?
EPSS score ?
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.
References
Impacted products
{
"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"
}
Loading…
Loading…
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.
Loading…
Loading…