In the Linux kernel, the following vulnerability has been resolved: dma-buf: fix UAF in dma_buf_fd() tracepoint Once FD_ADD() returns, the fd is… (CVE-2026-63910)
A use-after-free (UAF) vulnerability in the Linux kernel's dma-buf subsystem was resolved. The issue occurs in the dma_buf_fd() tracepoint where a file descriptor (fd) can be closed by another thread after FD_ADD() returns but before the tracepoint runs, leading to a use-after-free when the tracepoint dereferences a freed dma_buf. The fix involves splitting FD_ADD() into get_unused_fd_flags() and fd_install(), placing the tracepoint between them to prevent the race condition and ensure the dma_buf remains valid during tracing.
AI Analysis
Technical Summary
The Linux kernel dma-buf subsystem had a use-after-free vulnerability in the dma_buf_fd() tracepoint. After FD_ADD() returns, the fd is live in the file descriptor table, but a concurrent thread can close it before the tracepoint executes. This close operation frees the dma_buf, causing the tracepoint to dereference a freed object, resulting in a slab use-after-free. The fix reverts the FD_ADD() conversion and splits it into two steps, inserting the tracepoint between them. This approach reserves the fdtable slot with a NULL file pointer during the race window, causing a racing close() to fail safely without freeing the dma_buf, thus preventing the use-after-free.
Potential Impact
This vulnerability could lead to kernel memory corruption due to use-after-free, potentially causing system instability or crashes. No information about exploitation in the wild is available. The impact is limited to kernel memory safety and tracepoint operations related to dma-buf file descriptors.
Mitigation Recommendations
A fix has been implemented in the Linux kernel that reverts the unsafe FD_ADD() usage and inserts the tracepoint safely between get_unused_fd_flags() and fd_install(). Users should update to the fixed kernel versions once available. Patch status is not yet confirmed from vendor advisories; check the official Linux kernel security advisories for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: dma-buf: fix UAF in dma_buf_fd() tracepoint Once FD_ADD() returns, the fd is… (CVE-2026-63910)
Description
A use-after-free (UAF) vulnerability in the Linux kernel's dma-buf subsystem was resolved. The issue occurs in the dma_buf_fd() tracepoint where a file descriptor (fd) can be closed by another thread after FD_ADD() returns but before the tracepoint runs, leading to a use-after-free when the tracepoint dereferences a freed dma_buf. The fix involves splitting FD_ADD() into get_unused_fd_flags() and fd_install(), placing the tracepoint between them to prevent the race condition and ensure the dma_buf remains valid during tracing.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel dma-buf subsystem had a use-after-free vulnerability in the dma_buf_fd() tracepoint. After FD_ADD() returns, the fd is live in the file descriptor table, but a concurrent thread can close it before the tracepoint executes. This close operation frees the dma_buf, causing the tracepoint to dereference a freed object, resulting in a slab use-after-free. The fix reverts the FD_ADD() conversion and splits it into two steps, inserting the tracepoint between them. This approach reserves the fdtable slot with a NULL file pointer during the race window, causing a racing close() to fail safely without freeing the dma_buf, thus preventing the use-after-free.
Potential Impact
This vulnerability could lead to kernel memory corruption due to use-after-free, potentially causing system instability or crashes. No information about exploitation in the wild is available. The impact is limited to kernel memory safety and tracepoint operations related to dma-buf file descriptors.
Mitigation Recommendations
A fix has been implemented in the Linux kernel that reverts the unsafe FD_ADD() usage and inserts the tracepoint safely between get_unused_fd_flags() and fd_install(). Users should update to the fixed kernel versions once available. Patch status is not yet confirmed from vendor advisories; check the official Linux kernel security advisories for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-cwcv-9vv2-wx88
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63910"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ab2a4a8d598912f8f6
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:09:26 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.