From: "Christian König" <christian.koenig@amd.com>
To: David Carlier <devnexen@gmail.com>,
Sumit Semwal <sumit.semwal@linaro.org>
Cc: gaoxiang17@xiaomi.com, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-kernel@vger.kernel.org,
syzbot+7f4987d0afb97dd090cb@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] dma-buf: fix UAF in dma_buf_fd() tracepoint
Date: Mon, 25 May 2026 20:54:55 +0200 [thread overview]
Message-ID: <ae16f5c2-c6d9-4274-9a27-f87bfe931b1f@amd.com> (raw)
In-Reply-To: <20260523181446.69525-1-devnexen@gmail.com>
On 5/23/26 20:14, David Carlier wrote:
> 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.
>
> Reported-by: syzbot+7f4987d0afb97dd090cb@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=7f4987d0afb97dd090cb
> Fixes: 281a22631423 ("dma-buf: add some tracepoints to debug.")
> Cc: stable@vger.kernel.org # 7.0.x
> Signed-off-by: David Carlier <devnexen@gmail.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/dma-buf/dma-buf.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> index 71f37544a5c6..d504c636dc29 100644
> --- a/drivers/dma-buf/dma-buf.c
> +++ b/drivers/dma-buf/dma-buf.c
> @@ -792,9 +792,13 @@ int dma_buf_fd(struct dma_buf *dmabuf, int flags)
> if (!dmabuf || !dmabuf->file)
> return -EINVAL;
>
> - fd = FD_ADD(flags, dmabuf->file);
> + fd = get_unused_fd_flags(flags);
> + if (fd < 0)
> + return fd;
> +
> DMA_BUF_TRACE(trace_dma_buf_fd, dmabuf, fd);
>
> + fd_install(fd, dmabuf->file);
> return fd;
> }
> EXPORT_SYMBOL_NS_GPL(dma_buf_fd, "DMA_BUF");
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-05-25 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 18:14 David Carlier
2026-05-25 18:54 ` Christian König [this message]
2026-05-28 14:53 ` Sumit Semwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae16f5c2-c6d9-4274-9a27-f87bfe931b1f@amd.com \
--to=christian.koenig@amd.com \
--cc=devnexen@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gaoxiang17@xiaomi.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=syzbot+7f4987d0afb97dd090cb@syzkaller.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®