Answer in brief
CVE-2026-72093 records a High severity (CVSS 7.8) vulnerability in accel/amdxdna: Fix use-after-free in amdxdna_gem_dmabuf_mmap(). 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.
CVSS is 7.8. 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 | >=e486147c912f653ef4b60a6c7dbd4168a4c56a9f <4e370b5289624f46a356dcc94f9f87025eaa6036 || >=e486147c912f653ef4b60a6c7dbd4168a4c56a9f <5da885c39baa70f570a8be35a78e85a351f33918 || >=e486147c912f653ef4b60a6c7dbd4168a4c56a9f <63bbf9ac5dde2ba85e7b39d0a0b7d540e6252ba4 | 4e370b5289624f46a356dcc94f9f87025eaa6036, 5da885c39baa70f570a8be35a78e85a351f33918, 63bbf9ac5dde2ba85e7b39d0a0b7d540e6252ba4 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 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: accel/amdxdna: Fix use-after-free in amdxdna_gem_dmabuf_mmap() When vm_insert_pages() fails, the error path calls vma->vm_ops->close(vma) which internally calls drm_gem_vm_close() → drm_gem_object_put(), releasing the GEM object reference acquired at the start of the function. However, the close_vma label then falls through to put_obj, which calls drm_gem_object_put() a second time on the same object. If the first put releases the last reference, the object is freed and the second put accesses freed memory, causing a use-after-free. Fix by returning directly from close_vma instead of falling through to put_obj, since the close handler already performs all necessary cleanup including the object put.
Quoted source text, attributed separately from HOL analysis.