linux-cve-announce - CVE-2022-50430: mmc: vub300: fix warning - do not call blocking ops when !TASK

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: <2025100157-CVE-2022-50430-568d@gregkh>
Date: Wed,  1 Oct 2025 13:42:03 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50430: mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING

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

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

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

mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING

vub300_enable_sdio_irq() works with mutex and need TASK_RUNNING here.
Ensure that we mark current as TASK_RUNNING for sleepable context.

[   77.554641] do not call blocking ops when !TASK_RUNNING; state=1 set at [<ffffffff92a72c1d>] sdio_irq_thread+0x17d/0x5b0
[   77.554652] WARNING: CPU: 2 PID: 1983 at kernel/sched/core.c:9813 __might_sleep+0x116/0x160
[   77.554905] CPU: 2 PID: 1983 Comm: ksdioirqd/mmc1 Tainted: G           OE      6.1.0-rc5 #1
[   77.554910] Hardware name: Intel(R) Client Systems NUC8i7BEH/NUC8BEB, BIOS BECFL357.86A.0081.2020.0504.1834 05/04/2020
[   77.554912] RIP: 0010:__might_sleep+0x116/0x160
[   77.554920] RSP: 0018:ffff888107b7fdb8 EFLAGS: 00010282
[   77.554923] RAX: 0000000000000000 RBX: ffff888118c1b740 RCX: 0000000000000000
[   77.554926] RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffed1020f6ffa9
[   77.554928] RBP: ffff888107b7fde0 R08: 0000000000000001 R09: ffffed1043ea60ba
[   77.554930] R10: ffff88821f5305cb R11: ffffed1043ea60b9 R12: ffffffff93aa3a60
[   77.554932] R13: 000000000000011b R14: 7fffffffffffffff R15: ffffffffc0558660
[   77.554934] FS:  0000000000000000(0000) GS:ffff88821f500000(0000) knlGS:0000000000000000
[   77.554937] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   77.554939] CR2: 00007f8a44010d68 CR3: 000000024421a003 CR4: 00000000003706e0
[   77.554942] Call Trace:
[   77.554944]  <TASK>
[   77.554952]  mutex_lock+0x78/0xf0
[   77.554973]  vub300_enable_sdio_irq+0x103/0x3c0 [vub300]
[   77.554981]  sdio_irq_thread+0x25c/0x5b0
[   77.555006]  kthread+0x2b8/0x370
[   77.555017]  ret_from_fork+0x1f/0x30
[   77.555023]  </TASK>
[   77.555025] ---[ end trace 0000000000000000 ]---

The Linux kernel CVE team has assigned CVE-2022-50430 to this issue.


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

	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 4.9.337 with commit 32d5af247d4de6a35769ca1d027480a37c28fd0c
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 4.14.303 with commit 48e91ae755f027d817ed7e51db9963ddb7081946
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 4.19.270 with commit 6f7258c6f66692b3760c37ddd4bc9e02bb290da7
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 5.4.229 with commit f1c08947ab0538b07a0bd9d6edadfb5185f56344
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 5.10.163 with commit b51d5fed9f53e07ce9fc65efb4ff1abe021a4c16
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 5.15.87 with commit d58289fc77f8c1f879c818bddaf7ef524c73658b
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 6.0.17 with commit d15946ef98f4ccdca961b76f90d9b53c454d590e
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 6.1.3 with commit ba2e7d07dd06e646a72ba906a89fdc1cca7ea560
	Issue introduced in 3.0 with commit 88095e7b473a3d9ec3b9c60429576e9cbd327c89 and fixed in 6.2 with commit 4a44cd249604e29e7b90ae796d7692f5773dd348

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-2022-50430
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/mmc/host/vub300.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/32d5af247d4de6a35769ca1d027480a37c28fd0c
	https://git.kernel.org/stable/c/48e91ae755f027d817ed7e51db9963ddb7081946
	https://git.kernel.org/stable/c/6f7258c6f66692b3760c37ddd4bc9e02bb290da7
	https://git.kernel.org/stable/c/f1c08947ab0538b07a0bd9d6edadfb5185f56344
	https://git.kernel.org/stable/c/b51d5fed9f53e07ce9fc65efb4ff1abe021a4c16
	https://git.kernel.org/stable/c/d58289fc77f8c1f879c818bddaf7ef524c73658b
	https://git.kernel.org/stable/c/d15946ef98f4ccdca961b76f90d9b53c454d590e
	https://git.kernel.org/stable/c/ba2e7d07dd06e646a72ba906a89fdc1cca7ea560
	https://git.kernel.org/stable/c/4a44cd249604e29e7b90ae796d7692f5773dd348