Answer in brief
CVE-2026-72476 records a Unknown severity vulnerability in dmaengine: Fix possible use after free. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72476 records a Unknown severity vulnerability in dmaengine: Fix possible use after free. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <444f96066937f3fdf0e79b53289cff223c7d638b || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <ab438a9efb9042c79d2f8db28a326d55feb8591f || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <9bdc8dce4068dadbdf7cf5ad6d4983e2afffedce || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <5876f38b67a309c00628942cb25679749b53b397 || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <3b0240483dc977dbec4f3bc7a5383d4691ecb625 || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <329ec20a86091d2a6e5b4fe507545e7d678a22a2 || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <0bc191050c3253da8ef4bfaf157c44efed6e22cd || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <92f853f0645aebf1d05d333e97ab7c342ace1892 | 444f96066937f3fdf0e79b53289cff223c7d638b, ab438a9efb9042c79d2f8db28a326d55feb8591f, 9bdc8dce4068dadbdf7cf5ad6d4983e2afffedce, 5876f38b67a309c00628942cb25679749b53b397, 3b0240483dc977dbec4f3bc7a5383d4691ecb625, 329ec20a86091d2a6e5b4fe507545e7d678a22a2, 0bc191050c3253da8ef4bfaf157c44efed6e22cd, 92f853f0645aebf1d05d333e97ab7c342ace1892 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: dmaengine: Fix possible use after free In dma_release_channel(), check chan->device->privatecnt after call dma_chan_put(). However, dma_chan_put() call dma_device_put() which could release the last reference of the device if the DMA provider is already gone and hence free it. Fixes it by moving dma_chan_put() after the check.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <444f96066937f3fdf0e79b53289cff223c7d638b || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <ab438a9efb9042c79d2f8db28a326d55feb8591f || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <9bdc8dce4068dadbdf7cf5ad6d4983e2afffedce || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <5876f38b67a309c00628942cb25679749b53b397 || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <3b0240483dc977dbec4f3bc7a5383d4691ecb625 || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <329ec20a86091d2a6e5b4fe507545e7d678a22a2 || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <0bc191050c3253da8ef4bfaf157c44efed6e22cd || >=0f571515c332e00b3515dbe0859ceaa30ab66e00 <92f853f0645aebf1d05d333e97ab7c342ace1892 | 444f96066937f3fdf0e79b53289cff223c7d638b, ab438a9efb9042c79d2f8db28a326d55feb8591f, 9bdc8dce4068dadbdf7cf5ad6d4983e2afffedce, 5876f38b67a309c00628942cb25679749b53b397, 3b0240483dc977dbec4f3bc7a5383d4691ecb625, 329ec20a86091d2a6e5b4fe507545e7d678a22a2, 0bc191050c3253da8ef4bfaf157c44efed6e22cd, 92f853f0645aebf1d05d333e97ab7c342ace1892 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: dmaengine: Fix possible use after free In dma_release_channel(), check chan->device->privatecnt after call dma_chan_put(). However, dma_chan_put() call dma_device_put() which could release the last reference of the device if the DMA provider is already gone and hence free it. Fixes it by moving dma_chan_put() after the check.
Quoted source text, attributed separately from HOL analysis.