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 B90173F1661 for ; Fri, 8 May 2026 14:27:30 +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=1778250450; cv=none; b=dfNeTBlCZp2p7EMizC1Y1K3wv1RfLxU75IkqcKJFhvL9hXati3DTy4DBG1/7Ujvs3emRnXSIr1eltt6KSQ0FCqKXakspoWJgOAtbWwRVu+cNDKe18EcglA+HJFQmE/hfBoDl1BppDkGd6NHpWRagQx9iWbddCcE8KVKI8vmHaik= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250450; c=relaxed/simple; bh=j1RdcZ/mJeR8Tx+fsXkOaMWvzWYXJHZ+umDdyNzV8WA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=VJz82X5ufdznHvtJGoKhuOA1p8BGjtDLz+6wcIkOwU/ES2qy2ynNKmyjAmcN8Vfn+aGM/pOhu1sLwHVkB96HXbwD8TAOlL9r22F7toxwBLj0P2qvDn3vMGWk9ZI9Y8zMtegF4wsYMH9bsr7vZRpZJzGCj+wZ/dYzeeScBJsl2YA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=xi3vFkJ2; 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="xi3vFkJ2" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 55257C2BCB0; Fri, 8 May 2026 14:27:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778250450; bh=j1RdcZ/mJeR8Tx+fsXkOaMWvzWYXJHZ+umDdyNzV8WA=; h=From:To:Cc:Subject:Date:Reply-To:From; b=xi3vFkJ2USJp+GXAlRkxdqFl/NreCXjsBBBN5zMKDgn1e1Dqq2oF3MlBi1mbgC2Xp JaRDAMYUQAfIJBpWYrqZNXvVCC97Z3P6cmAjKWy3xAS50iYNIUmKPo3wttKM0hrDIP kZMQyeETPMbBSpiJpk+K7sod5lCPlLb+CJQpCEoU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43459: ASoC: soc-core: flush delayed work before removing DAIs and widgets Date: Fri, 8 May 2026 16:23:08 +0200 Message-ID: <2026050800-CVE-2026-43459-2ed8@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=4259; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ghEBULrZGwW0w42HAfsOwzEf/WfNLycGdvmgpuFDxMk=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/P3b8rXsfM7FJXkeDU+0w75VoCWHxAOWzh/dlTambU Xn2GZduRwwLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzk1jaG6cnrn9zqibw3c2vO i9ry1Ka8OYppDAvaZnTVh//YcL6urj+9Rm/KrfOTKpYDAA== 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: ASoC: soc-core: flush delayed work before removing DAIs and widgets When a sound card is unbound while a PCM stream is open, a use-after-free can occur in snd_soc_dapm_stream_event(), called from the close_delayed_work workqueue handler. During unbind, snd_soc_unbind_card() flushes delayed work and then calls soc_cleanup_card_resources(). Inside cleanup, snd_card_disconnect_sync() releases all PCM file descriptors, and the resulting PCM close path can call snd_soc_dapm_stream_stop() which schedules new delayed work with a pmdown_time timer delay. Since this happens after the flush in snd_soc_unbind_card(), the new work is not caught. soc_remove_link_components() then frees DAPM widgets before this work fires, leading to the use-after-free. The existing flush in soc_free_pcm_runtime() also cannot help as it runs after soc_remove_link_components() has already freed the widgets. Add a flush in soc_cleanup_card_resources() after snd_card_disconnect_sync() (after which no new PCM closes can schedule further delayed work) and before soc_remove_link_dais() and soc_remove_link_components() (which tear down the structures the delayed work accesses). The Linux kernel CVE team has assigned CVE-2026-43459 to this issue. Affected and fixed versions =========================== Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 5.10.253 with commit bf80a89da97285d9b877e0c6995e870d46b8025c Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 5.15.203 with commit 3887e514978d28216246360b46a9cb534969eb5a Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.1.167 with commit 231568afbc0cd25b8fb2a94ebf9738eabe1cf007 Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.6.130 with commit 317a9298c54bb00319da73e5a7179f00e67fcbdf Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.12.78 with commit eab71e11ce2447c1e01809cbc11eab4234cf8dc8 Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.18.19 with commit 7d33e6140945482a07f8089ee86e13e02553ffdb Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 6.19.9 with commit c054f0607c8bb1b1aa529bc109e4149298a1cccd Issue introduced in 4.20 with commit e894efef9ac7c10b7727798dcc711cccf07569f9 and fixed in 7.0 with commit 95bc5c225513fc3c4ce169563fb5e3929fbb938b 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-43459 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: sound/soc/soc-core.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/bf80a89da97285d9b877e0c6995e870d46b8025c https://git.kernel.org/stable/c/3887e514978d28216246360b46a9cb534969eb5a https://git.kernel.org/stable/c/231568afbc0cd25b8fb2a94ebf9738eabe1cf007 https://git.kernel.org/stable/c/317a9298c54bb00319da73e5a7179f00e67fcbdf https://git.kernel.org/stable/c/eab71e11ce2447c1e01809cbc11eab4234cf8dc8 https://git.kernel.org/stable/c/7d33e6140945482a07f8089ee86e13e02553ffdb https://git.kernel.org/stable/c/c054f0607c8bb1b1aa529bc109e4149298a1cccd https://git.kernel.org/stable/c/95bc5c225513fc3c4ce169563fb5e3929fbb938b