Linux Kernel up to 7.1.4 dmaengine initialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.2$0-$5k0.00

Summaryinfo

A vulnerability labeled as problematic has been found in Linux Kernel up to 6.1.177/6.6.144/6.12.96/6.18.39/7.1.4. This affects an unknown part of the component dmaengine. Executing a manipulation can lead to initialization. This vulnerability appears as CVE-2026-72149. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.1.177/6.6.144/6.12.96/6.18.39/7.1.4 and classified as problematic. This vulnerability affects an unknown part of the component dmaengine. The manipulation with an unknown input leads to a initialization vulnerability. The CWE definition for the vulnerability is CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. As an impact it is known to affect availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-72149 since 08/09/2026. The exploitation appears to be easy. The attack needs to be approached locally. Additional levels of successful authentication are necessary for exploitation. There are neither technical details nor an exploit publicly available.

Upgrading to version 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch 735951baa311c66353405dcac39375dd66441db0/8f0f5de1091119679d87f60dfb1acbff4b2a0ed3/a3b76b54e06d73166af4d1a284a0e0711889060c/7926c1e4be86379945fb5f168888ac4d2aaf6c91/6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1/4651df83b6c796daead3447e8fd874322918ee4f is able to eliminate this problem.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc1
Patch: 735951baa311c66353405dcac39375dd66441db0/8f0f5de1091119679d87f60dfb1acbff4b2a0ed3/a3b76b54e06d73166af4d1a284a0e0711889060c/7926c1e4be86379945fb5f168888ac4d2aaf6c91/6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1/4651df83b6c796daead3447e8fd874322918ee4f

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72149 (🔒)
GCVE (CVE): GCVE-0-2026-72149
GCVE (VulDB): GCVE-100-390568

Entryinfo

Created: 08/15/2026 12:52
Changes: 08/15/2026 12:52 (58)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!