Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-50430

5.5 · MEDIUM

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_…

Published Oct 1, 2025EPSS 0.16%

Overview

CVE-2022-50430 is a medium-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/32d5af247d4de6a35769ca1d027480a37c28fd0cRefgit.kernel.org/stable/c/48e91ae755f027d817ed7e51db9963ddb7081946Refgit.kernel.org/stable/c/4a44cd249604e29e7b90ae796d7692f5773dd348Refgit.kernel.org/stable/c/6f7258c6f66692b3760c37ddd4bc9e02bb290da7Refgit.kernel.org/stable/c/b51d5fed9f53e07ce9fc65efb4ff1abe021a4c16Refgit.kernel.org/stable/c/ba2e7d07dd06e646a72ba906a89fdc1cca7ea560Refgit.kernel.org/stable/c/d15946ef98f4ccdca961b76f90d9b53c454d590eRefgit.kernel.org/stable/c/d58289fc77f8c1f879c818bddaf7ef524c73658bRefgit.kernel.org/stable/c/f1c08947ab0538b07a0bd9d6edadfb5185f56344

How CyberStrike helps

Frequently asked questions

What is CVE-2022-50430?

CVE-2022-50430 is a medium-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-50430?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-50430?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50430?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50430 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999