From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 6779A3E276D for ; Fri, 8 May 2026 13:14:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778246064; cv=none; b=a0EPiYZkjaLT87ykjjVnoIBiDPTjBvsy1Gx6heCsXR/ZRPX2igcPOTOjrWUPh2Q7hsLFnaTSEI1ICCa6LJr2Jr78w5cM76Zv6LjdYhthNWZ/lmC3KJjQjbiOvDLoaAmAHnfaz3UOQC26HStE56BDuEUWX2FQpfP+n6qSYfRG36Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778246064; c=relaxed/simple; bh=ZXPiRvGSV41hFTSdWB1erhGI+3ki5nxiRFulm1NVRZ4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ZFfblySf6f7A7R85gGNHiiJgLM+ILcotUzp5925lx8nJNztTA6xn7ffTAGu+MoyrPx1FUnyIVWrAp7fMCZEUXCx0O+L+KwKaNI3vDdrBOtwF+YvvZmRaw1BfArPIxnFZCZ/miUZnpquhESPXGrBYHRQvSHz+fMIIFrOeJ8fS24w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=zgTIwA1B; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="zgTIwA1B" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B942EC2BCB0; Fri, 8 May 2026 13:14:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778246064; bh=ZXPiRvGSV41hFTSdWB1erhGI+3ki5nxiRFulm1NVRZ4=; h=From:To:Cc:Subject:Date:Reply-To:From; b=zgTIwA1B3qj1hIQlxnW68E8FiMVhNSDQYmWR6Jg2ZnM4/pBF7xL8ott819iEPG4y5 HVjIuI5/TQdc0nu9HoTKKLbpTMPQXIOgeBNo6nBcKqiZ7tZY+vfLI++Vtg/YWh75XZ oj93Bbm6jH4/vIKb1DHS0fDn9FIBuGtiHTe9AVMk= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43301: media: chips-media: wave5: Fix PM runtime usage count underflow Date: Fri, 8 May 2026 15:12:06 +0200 Message-ID: <2026050856-CVE-2026-43301-e11d@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2822; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=2u4nikeoE4IeF/sKUg4Ex/JUOC3vlwijW57UyctfON0=; b=kA0DAAIRMUfUDdst+ykByyZiAGn94Ryi6IMeiW8u5PHehj4+pAwA3/dCyaQSNtIuucQOvhvma IhdBAARAgAdFiEE9LYMxb94wiFKMT3LMUfUDdst+ykFAmn94RwACgkQMUfUDdst+ylabgCgvlaj E2s+mEsH0Jv3YQ68nOT1rFIAoJKvJzmpjd8XjXoT4IiIu3wCjQFe X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix PM runtime usage count underflow Replace pm_runtime_put_sync() with pm_runtime_dont_use_autosuspend() in the remove path to properly pair with pm_runtime_use_autosuspend() from probe. This allows pm_runtime_disable() to handle reference count cleanup correctly regardless of current suspend state. The driver calls pm_runtime_put_sync() unconditionally in remove, but the device may already be suspended due to autosuspend configured in probe. When autosuspend has already suspended the device, the usage count is 0, and pm_runtime_put_sync() decrements it to -1. This causes the following warning on module unload: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 963 at kernel/kthread.c:1430 kthread_destroy_worker+0x84/0x98 ... vdec 30210000.video-codec: Runtime PM usage count underflow! The Linux kernel CVE team has assigned CVE-2026-43301 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit 9707a6254a8a6b978bde811a44fe07d86c229d1c and fixed in 6.18.16 with commit 3a278a55ead50db2444c8f01410c7f5a68723990 Issue introduced in 6.8 with commit 9707a6254a8a6b978bde811a44fe07d86c229d1c and fixed in 6.19.6 with commit 0bffda02317989f8d5cdc2d4462a4110b1290cf0 Issue introduced in 6.8 with commit 9707a6254a8a6b978bde811a44fe07d86c229d1c and fixed in 7.0 with commit 9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38 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-43301 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/media/platform/chips-media/wave5/wave5-vpu.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/3a278a55ead50db2444c8f01410c7f5a68723990 https://git.kernel.org/stable/c/0bffda02317989f8d5cdc2d4462a4110b1290cf0 https://git.kernel.org/stable/c/9cf4452e824c1e2d41c9c0b13cc8a32a0a7dec38