linux-cve-announce - CVE-2024-56540: accel/ivpu: Prevent recovery invocation during probe and resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2024122726-CVE-2024-56540-d2f7@gregkh>
Date: Fri, 27 Dec 2024 15:11:31 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-56540: accel/ivpu: Prevent recovery invocation during probe and resume

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

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

accel/ivpu: Prevent recovery invocation during probe and resume

Refactor IPC send and receive functions to allow correct
handling of operations that should not trigger a recovery process.

Expose ivpu_send_receive_internal(), which is now utilized by the D0i3
entry, DCT initialization, and HWS initialization functions.
These functions have been modified to return error codes gracefully,
rather than initiating recovery.

The updated functions are invoked within ivpu_probe() and ivpu_resume(),
ensuring that any errors encountered during these stages result in a proper
teardown or shutdown sequence. The previous approach of triggering recovery
within these functions could lead to a race condition, potentially causing
undefined behavior and kernel crashes due to null pointer dereferences.

The Linux kernel CVE team has assigned CVE-2024-56540 to this issue.

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

	Issue introduced in 6.8 with commit 45e45362e0955fc3b0b622e8a0d788097f3de902 and fixed in 6.11.11 with commit cac822772c4dc27a285f09caf30072ab76d2bf38
	Issue introduced in 6.8 with commit 45e45362e0955fc3b0b622e8a0d788097f3de902 and fixed in 6.12.2 with commit 362ef76020ea6219a4df4ac5b738672b59527239
	Issue introduced in 6.8 with commit 45e45362e0955fc3b0b622e8a0d788097f3de902 and fixed in 6.13-rc1 with commit 5eaa497411197c41b0813d61ba3fbd6267049082

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-2024-56540
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_ipc.c
	drivers/accel/ivpu/ivpu_ipc.h
	drivers/accel/ivpu/ivpu_jsm_msg.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/cac822772c4dc27a285f09caf30072ab76d2bf38
	https://git.kernel.org/stable/c/362ef76020ea6219a4df4ac5b738672b59527239
	https://git.kernel.org/stable/c/5eaa497411197c41b0813d61ba3fbd6267049082