Skip to content

Commit 137d01d

Browse files
Al Virotorvalds
authored andcommitted
Fix missing sanity check in /dev/sg
What happens is that a write to /dev/sg is given a request with non-zero ->iovec_count combined with zero ->dxfer_len. Or with ->dxferp pointing to an array full of empty iovecs. Having write permission to /dev/sg shouldn't be equivalent to the ability to trigger BUG_ON() while holding spinlocks... Found by Dmitry Vyukov and syzkaller. [ The BUG_ON() got changed to a WARN_ON_ONCE(), but this fixes the underlying issue. - Linus ] Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Reported-by: Dmitry Vyukov <dvyukov@google.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Cc: stable@vger.kernel.org Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent fd3fc0b commit 137d01d

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

drivers/scsi/sg.c

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1753,6 +1753,10 @@ sg_start_req(Sg_request *srp, unsigned char *cmd)
17531753
return res;
17541754

17551755
iov_iter_truncate(&i, hp->dxfer_len);
1756+
if (!iov_iter_count(&i)) {
1757+
kfree(iov);
1758+
return -EINVAL;
1759+
}
17561760

17571761
res = blk_rq_map_user_iov(q, rq, md, &i, GFP_ATOMIC);
17581762
kfree(iov);

0 commit comments

Comments
 (0)