Commit 0a16e24e authored by Jann Horn's avatar Jann Horn Committed by Vivek Kasireddy
Browse files

udmabuf: also check for F_SEAL_FUTURE_WRITE 



When F_SEAL_FUTURE_WRITE was introduced, it was overlooked that udmabuf
must reject memfds with this flag, just like ones with F_SEAL_WRITE.
Fix it by adding F_SEAL_FUTURE_WRITE to SEALS_DENIED.

Fixes: ab3948f5 ("mm/memfd: add an F_SEAL_FUTURE_WRITE seal to memfd")
Cc: stable@vger.kernel.org
Acked-by: default avatarVivek Kasireddy <vivek.kasireddy@intel.com>
Signed-off-by: default avatarJann Horn <jannh@google.com>
Reviewed-by: default avatarJoel Fernandes (Google) <joel@joelfernandes.org>
Signed-off-by: default avatarVivek Kasireddy <vivek.kasireddy@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20241204-udmabuf-fixes-v2-2-23887289de1c@google.com
parent 9cb189a8

drivers/dma-buf/udmabuf.c

+1 −1
Original line number Diff line number Diff line
@@ -297,7 +297,7 @@ static const struct dma_buf_ops udmabuf_ops = { 
};



#define SEALS_WANTED (F_SEAL_SHRINK)

#define SEALS_DENIED (F_SEAL_WRITE)

#define SEALS_DENIED (F_SEAL_WRITE|F_SEAL_FUTURE_WRITE)



static int check_memfd_seals(struct file *memfd)

{