Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2026-80902

dmaengine: sun6i-dma: Fix reclaim descriptors while terminating DMA

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (10 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < bb87440561eb72b47a2b848b5373b86433b247e6
    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < 004a7a02982bed0a727a4ac7be400f00f353e7a2
    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < b150f603083cc8b72b0cbf13ec3e91f85b4390a0
    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < 27806fe7b9701af0963dcd510e30e7d0cc314c43
    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < 1ccc5c059d067c5358682ad5352e7d7e9239ed9b
    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < 9086b488f2737d5dcee86852b83f2059f1cdfabf
    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < d4ba6aa65fcd797152d3aebd428a7b2da49cd5eb
    • affected 555859308723d8d5b828304f5eb9281143fd86b5 – < ab1150115e68a46b687eb38c1ab92782018c9f2c
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80902 badge
[![CVE-2026-80902](https://cveledger.app/badge/CVE-2026-80902.svg)](https://cveledger.app/cve/CVE-2026-80902)

Record last updated .