CVE-2022-50140

memstick/ms_block: Fix a memory leak

MEDIUM

5.5

CVSS Score

Published: June 18, 2025 at 11:03 AM UTC

Updated: June 17, 2026 at 05:22 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

3.12 ≤ v < 4.14.2913.12 ≤ v < 4.19.2563.12 ≤ v < 5.10.1373.12 ≤ v < 5.15.613.12 ≤ v < 5.18.183.12 ≤ v < 5.19.23.12 ≤ v < 5.4.2113.12 ≤ v < 6.04.15 ≤ v < 4.19.2564.20 ≤ v < 5.4.2115.11 ≤ v < 5.15.615.16 ≤ v < 5.18.185.19 ≤ v < 5.19.25.5 ≤ v < 5.10.1370ab30494bc4f3bc1ea4659b7c5d97c5218554a63 3.12

Vendor states this is fixed in 16e07966638717416abf45393d6a80a5a1034429 (fixed)

Vendor states this is fixed in 37958980eb4cd71ae594ace093c11b6a91e165e8 (fixed)

Vendor states this is fixed in 39be95d1ff7b44c1e969af72ba9da7332dfcc1da (fixed)

Vendor states this is fixed in 54eb7a55be6779c4d0c25eaf5056498a28595049 (fixed)

Vendor states this is fixed in 9260a154b3b5e387dbceec7c0ac441470646bc6f (fixed)

Vendor states this is fixed in 961d7d12080fe70847f944d656e36cd0dd0214ba (fixed)

Vendor states this is fixed in 9d8b911fe3c3ed788c66edba7c90e32a4a7a5f53 (fixed)

Vendor states this is fixed in efd675246aec045507b9425c67b548cc2d782d8f (fixed)

Vendor states this is fixed in 3.12 (unaffected)

Vendor states this is fixed in 4.14.291 (unaffected)

Vendor states this is fixed in 4.19.256 (unaffected)

Vendor states this is fixed in 5.10.137 (unaffected)