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

14 results

Back

CVE-2026-80737serial: amba-pl011: synchronize DMA teardown

Description

In the Linux kernel, the following vulnerability has been resolved: serial: amba-pl011: synchronize DMA teardown dmaengine_terminate_all() does not wait for a running callback, so the TX callback can still touch the TX buffer after it is freed. The RX poll timer reads the RX buffers without the port lock. Switch to dmaengine_terminate_sync() and delete the RX timer before freeing the buffers.

Timeline

  1. ID reserved

    By Linux

  2. · 8 days later

    Published

  3. · 43 days later

    Record updated

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

CVSS scores of CVE-2026-80737, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < a38fae9d212e2d3ed5e9ec0ef773f8c0a27fb76e
    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < 44bd0ecc3444882d08ecfbc2b2418d2f463d3186
    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < f70c9d4fba46463a5b1c7b3ee9ee3b40c90dac03
    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < c8c8e895f65fbf71ea6224e27cf8dab91b776e0d
    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < 9f6989e477f03a4721d34bb4b09b17accd40283e
    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < 5974cb66681eac367107b05924744d7e3b49d41c
    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < fdfb46c387241b4eddd36d746793764413285913
    • affected ead76f329f777c7301e0a5456a0a1c7a081570bd – < 440915499231e9db1c361aa45bb702e8fd3b4a32
  • Linux · Linux

    • affected 2.6.39
    • unaffected < 2.6.39
    • unaffected 5.10.267 – ≤ 5.10.*
    • unaffected 5.15.218 – ≤ 5.15.*
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .