CVE-2026-72149

dmaengine: tegra: Fix burst size calculation

HIGH
7.5
CVSS Score
Published: August 15, 2026 at 05:53 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.19ee17028009d49fffed8cc963455d33b1fd3f1d08
Vendor states this is fixed in 4651df83b6c796daead3447e8fd874322918ee4f (fixed)
Vendor states this is fixed in 6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1 (fixed)
Vendor states this is fixed in 735951baa311c66353405dcac39375dd66441db0 (fixed)
Vendor states this is fixed in 7926c1e4be86379945fb5f168888ac4d2aaf6c91 (fixed)
Vendor states this is fixed in 8f0f5de1091119679d87f60dfb1acbff4b2a0ed3 (fixed)
Vendor states this is fixed in a3b76b54e06d73166af4d1a284a0e0711889060c (fixed)
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card