CVE-2025-71162: dmaengine: tegra-adma: Fix use-after-free
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2efd07a7c36949e6fa36a69183df24d368bf9e96, 59cb421b0902fbef2b9512ae8ba198a20f26b41f, 5f8d1d66a952d0396671e1f21ff8127a4d14fb4e.
Low priority for now. Upgrade to Linux Linux 2efd07a7c36949e6fa36a69183df24d368bf9e96, 59cb421b0902fbef2b9512ae8ba198a20f26b41f, 5f8d1d66a952d0396671e1f21ff8127a4d14fb4e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: dmaengine: tegra-adma: Fix use-after-free A use-after-free bug exists in the Tegra ADMA driver when audio streams are terminated, particularly during XRUN conditions. The issue occurs when the DMA buffer is freed by tegra_adma_terminate_all() before the vchan completion tasklet finishes accessing it. The race condition follows this sequence: 1. DMA transfer completes, triggering an interrupt that schedules the completion tasklet (tasklet has not executed yet) 2. Audio playback stops, calling tegra_adma_terminate_all() which frees the DMA buffer memory via kfree() 3. The scheduled tasklet finally executes, calling vchan_complete() which attempts to access the already-freed memory Since tasklets can execute at any time after being scheduled, there is no guarantee that the buffer will remain valid when vchan_complete() runs. Fix this by properly synchronizing the virtual channel completion: - Calling vchan_terminate_vdesc() in tegra_adma_stop() to mark the descriptors as terminated instead of freeing the descriptor. - Add the callback tegra_adma_synchronize() that calls vchan_synchronize() which kills any pending tasklets and frees any terminated descriptors. Crash logs: [ 337.427523] BUG: KASAN: use-after-free in vchan_complete+0x124/0x3b0 [ 337.427544] Read of size 8 at addr ffff000132055428 by task swapper/0/0 [ 337.427562] Call trace: [ 337.427564] dump_backtrace+0x0/0x320 [ 337.427571] show_stack+0x20/0x30 [ 337.427575] dump_stack_lvl+0x68/0x84 [ 337.427584] print_address_description.constprop.0+0x74/0x2b8 [ 337.427590] kasan_report+0x1f4/0x210 [ 337.427598] __asan_load8+0xa0/0xd0 [ 337.427603] vchan_complete+0x124/0x3b0 [ 337.427609] tasklet_action_common.constprop.0+0x190/0x1d0 [ 337.427617] tasklet_action+0x30/0x40 [ 337.427623] __do_softirq+0x1a0/0x5c4 [ 337.427628] irq_exit+0x110/0x140 [ 337.427633] handle_domain_irq+0xa4/0xe0 [ 337.427640] gic_handle_irq+0x64/0x160 [ 337.427644] call_on_irq_stack+0x20/0x4c [ 337.427649] do_interrupt_handler+0x7c/0x90 [ 337.427654] el1_interrupt+0x30/0x80 [ 337.427659] el1h_64_irq_handler+0x18/0x30 [ 337.427663] el1h_64_irq+0x7c/0x80 [ 337.427667] cpuidle_enter_state+0xe4/0x540 [ 337.427674] cpuidle_enter+0x54/0x80 [ 337.427679] do_idle+0x2e0/0x380 [ 337.427685] cpu_startup_entry+0x2c/0x70 [ 337.427690] rest_init+0x114/0x130 [ 337.427695] arch_call_rest_init+0x18/0x24 [ 337.427702] start_kernel+0x380/0x3b4 [ 337.427706] __primary_switched+0xc0/0xc8
- Published
- Jan 25, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.7affected
- f46b195799b5cb05338e7c44cb3617eacb56d755 and later · before 5f8d1d66a952d0396671e1f21ff8127a4d14fb4eaffected · git
- f46b195799b5cb05338e7c44cb3617eacb56d755 and later · before 76992310f80776b4d1f7f8915f59b92883a3e44caffected · git
- f46b195799b5cb05338e7c44cb3617eacb56d755 and later · before ae3eed72de682ddbba507ed2d6b848c21a6b721eaffected · git
- f46b195799b5cb05338e7c44cb3617eacb56d755 and later · before 59cb421b0902fbef2b9512ae8ba198a20f26b41faffected · git
- f46b195799b5cb05338e7c44cb3617eacb56d755 and later · before cb2c9c4bb1322cc3c9984ad17db8cdd2663879caaffected · git
- f46b195799b5cb05338e7c44cb3617eacb56d755 and later · before be655c3736b3546f39bc8116ffbf2a3b6cac96c4affected · git
- f46b195799b5cb05338e7c44cb3617eacb56d755 and later · before 2efd07a7c36949e6fa36a69183df24d368bf9e96affected · git
- before 4.7not affected · semver
- 5.10.249 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.7 and later · before 5.10.249
- linux linux kernel5.11 and later · before 5.15.199
- linux linux kernel5.16 and later · before 6.1.162
- linux linux kernel6.2 and later · before 6.6.122
- linux linux kernel6.7 and later · before 6.12.67
- linux linux kernel6.13 and later · before 6.18.7
- linux linux kernel6.19
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.8-1 | 6.18.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23006Jan 25, 2026 · ASoC: tlv320adcx140: fix null pointer22Monitor
- ← EarlierCVE-2026-23012Jan 25, 2026 · mm/damon/core: remove call_control in inactive contexts31Monitor
- Later →CVE-2025-71163Jan 25, 2026 · dmaengine: idxd: fix device leaks on compat bind and unbind22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2efd07a7c36949e6fa36a69183df24d368bf9e96 | Vendor (CNA) |
| Linux Linux | 59cb421b0902fbef2b9512ae8ba198a20f26b41f | Vendor (CNA) |
| Linux Linux | 5f8d1d66a952d0396671e1f21ff8127a4d14fb4e | Vendor (CNA) |
| Linux Linux | 76992310f80776b4d1f7f8915f59b92883a3e44c | Vendor (CNA) |
| Linux Linux | ae3eed72de682ddbba507ed2d6b848c21a6b721e | Vendor (CNA) |
| Linux Linux | be655c3736b3546f39bc8116ffbf2a3b6cac96c4 | Vendor (CNA) |
| Linux Linux | cb2c9c4bb1322cc3c9984ad17db8cdd2663879ca | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/59cb421b0902fbef2b9512ae8ba198a20f26b41f
- git.kernel.org/stable/c/5f8d1d66a952d0396671e1f21ff8127a4d14fb4e
- git.kernel.org/stable/c/76992310f80776b4d1f7f8915f59b92883a3e44c
- git.kernel.org/stable/c/ae3eed72de682ddbba507ed2d6b848c21a6b721e
- git.kernel.org/stable/c/be655c3736b3546f39bc8116ffbf2a3b6cac96c4
- git.kernel.org/stable/c/cb2c9c4bb1322cc3c9984ad17db8cdd2663879ca
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.