CVE-2022-50140Published Jun 18, 2025 · Jun 18Updated Oct 28
memstick/ms_block: Fix a memory leak
Linux
Medium5.5Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 · < 16e07966638717416abf45393d6a80a5a1034429| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
memstick/ms_block: Fix a memory leak
'erased_blocks_bitmap' is never freed. As it is allocated at the same time as 'used_blocks_bitmap', it is likely that it should be freed also at the same time.
Add the corresponding bitmap_free() in msb_data_clear().
From the CVE record · Linux
The Linux kernel’s memstick/ms_block component does not free the erased_blocks_bitmap during cleanup, causing a memory leak. The input does not establish whether an attacker can trigger the leak or what access or user interaction would be required.
Engineers running the Linux kernel should check whether their kernel includes the affected memstick/ms_block code; affected versions were not provided.