Linux Kernel up to 7.1.7 sun6i-dma vchan_terminate_vdesc memory leak

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.
3.3$0-$5k0.41

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 7.1.7. This affects the function vchan_terminate_vdesc of the component sun6i-dma. Performing a manipulation results in memory leak. This vulnerability is cataloged as CVE-2026-80902. The attack must be initiated from a local position. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 7.1.7. This affects the function vchan_terminate_vdesc of the component sun6i-dma. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: dmaengine: sun6i-dma: Fix reclaim descriptors while terminating DMA When terminating DMA transfers, active descriptors are not properly reclaimed. Only cyclic descriptors were handled, leaving non-cyclic descriptors and their LLI chains to be permanently leaked. Fix by using vchan_terminate_vdesc() which handles both cyclic and non-cyclic descriptors by adding them to desc_terminated queue for proper cleanup. Add pchan->desc != pchan->done check to prevent double-adding completed descriptors, which would corrupt the list.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-80902 since 08/26/2026. The exploitability is told to be easy. Attacking locally is a requirement. Additional levels of successful authentication are needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch bb87440561eb72b47a2b848b5373b86433b247e6/004a7a02982bed0a727a4ac7be400f00f353e7a2/b150f603083cc8b72b0cbf13ec3e91f85b4390a0/27806fe7b9701af0963dcd510e30e7d0cc314c43/1ccc5c059d067c5358682ad5352e7d7e9239ed9b/9086b488f2737d5dcee86852b83f2059f1cdfabf/d4ba6aa65fcd797152d3aebd428a7b2da49cd5eb/ab1150115e68a46b687eb38c1ab92782018c9f2c is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.4
VulDB Meta Temp Score: 3.3

VulDB Base Score: 3.4
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

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.265/5.15.216/6.1.183/6.6.151/6.12.103/6.18.44/7.1.8
Patch: bb87440561eb72b47a2b848b5373b86433b247e6/004a7a02982bed0a727a4ac7be400f00f353e7a2/b150f603083cc8b72b0cbf13ec3e91f85b4390a0/27806fe7b9701af0963dcd510e30e7d0cc314c43/1ccc5c059d067c5358682ad5352e7d7e9239ed9b/9086b488f2737d5dcee86852b83f2059f1cdfabf/d4ba6aa65fcd797152d3aebd428a7b2da49cd5eb/ab1150115e68a46b687eb38c1ab92782018c9f2c

Timelineinfo

08/26/2026 CVE reserved
09/04/2026 +9 days Advisory disclosed
09/04/2026 +0 days VulDB entry created
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80902 (🔒)
GCVE (CVE): GCVE-0-2026-80902
GCVE (VulDB): GCVE-100-399099

Entryinfo

Created: 09/04/2026 19:37
Changes: 09/04/2026 19:37 (59)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!