Skip to content

[ciqlts9_2] Multiple patches tested (2 commits) - #1706

Open
ciq-kernel-automation[bot] wants to merge 2 commits into
ciqlts9_2from
{maple}_ciqlts9_2
Open

ciq-kernel-automation[bot] wants to merge 2 commits into
ciqlts9_2from
{maple}_ciqlts9_2

Conversation

@ciq-kernel-automation

Copy link
Copy Markdown

Summary

This PR has been automatically created after successful completion of all CI stages.

Commit Message(s)

vhost: reset the vring metadata cache on vring reconfiguration

jira VULN-204218
cve CVE-2026-74580
commit-author Jun Yang <junvyyang@tencent.com>
commit de845981da67a6b049080c87e605130b0c30adc5
ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices

jira VULN-46743
cve CVE-2024-53197
commit-author Benoît Sevens <bsevens@google.com>
commit b8f8b81dabe52b413fe9e062e8a852c48dd0680d

Test Results

✅ Build Stage

Architecture Build Time Total Time
x86_64 18m 6s 18m 51s
aarch64 8m 47s 9m 17s

✅ Boot Verification

✅ Kernel Selftests

Architecture Passed Failed Compared Against Status
x86_64 174 24 ciqlts9_2 ✅ No regressions
aarch64 144 24 ciqlts9_2 ✅ No regressions

✅ LTP Results

Architecture Passed Failed Compared Against Status
x86_64 1433 81 ciqlts9_2 ✅ No regressions
aarch64 1409 83 ciqlts9_2 ✅ No regressions

🤖 This PR was automatically generated by GitHub Actions
Run ID: 38805267708

jira VULN-204218
cve CVE-2026-74580
commit-author Jun Yang <junvyyang@tencent.com>
commit de84598

vq->meta_iotlb[] caches the vhost_iotlb_map that backs each vring
metadata region, and iotlb_access_ok() returns early on a cache hit,
taking the hit as proof that the region has already been validated:

	if (vhost_vq_meta_fetch(vq, addr, len, type))
		return true;

The cache is reset on VHOST_IOTLB_UPDATE and VHOST_IOTLB_INVALIDATE, on
device IOTLB (re)initialisation and on vq reset, but not when
VHOST_SET_VRING_ADDR replaces vq->desc, vq->avail and vq->used, nor when
VHOST_SET_VRING_NUM changes the region sizes.

With a device IOTLB attached both ioctls are accepted while the vq is
live, and neither validates the addresses at ioctl time: vq_access_ok()
and vq_log_used_access_ok() return true early because the addresses are
GIOVAs, deferring validation to prefetch time.  Once the cache has been
populated that deferred validation no longer runs -- vq_meta_prefetch()
hits the stale entry and returns true -- and vhost_vq_meta_fetch() keeps
translating through the old mapping as

	map->addr + addr - map->start

for an address the mapping no longer covers.  vhost_copy_to_user() and
vhost_copy_from_user() consume the result with __copy_to_user() and
__copy_from_user(), which do not check it either, so a subsequent used
ring update or descriptor fetch accesses memory outside the region the
IOTLB actually maps.

Reset the metadata cache whenever the vring is reconfigured, so the new
addresses are pushed back through iotlb_access_ok()'s slow path.

Fixes: f889491 ("vhost: introduce O(1) vq metadata cache")
	Cc: stable@vger.kernel.org
Assisted-by: tencentos-corvus-ai:kimi-k3
	Signed-off-by: Jun Yang <junvyyang@tencent.com>
Message-ID: <20260803014823.68623-1-juny24602@gmail.com>
	Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
(cherry picked from commit de84598)
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
…box devices

jira VULN-46743
cve CVE-2024-53197
commit-author Benoît Sevens <bsevens@google.com>
commit b8f8b81

commit b909df1 upstream.

A bogus device can provide a bNumConfigurations value that exceeds the
initial value used in usb_get_configuration for allocating dev->config.

This can lead to out-of-bounds accesses later, e.g. in
usb_destroy_configuration.

	Signed-off-by: Benoît Sevens <bsevens@google.com>
Fixes: 1da177e ("Linux-2.6.12-rc2")
	Cc: stable@kernel.org
Link: https://patch.msgid.link/20241120124144.3814457-1-bsevens@google.com
	Signed-off-by: Takashi Iwai <tiwai@suse.de>
	Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit b8f8b81)
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
@ciq-kernel-automation ciq-kernel-automation Bot added the created-by-kernelci Tag PRs that were automatically created when a user branch was pushed to the repo (kernelCI) label Oct 16, 2026
@github-actions

Copy link
Copy Markdown

❌ Diffofdiffs: 1 of 2 backports couldn't be compared with upstream

Warning

1 backport couldn't be compared. Details are in the workflow run log.

1. ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices

Backport: e06b15d7f95c · Upstream: Unavailable

Show error
The commit message names more than one upstream commit

Checked PR revision e06b15d7f95c against base f51e0d053984.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

created-by-kernelci Tag PRs that were automatically created when a user branch was pushed to the repo (kernelCI)

Development

Successfully merging this pull request may close these issues.

1 participant