CVE-2022-50668

ext4: fix deadlock due to mbcache entry corruption

HIGH
7.5
CVSS Score
Published: December 9, 2025 at 01:29 AM UTC
Updated: August 5, 2026 at 09:24 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
Severity
HIGH7.5
Exploit prediction
EPSS 0.8%

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock due to mbcache entry corruption When manipulating xattr blocks, we can deadlock infinitely looping inside ext4_xattr_block_set() where we constantly keep finding xattr block for reuse in mbcache but we are unable to reuse it because its reference count is too big. This happens because cache entry for the xattr block is marked as reusable (e_reusable set) although its reference count is too big. When this inconsistency happens, this inconsistent state is kept indefinitely and so ext4_xattr_block_set() keeps retrying indefinitely. The inconsistent state is caused by non-atomic update of e_reusable bit. e_reusable is part of a bitfield and e_reusable update can race with update of e_referenced bit in the same bitfield resulting in loss of one of the updates. Fix the problem by using atomic bitops instead. This bug has been around for many years, but it became *much* easier to hit after commit 65f8b80053a1 ("ext4: fix race when reusing xattr blocks").

Affected

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

4.6 ≤ v < 4.19.2704.6 ≤ v < 5.10.1634.6 ≤ v < 5.15.874.6 ≤ v < 5.4.2294.6 ≤ v < 6.0.184.6 ≤ v < 6.1.44.6 ≤ v < 6.24.66048c64b26097a0ffbd966866b599f990e674e9b
Vendor states this is fixed in 127b80cefb941a81255c72f11081123f3a705369 (fixed)
Vendor states this is fixed in 1be16a0c2f10186df505e28b0cc92d7f3366e2a8 (fixed)
Vendor states this is fixed in 5bc0b2fda4b47c86278f7c6d30c211f425bf51cf (fixed)
Vendor states this is fixed in a44e84a9b7764c72896f7241a0ec9ac7e7ef38dd (fixed)
Vendor states this is fixed in af53065276376750dfac35a7248af18806404c5d (fixed)
Vendor states this is fixed in cc1538c693d25e282bed8c54b65c914a04023a78 (fixed)
Vendor states this is fixed in efaa0ca678f56d47316a08030b2515678cebbc50 (fixed)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.6 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.87 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.18 (unaffected)
Vendor states this is fixed in 6.1.4 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card