dma-buf: insert memory barrier before updating num_fences
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a590d0fdbaa56f482ff515e1040b6d9b1b200d63 · < 08680c4dadc6e736c75bc2409d833f03f9003c51| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dma-buf: insert memory barrier before updating num_fences
smp_store_mb() inserts memory barrier after storing operation. It is different with what the comment is originally aiming so Null pointer dereference can be happened if memory update is reordered.
From the CVE record · Linux
The Linux kernel's dma-buf code places a memory barrier after updating num_fences, rather than before it. If memory updates are reordered, a null pointer dereference can occur; the input does not specify how an attacker could trigger it or whether access or user interaction is required.
Anyone running the Linux kernel should check whether their version is affected; affected versions are not specified.