Linux Kernel up to 7.1.4 dmaengine dma_release_channel use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.48+

Summaryinfo

A vulnerability categorized as very critical has been discovered in Linux Kernel up to 7.1.4. This affects the function dma_release_channel of the component dmaengine. Such manipulation leads to use after free. This vulnerability is documented as CVE-2026-72476. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.4. It has been rated as very critical. Affected by this issue is the function dma_release_channel of the component dmaengine. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-72476 since 08/09/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch 444f96066937f3fdf0e79b53289cff223c7d638b/ab438a9efb9042c79d2f8db28a326d55feb8591f/9bdc8dce4068dadbdf7cf5ad6d4983e2afffedce/5876f38b67a309c00628942cb25679749b53b397/3b0240483dc977dbec4f3bc7a5383d4691ecb625/329ec20a86091d2a6e5b4fe507545e7d678a22a2/0bc191050c3253da8ef4bfaf157c44efed6e22cd/92f853f0645aebf1d05d333e97ab7c342ace1892 is able to eliminate this problem.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc1
Patch: 444f96066937f3fdf0e79b53289cff223c7d638b/ab438a9efb9042c79d2f8db28a326d55feb8591f/9bdc8dce4068dadbdf7cf5ad6d4983e2afffedce/5876f38b67a309c00628942cb25679749b53b397/3b0240483dc977dbec4f3bc7a5383d4691ecb625/329ec20a86091d2a6e5b4fe507545e7d678a22a2/0bc191050c3253da8ef4bfaf157c44efed6e22cd/92f853f0645aebf1d05d333e97ab7c342ace1892

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72476 (🔒)
GCVE (CVE): GCVE-0-2026-72476
GCVE (VulDB): GCVE-100-390986

Entryinfo

Created: 08/15/2026 16:48
Changes: 08/15/2026 16:48 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!