CVE-2026-72094 (GCVE-0-2026-72094)
Vulnerability from cvelistv5
Published
2026-08-15 05:52
Modified
2026-08-17 05:08
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
dma-buf: dma-fence: Fix potential NULL pointer dereference
The commit mentioned in the fixes tag below introduced a mechanism
through which fence producers can fully decouple from fence consumers.
This, desirable, mechanism is based on the fence's signaled-bit as the
"decoupling point".
A sophisticated interaction between RCU and atomic instructions attempts
to ensure that fence consumers can still interact with fence producers
through the dma_fence_ops (callback pointers into the producer).
This is the desired behavior: to check for decoupling, the signaled-bit
is first checked. If it's not yet signaled, RCU ensures that the ops
pointer cannot yet be NULL.
Hereby, dma_fence_signal_timestamp_locked() first sets the signaled-bit,
and then sets the ops pointer to NULL. Readers first load the ops
pointer, and then check through the signaled-bit whether the pointer can
legally be accessed.
These set and load operations could occur out of order on weakly ordered
platforms. This problem can be solved very elegantly by using the ops
pointer itself as the synchronization point. The pointer is either NULL,
or cannot become NULL while it is being used thanks to RCU.
Replace the signaled-bit check in dma_fence_timeline_name() and
dma_fence_driver_name().
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/dma-buf/dma-fence.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "15ecfdf0ef6f6d874d0a26690d300857b39ebfd0",
"status": "affected",
"version": "f4cc3ab824d6772a48ca9d9c74ac623b3309985d",
"versionType": "git"
},
{
"lessThan": "035219a760edb35ae9a9e96beba7f122e26a997b",
"status": "affected",
"version": "f4cc3ab824d6772a48ca9d9c74ac623b3309985d",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/dma-buf/dma-fence.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.5",
"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.5",
"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\ndma-buf: dma-fence: Fix potential NULL pointer dereference\n\nThe commit mentioned in the fixes tag below introduced a mechanism\nthrough which fence producers can fully decouple from fence consumers.\nThis, desirable, mechanism is based on the fence\u0027s signaled-bit as the\n\"decoupling point\".\n\nA sophisticated interaction between RCU and atomic instructions attempts\nto ensure that fence consumers can still interact with fence producers\nthrough the dma_fence_ops (callback pointers into the producer).\n\nThis is the desired behavior: to check for decoupling, the signaled-bit\nis first checked. If it\u0027s not yet signaled, RCU ensures that the ops\npointer cannot yet be NULL.\n\nHereby, dma_fence_signal_timestamp_locked() first sets the signaled-bit,\nand then sets the ops pointer to NULL. Readers first load the ops\npointer, and then check through the signaled-bit whether the pointer can\nlegally be accessed.\n\nThese set and load operations could occur out of order on weakly ordered\nplatforms. This problem can be solved very elegantly by using the ops\npointer itself as the synchronization point. The pointer is either NULL,\nor cannot become NULL while it is being used thanks to RCU.\n\nReplace the signaled-bit check in dma_fence_timeline_name() and\ndma_fence_driver_name()."
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:08:05.562Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/15ecfdf0ef6f6d874d0a26690d300857b39ebfd0"
},
{
"url": "https://git.kernel.org/stable/c/035219a760edb35ae9a9e96beba7f122e26a997b"
}
],
"title": "dma-buf: dma-fence: Fix potential NULL pointer dereference",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72094",
"datePublished": "2026-08-15T05:52:40.632Z",
"dateReserved": "2026-08-09T03:40:39.905Z",
"dateUpdated": "2026-08-17T05:08:05.562Z",
"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…