Answer in brief
CVE-2026-72149 records a Unknown severity vulnerability in dmaengine: tegra: Fix burst size calculation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <735951baa311c66353405dcac39375dd66441db0 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <8f0f5de1091119679d87f60dfb1acbff4b2a0ed3 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <a3b76b54e06d73166af4d1a284a0e0711889060c || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <7926c1e4be86379945fb5f168888ac4d2aaf6c91 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <4651df83b6c796daead3447e8fd874322918ee4f | 735951baa311c66353405dcac39375dd66441db0, 8f0f5de1091119679d87f60dfb1acbff4b2a0ed3, a3b76b54e06d73166af4d1a284a0e0711889060c, 7926c1e4be86379945fb5f168888ac4d2aaf6c91, 6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1, 4651df83b6c796daead3447e8fd874322918ee4f |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72149 records a Unknown severity vulnerability in dmaengine: tegra: Fix burst size calculation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <735951baa311c66353405dcac39375dd66441db0 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <8f0f5de1091119679d87f60dfb1acbff4b2a0ed3 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <a3b76b54e06d73166af4d1a284a0e0711889060c || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <7926c1e4be86379945fb5f168888ac4d2aaf6c91 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1 || >=ee17028009d49fffed8cc963455d33b1fd3f1d08 <4651df83b6c796daead3447e8fd874322918ee4f | 735951baa311c66353405dcac39375dd66441db0, 8f0f5de1091119679d87f60dfb1acbff4b2a0ed3, a3b76b54e06d73166af4d1a284a0e0711889060c, 7926c1e4be86379945fb5f168888ac4d2aaf6c91, 6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1, 4651df83b6c796daead3447e8fd874322918ee4f |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.