GHSA-3G95-H923-8HFC
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
dmaengine: dw-edma: Serialize channel state checks
pause() and resume() read and update channel state without holding vc.lock, while the interrupt handlers update the same state under it. Take the same lock around those state checks so that request, status, and configured stay consistent.
For example, pause() can observe EDMA_ST_BUSY right before the interrupt handler completes the final descriptor and moves the channel to EDMA_ST_IDLE, and then record EDMA_REQ_PAUSE on an already idle channel. No further interrupt will acknowledge the request, and since issue_pending() requires EDMA_REQ_NONE, the channel is wedged for good: terminate_all() leaves the stale request behind, so even reconfiguring the channel does not recover it.
issue_pending() already runs under vc.lock, but it tests configured before taking it. Move that test under the lock as well, so configured, request, and status are evaluated as one channel-state snapshot.
{
"affected": [],
"aliases": [
"CVE-2026-93040"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:57Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: dw-edma: Serialize channel state checks\n\npause() and resume() read and update channel state without holding vc.lock,\nwhile the interrupt handlers update the same state under it. Take the same\nlock around those state checks so that request, status, and configured stay\nconsistent.\n\nFor example, pause() can observe EDMA_ST_BUSY right before the interrupt\nhandler completes the final descriptor and moves the channel to\nEDMA_ST_IDLE, and then record EDMA_REQ_PAUSE on an already idle channel. No\nfurther interrupt will acknowledge the request, and since issue_pending()\nrequires EDMA_REQ_NONE, the channel is wedged for good: terminate_all()\nleaves the stale request behind, so even reconfiguring the channel does not\nrecover it.\n\nissue_pending() already runs under vc.lock, but it tests configured before\ntaking it. Move that test under the lock as well, so configured, request,\nand status are evaluated as one channel-state snapshot.",
"id": "GHSA-3g95-h923-8hfc",
"modified": "2026-09-17T18:32:08Z",
"published": "2026-09-17T18:32:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93040"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2d76b91deeab973dd8a8c2ee587ce27f881de768"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3001cfcee30dcc81f8b3774319c12067f126e49a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6fc436e1500c5e4f0dde2a3dbadf6d898057be8f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b6293a8a38f4d5866ce1a264c138265a02e4c53a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/be0072af8ce6e9458cc586e0e8b41a251e7d4316"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/da16a02f0998a0d455ce6265b836b29ad92e6e58"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f7d1619f3e10c619b62c6cd6d95371b5c526c85a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fe0ffa0190e862ed71e8c1a476090f648c9cb7d9"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.