CVE-2026-72149 Linux CVE debrief

Who should care

Users of Linux kernel systems, particularly those using the Tegra GPC DMA hardware, should be aware of this vulnerability and take steps to patch or mitigate it. Affected operator teams, platform administrators, vulnerability management teams, and security teams should review system configurations and ensure that the Linux kernel is up-to-date. They should also consider implementing compensating controls, such as monitoring system activity and restricting access to sensitive areas. Additionally, they should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. This vulnerability affects the Linux kernel and could potentially lead to a denial-of-service (DoS) or other unspecified impacts. Users of affected systems should prioritize patching and review compensating controls for exposed systems while remediation is scheduled and verified. They should also check relevant monitoring, detection, and logs for exposed assets that need extra review and track exceptions, retest remediated assets, and close the item only after evidence is documented. The CVE-2026-72149 vulnerability is related to the Linux kernel's dmaengine: tegra component. The fix involves reducing the burst size to the largest power-of-2 value that evenly divides the transfer length. The issue arises when a client requests a transfer where the length is not evenly divisible by the configured max burst size, causing the DMA to hang with a partial burst at the end. This vulnerability has been resolved by fixing the burst size calculation in the Tegra GPC DMA hardware. Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Review compensating controls for exposed systems while remediation is scheduled and verified. Check relevant monitoring, detection, and logs for exposed assets that need extra review. Track exceptions, retest remediated assets, and close the item only after evidence is documented. The CVE record was published on 2026-08-15T06:21:32.610Z and has not been modified since then.

Technical summary

The CVE-2026-72149 vulnerability is related to the Linux kernel's dmaengine: tegra component. This vulnerability has been resolved by fixing the burst size calculation in the Tegra GPC DMA hardware. The issue arises when a client requests a transfer where the length is not evenly divisible by the configured max burst size, causing the DMA to hang with a partial burst at the end. The fix involves reducing the burst size to the largest power-of-2 value that evenly divides the transfer length.

Defensive priority

This vulnerability affects the Linux kernel and could potentially lead to a denial-of-service (DoS) or other unspecified impacts. Users of affected systems should prioritize patching.

Recommended defensive actions

• Apply patches or updates provided by the Linux kernel maintainers to address the dmaengine: tegra vulnerability.
• Review system configurations and ensure that the Linux kernel is up-to-date.
• Consider implementing compensating controls, such as monitoring system activity and restricting access to sensitive areas.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE-2026-72149 vulnerability is related to the Linux kernel's dmaengine: tegra component. According to the NVD, this vulnerability has been resolved by fixing the burst size calculation in the Tegra GPC DMA hardware. The issue arises when a client requests a transfer where the length is not evenly divisible by the configured max burst size, causing the DMA to hang with a partial burst at the end. The fix involves reducing the burst size to the largest power-of-2 value that evenly divides the transfer length.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.