From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B394872622 for ; Sat, 18 Apr 2026 17:18:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776532697; cv=none; b=VplOqKEXavPMNDta7FXf74IUOv6ulMAxO5LVH4e+AXAEePqY7A2lYMOKdqVFQB1jkLxHG0qMwGusu7JslAeuK/SR9UvUeVUsgdGBXrzFU6RLs3pkVFIhqHiD2Q2CjtVpFV4NUYh+c0t2Rwk2ywCcRqXHsdGRZaxqoZQLvC+A9gA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776532697; c=relaxed/simple; bh=Gu8eeLkTFWApFqN/pJd9fwrbx7MTr5fi31lrqj7DrzE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=N6iFa+Y1nUn9f2dlcn2eE7GRTdBNmELneMCEhrymMJKltseOuPnlodmLrf4PQYo1FKtV5VerIbkgfthYbzLy+YfRERcGCVhXmHpce3/EftBcKKQNSZnuZUN0vytsFIQilEBae2hB1TG9suHcZmEHrPgXybGRgv7mPHrjumUkzvI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=Xny3aRKl; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b=JYmgwv/g; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Xny3aRKl"; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b="JYmgwv/g" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1776532693; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lg1X2HhPqDML25PLvODz8bdExDJw0JHd2gmFAwXJGFI=; b=Xny3aRKlmc55ZjMGwvPrDAX9H4sovB45D3RHjAGYGdyRpKsGRQwHkXqz1Fz1YEGrNQxc0t cKb44yqeWH8soT8gMCePzXVjFk++96jdUL8gDZkGxxACGpFb11pCN7UbW4OrALyy963rRw PsbQzRZvPbn6LnI0PWM1toxyiwt2dys= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-607-_iDcd1RxOeq1rNfUcGPvZg-1; Sat, 18 Apr 2026 13:18:12 -0400 X-MC-Unique: _iDcd1RxOeq1rNfUcGPvZg-1 X-Mimecast-MFC-AGG-ID: _iDcd1RxOeq1rNfUcGPvZg_1776532691 Received: by mail-wm1-f71.google.com with SMTP id 5b1f17b1804b1-488c16958e9so12089235e9.1 for ; Sat, 18 Apr 2026 10:18:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=google; t=1776532691; x=1777137491; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=lg1X2HhPqDML25PLvODz8bdExDJw0JHd2gmFAwXJGFI=; b=JYmgwv/gyIF7qHnmlAieciyXmOfKbqLwSjd/KlCYhCSL/9CTaQpdT9WU4aUV9E4RoP EcowiG0N5BYK/pM3KqWj8DVxROPiw4732ZdsdTbC2VdjpVq5HGYClkS7k0OkuPzWbrO4 qlNHwYUCyCUftL6ugDfx85/WuqeUt/aNMDwkRa7kGX4jFK40iF2nQi6WuYKoR+0NAIGS PFKEXlmm0emr6Y88KpEHYfC4TUiHqDvNSxdIN2x5Jc5CF08pWIzHYAQyxK3t2PVrXPJM X5pLfxLUPiApeqhEQVFUrMIHYcNJECtMFfvhaIoFy5PEHCEh9Fnxm7HIbVeGAIxzZhUn g1Vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776532691; x=1777137491; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=lg1X2HhPqDML25PLvODz8bdExDJw0JHd2gmFAwXJGFI=; b=ZKzbyf9hHWpmwim4fWbQF/K/zoQNkno+0hio/cp9pc0YvBVx1dTTVUlCG/OmTUNQEi 626nktx0qIbB3sQJjs5NM5hWD+6Qxuaq1FM4vSYxb3k29KxYRgbCVO5MvJbX2ZQKmlDU lcapaajHZNvoy/TSS9CELAPbHhF8dqTCEh/r6v9hz/+fgbAgggigQ7I7eV0dw6ScDNhy vcikr3LRfn+GKHdaDp7WGwoyqiZdsiXbYCZvfjM1EpDjbhuxEsu86zAwXSByG1FtLXHl IPxvd28gyGHjHMpPGABTfIML4Nr2UVSW0q8LMOa2sPYiVMxaiDuleTmux9L4yrlSi5zW +YTw== X-Forwarded-Encrypted: i=1; AFNElJ/fLCaKsj861CE3I+zXCrvPlMjepj5GHKuzKHBkBz/OYD8RjwWkNskJZthLIclBtmktNQuUEDYyA9d027o=@vger.kernel.org X-Gm-Message-State: AOJu0YzY1YyjRnV5PwbpdpKfnakHWfrnmaM++MYJGWsQImU2XnpjlY5V DBXtjn3aApRTeXDT5SEUKXjsqQ+B6Xp5b51QhdIIuGNKpMG+uPU+VODRkCuHA4nhOxrjdAzJruj 8vENSkRm04Q3F0HRrbZzLazNDObsUNZm7i3nXU4GAcW+pWvfgnriVvlS8gTJK9dXGqA== X-Gm-Gg: AeBDietgV3jblBVM9RAQHVizOeIqtODp7G2enQC89Igs5R8bKq8eNJkh6TOB0gisw4s 2mmCpuPCmlGG6eVzGgOJu7CbRs9OjPbsZuLh8RJOhNalA2Jsac73eLjistucUt1nE1ADQEborja uyLTzEwFoJWFlPwzMsrK8Do09GpfsmNZm5z92EjVKcqcGtptOQyw/+KLOoZA2KhWAlXed/vEXDq R9FVRcCuvhVWoD5Rgg96/1wgtooaI8G1N21Pf9RH8+JGf/3JXRlLJfVYHjl9duwxKa/dT8pRQvV 9UGV7y5FI94d/XQarCT63avj+GVdVqRQel1iBdC1zYhxqIOH9nbSaW1oRtfWZ2orHqtRWswEbxz QiYP89xP0ILyU7QsKUDcZ3EWQ3fWVsnx7FgiAq9q9YcQiwRS7A81x0w== X-Received: by 2002:a05:600c:8b38:b0:488:b14f:b8ed with SMTP id 5b1f17b1804b1-488fb6e815amr111086605e9.0.1776532691210; Sat, 18 Apr 2026 10:18:11 -0700 (PDT) X-Received: by 2002:a05:600c:8b38:b0:488:b14f:b8ed with SMTP id 5b1f17b1804b1-488fb6e815amr111085965e9.0.1776532690536; Sat, 18 Apr 2026 10:18:10 -0700 (PDT) Received: from redhat.com (IGLD-80-230-25-21.inter.net.il. [80.230.25.21]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-488fc1c0354sm129158345e9.11.2026.04.18.10.18.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 18 Apr 2026 10:18:09 -0700 (PDT) Date: Sat, 18 Apr 2026 13:18:07 -0400 From: "Michael S. Tsirkin" To: Michael Bommarito Cc: Olivia Mackall , Herbert Xu , linux-crypto@vger.kernel.org, Jason Wang , virtualization@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] hwrng: virtio: clamp device-reported used.len at copy_data() Message-ID: <20260418131110-mutt-send-email-mst@kernel.org> References: <20260418000020.1847122-1-michael.bommarito@gmail.com> <20260418150613.3522589-1-michael.bommarito@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260418150613.3522589-1-michael.bommarito@gmail.com> On Sat, Apr 18, 2026 at 11:06:13AM -0400, Michael Bommarito wrote: > random_recv_done() stores the device-reported used.len directly into > vi->data_avail. copy_data() then indexes vi->data[] using > vi->data_idx (advanced by previous copy_data() calls) and issues a > memcpy() without re-validating either value against the posted > buffer size sizeof(vi->data) (SMP_CACHE_BYTES bytes, typically 32 > or 64). > > A malicious or buggy virtio-rng backend can set used.len beyond > sizeof(vi->data), steering the memcpy() past the end of the inline > array into adjacent kmalloc-1k slab bytes. hwrng_fillfn() mixes > those bytes into the guest RNG, and guest root can also observe > them directly via /dev/hwrng. > > Concrete impact is inside the guest: > > - Memory-safety / hardening: any virtio-rng backend that > over-reports used.len causes the driver to read past vi->data > into unrelated slab contents. hwrng_fillfn() is a kernel thread > that runs as soon as the device is probed; no guest userspace > interaction is required to first-trigger the OOB. > > - Cross-boundary leak (confidential-compute threat model): a > malicious hypervisor cooperating with a malicious or compromised > guest root userspace can use /dev/hwrng as a leak channel for > guest-kernel heap data. The host sets a large used.len, guest > root reads /dev/hwrng, and the returned bytes contain guest > kernel slab contents that were adjacent to vi->data. In > practice, confidential-compute guests (SEV-SNP, TDX) usually > disable virtio-rng entirely, so this path is narrow, but the > fix is still worth carrying because the underlying > memory-safety bug contaminates the guest RNG on any host. > > KASAN confirms the OOB on a guest booted under a QEMU 9.0 whose > virtio-rng backend has been patched to report used.len = 0x10000: > > BUG: KASAN: slab-out-of-bounds in virtio_read+0x394/0x5d0 > Read of size 64 at addr ffff8880089c2220 by task hwrng/52 > Call Trace: > __asan_memcpy > virtio_read+0x394/0x5d0 > hwrng_fillfn+0xb2/0x470 > kthread > Allocated by task 1: > probe_common+0xa5/0x660 > virtio_dev_probe+0x549/0xbc0 > The buggy address belongs to the object at ffff8880089c2000 > which belongs to the cache kmalloc-1k of size 1024 > The buggy address is located 0 bytes to the right of > allocated 544-byte region [ffff8880089c2000, ffff8880089c2220) > > Same class of bug as commit c04db81cd028 ("net/9p: Fix buffer > overflow in USB transport layer"), which hardened > usb9pfs_rx_complete() against unchecked device-reported length in > the USB 9p transport. > > With the clamp at point of use and array_index_nospec() in place, > the same harness boots cleanly: copy_data() returns zero for the > bogus report, the device-supplied bytes after data_idx are > discarded, and the driver issues a fresh request. > > Changes in v2 (per Michael S. Tsirkin review): > - move the bound check from random_recv_done() into copy_data(), > so the clamp sits immediately next to the memcpy it protects > - clamp to sizeof(vi->data) rather than substituting len = 0, so a > previously-working but buggy device that occasionally over-reports > used.len does not start returning zero-length reads > - add array_index_nospec() on vi->data_idx to defeat a speculative > out-of-bounds read given the malicious-backend threat model > - expand the commit message to describe the /dev/hwrng observation > path and the hypervisor + guest-root cooperation scenario > > Fixes: f7f510ec1957 ("virtio: An entropy device, as suggested by hpa.") > Cc: stable@vger.kernel.org > Suggested-by: Michael S. Tsirkin > Signed-off-by: Michael Bommarito > Assisted-by: Claude:claude-opus-4-7 > --- > drivers/char/hw_random/virtio-rng.c | 23 +++++++++++++++++++++-- > 1 file changed, 21 insertions(+), 2 deletions(-) > > diff --git a/drivers/char/hw_random/virtio-rng.c b/drivers/char/hw_random/virtio-rng.c > index 0ce02d7e5048..5e83ffa105e4 100644 > --- a/drivers/char/hw_random/virtio-rng.c > +++ b/drivers/char/hw_random/virtio-rng.c > @@ -7,6 +7,7 @@ > #include > #include > #include > +#include > #include > #include > #include > @@ -69,8 +70,26 @@ static void request_entropy(struct virtrng_info *vi) > static unsigned int copy_data(struct virtrng_info *vi, void *buf, > unsigned int size) > { > - size = min_t(unsigned int, size, vi->data_avail); > - memcpy(buf, vi->data + vi->data_idx, size); > + unsigned int idx, avail; > + > + /* > + * vi->data_avail was set from the device-reported used.len and > + * vi->data_idx was advanced by previous copy_data() calls. A > + * malicious or buggy virtio-rng backend can drive either past > + * sizeof(vi->data). Clamp at point of use and harden the index > + * with array_index_nospec() so the memcpy() below cannot be > + * steered into adjacent slab memory, including under > + * speculation. > + */ > + avail = min_t(unsigned int, vi->data_avail, sizeof(vi->data)); > + if (vi->data_idx >= avail) { > + vi->data_avail = 0; > + request_entropy(vi); > + return 0; > + } > + size = min_t(unsigned int, size, avail - vi->data_idx); > + idx = array_index_nospec(vi->data_idx, sizeof(vi->data)); > + memcpy(buf, vi->data + idx, size); > vi->data_idx += size; > vi->data_avail -= size; > if (vi->data_avail == 0) > -- This came out quite complex. Tell me, will the following do the trick? diff --git a/drivers/char/hw_random/virtio-rng.c b/drivers/char/hw_random/virtio-rng.c index 0ce02d7e5048..e887a68cc151 100644 --- a/drivers/char/hw_random/virtio-rng.c +++ b/drivers/char/hw_random/virtio-rng.c @@ -47,6 +47,8 @@ static void random_recv_done(struct virtqueue *vq) if (!virtqueue_get_buf(vi->vq, &len)) return; + len = array_index_nospec(len, sizeof(vi->data)); + smp_store_release(&vi->data_avail, len); complete(&vi->have_data); } > 2.53.0