CVE-2026-97917: accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr

CVE-2026-97917: accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr

Add a size parameter to ivpu_to_cpu_addr() and validate that the
whole [vpu_addr, vpu_addr + size) range stays within the BO.

The Linux kernel CVE team has assigned CVE-2026-97917 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.3 with commit 647371a6609ddf8700fe151af72e32daebb9baa7 and fixed in 6.12.111 with commit 5419be345f32222750e006b85b7f9bae1a285c8e
	Issue introduced in 6.3 with commit 647371a6609ddf8700fe151af72e32daebb9baa7 and fixed in 6.18.53 with commit 43c68f52aecd519eb682fa09d57ae52c896f860f
	Issue introduced in 6.3 with commit 647371a6609ddf8700fe151af72e32daebb9baa7 and fixed in 7.2.7 with commit 29f82a2280e170429370e7a842cde4e70ead8547
	Issue introduced in 6.3 with commit 647371a6609ddf8700fe151af72e32daebb9baa7 and fixed in 7.3-rc3 with commit 3837c3f29fbc3b8c12bebf5c62741e2befe3482a

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-97917
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/accel/ivpu/ivpu_gem.h
	drivers/accel/ivpu/ivpu_ipc.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/5419be345f32222750e006b85b7f9bae1a285c8e
	https://git.kernel.org/stable/c/43c68f52aecd519eb682fa09d57ae52c896f860f
	https://git.kernel.org/stable/c/29f82a2280e170429370e7a842cde4e70ead8547
	https://git.kernel.org/stable/c/3837c3f29fbc3b8c12bebf5c62741e2befe3482a