CVE-2026-63910
Last modified
CVE-2026-63910 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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 live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf->name_lock -- slab-use-after-free. Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
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 live in the file descriptor table and a thread sharing that table can close() it before DMA_BUF_TRACE() runs. The close drops the last reference, __fput() frees the dma_buf, and the tracepoint then dereferences dmabuf to take dmabuf->name_lock -- slab-use-after-free. Split FD_ADD() back into get_unused_fd_flags() + fd_install() and emit the tracepoint between them. While the fdtable slot is reserved with a NULL file pointer, a racing close() returns -EBADF without entering __fput(), so the dma_buf stays alive across the trace. Same approach as commit 2d76319c4cbb ("dma-buf: fix UAF in dma_buf_put() tracepoint"). This undoes the FD_ADD() conversion done in commit 34dfce523c90 ("dma: convert dma_buf_fd() to FD_ADD()"); FD_ADD() has no place to hook the tracepoint safely.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 281a226314238e8adb08d11b765347687ffb38b9, < b569f86e2f8dbf6f11d31d3de794d22e18098b23; >= 281a226314238e8adb08d11b765347687ffb38b9, < ead6680f354f83966c796fc7f9463a3171789616 |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-63910?
How severe is CVE-2026-63910?
How do I fix CVE-2026-63910?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63905In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63906In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-63907In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63908In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63909In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-6391The Sentence To SEO (keywords, description and tags) plugin …6.1
- CVE-2026-63911In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63912In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63913In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-63914In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-63915In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63916In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-63910?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
