dma-buf: fix UAF in dma_buf_fd() tracepoint
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 7.0.12
- CVEs
- CVE-2026-63910
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 01:33 UTC · Revision 1
Source evidence
dma-buf: fix UAF in dma_buf_fd() tracepoint
core-osv · Original sourcePublished 19 Jul 2026, 14:55 UTC
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.
osv:CVE-2026-63910
Kernel
Fixed versions: 7.0.12
Complete source record
{
"id": "5d870429c06ba8f88fcdefdd4b0ff7173565a607eb35c3483cfc10e82da520be",
"url": "https://osv.dev/vulnerability/CVE-2026-63910",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "dma-buf: fix UAF in dma_buf_fd() tracepoint",
"summary": "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.",
"evidence": "osv:CVE-2026-63910",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.0.12",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-63910",
"aliases": [
"CVE-2026-63910"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "281a226314238e8adb08d11b765347687ffb38b9"
},
{
"fixed": "b569f86e2f8dbf6f11d31d3de794d22e18098b23"
},
{
"fixed": "ead6680f354f83966c796fc7f9463a3171789616"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-63910.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "7.0.0"
},
{
"fixed": "7.0.12"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-63910.json"
}
}
],
"modified": "2026-11-01T02:30:52.185561884Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/b569f86e2f8dbf6f11d31d3de794d22e18098b23",
"https://git.kernel.org/stable/c/ead6680f354f83966c796fc7f9463a3171789616",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63910.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-63910",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/63xxx/CVE-2026-63910.json"
}
},
"related_cves": [
{
"value": "CVE-2026-63910",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 521383,
"published_at": "2026-07-19T14:55:15.77+00:00"
}