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-72149dmaengine: tegra: Fix burst size calculation

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: tegra: Fix burst size calculation Currently, the Tegra GPC DMA hardware requires the transfer length to be a multiple of the max burst size configured for the channel. When a client requests a transfer where the length is not evenly divisible by the configured max burst size, the DMA hangs with partial burst at the end. Fix this by reducing the burst size to the largest power-of-2 value that evenly divides the transfer length. For example, a 40-byte transfer with a 16-byte max burst will now use an 8-byte burst (40 / 8 = 5 complete bursts) instead of causing a hang. This issue was observed with the PL011 UART driver where TX DMA transfers of arbitrary lengths were stuck.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 months 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-72149, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.65% · top 48% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ee17028009d49fffed8cc963455d33b1fd3f1d08 – < 735951baa311c66353405dcac39375dd66441db0
    • affected ee17028009d49fffed8cc963455d33b1fd3f1d08 – < 8f0f5de1091119679d87f60dfb1acbff4b2a0ed3
    • affected ee17028009d49fffed8cc963455d33b1fd3f1d08 – < a3b76b54e06d73166af4d1a284a0e0711889060c
    • affected ee17028009d49fffed8cc963455d33b1fd3f1d08 – < 7926c1e4be86379945fb5f168888ac4d2aaf6c91
    • affected ee17028009d49fffed8cc963455d33b1fd3f1d08 – < 6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1
    • affected ee17028009d49fffed8cc963455d33b1fd3f1d08 – < 4651df83b6c796daead3447e8fd874322918ee4f
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .