The memstick ms_block driver in the Linux kernel allocates an ordered workqueue for every inserted card during initialization. Because the driver never frees this workqueue upon card removal, each insertion/removal cycle leaks both the workqueue and its kworker thread. Over repeated cycles, available kernel memory is depleted, which can lead to the kernel failing to handle further allocation requests, resulting in system instability or a crash—a denial-of-service condition.

All Linux kernel configurations that include the memstick ms_block driver, which is part of the mainstream distribution kernel. Any system that uses the stock kernel without disabling this driver is affected.

The CVSS score of 5.5 indicates medium severity, while the EPSS score of less than 1% shows a very low likelihood of exploitation under normal circumstances. The vulnerability is not listed in CISA's KEV catalog. The only way to trigger the memory leak is to repeatedly insert and remove supported memory cards or USB devices that the driver handles. No network interface is exposed, so the attack vector requires local or privileged access; it is inferred that an attacker with such access could trigger the failure by automating card insertion events.