CVE-2022-50668 Details
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").
A deadlock vulnerability has been identified in the Linux kernel's ext4 file system when handling extended attribute (xattr) blocks. This issue arises from a corruption of the mbcache entry, leading to an infinite loop in the function ext4_xattr_block_set(). The problem occurs because the cache entry for the xattr block is incorrectly marked as reusable, despite its reference count being too high for reuse. This inconsistency, caused by a non-atomic update of the reusable bit, allows the reference count update to clash with the referenced bit update, creating a persistent erroneous state. As a result, the function continuously retries to reuse the block, causing a deadlock. This vulnerability has existed for several years but became significantly more pronounced after a previous commit intended to fix a related issue.
The vulnerability has been addressed by updating the mbcache entry management to use atomic operations for the reusable and referenced flags, preventing the race condition that leads to the deadlock. Users should upgrade to the patched version of the Linux kernel where this fix is applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 9, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/127b80cefb941a81255c72f11081123f3a705369 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/1be16a0c2f10186df505e28b0cc92d7f3366e2a8 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/5bc0b2fda4b47c86278f7c6d30c211f425bf51cf | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/a44e84a9b7764c72896f7241a0ec9ac7e7ef38dd | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/af53065276376750dfac35a7248af18806404c5d | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/cc1538c693d25e282bed8c54b65c914a04023a78 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/efaa0ca678f56d47316a08030b2515678cebbc50 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 9, 2025 | New CVE Received | kernel.org |
Volerion