Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-50381

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: md: fix a crash in mempool_free There's a crash in mempool_free when running the lvm test shell/lvchange-rebuild-raid.sh.

Published Sep 18, 2025CWE-476EPSS 0.16%

Overview

CVE-2022-50381 is a medium-severity vulnerability. It was published on September 18, 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:

md: fix a crash in mempool_free

There's a crash in mempool_free when running the lvm test

shell/lvchange-rebuild-raid.sh.

The reason for the crash is this:

* super_written calls atomic_dec_and_test(&mddev->pending_writes) and

wake_up(&mddev->sb_wait). Then it calls rdev_dec_pending(rdev, mddev)

and bio_put(bio).

* so, the process that waited on sb_wait and that is woken up is racing

with bio_put(bio).

* if the process wins the race, it calls bioset_exit before bio_put(bio)

is executed.

* bio_put(bio) attempts to free a bio into a destroyed bio set - causing

a crash in mempool_free.

We fix this bug by moving bio_put before atomic_dec_and_test.

We also move rdev_dec_pending before atomic_dec_and_test as suggested by

Neil Brown.

The function md_end_flush has a similar bug - we must call bio_put before

we decrement the number of in-progress bios.

BUG: kernel NULL pointer dereference, address: 000000000000

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/341097ee53573e06ab9fc675d96a052385b851faRefgit.kernel.org/stable/c/384ef33d37cefb2ac539d44597d03f06c9b8975cRefgit.kernel.org/stable/c/732cd66ec19a17f2b9183d7d5b7bdb9c39b0776eRefgit.kernel.org/stable/c/842f222fc42a9239831e15b1fd49a51c546902cbRefgit.kernel.org/stable/c/91bd504128a51776472445070e11a3b0f9348c90Refgit.kernel.org/stable/c/97ce99984be12b9acb49ddce0f5d8ebb037adbb6Refgit.kernel.org/stable/c/ae7793027766491c5f8635b12d15a5940d3b8698Refgit.kernel.org/stable/c/b5be563b4356b3089b3245d024cae3f248ba7090Refgit.kernel.org/stable/c/cf06b162f5b6337b688072a1a47941280b8f7110

How CyberStrike helps

Frequently asked questions

What is CVE-2022-50381?

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

How severe is CVE-2022-50381?

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-50381?

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-50381?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50381 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