LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50668: ext4: fix deadlock due to mbcache entry corruption

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50668 is a Linux kernel ext4 filesystem bug that can cause an indefinite deadlock while handling extended attribute blocks. The main business risk is availability: affected systems may hang or become unresponsive during filesystem activity. Public sources do not show active exploitation or a CVSS score.

Executive priority

Treat as a planned availability-risk kernel update. Prioritize production Linux systems using ext4, especially where downtime is costly. There is no source-backed evidence of active exploitation, so emergency response is not indicated solely from the provided data.

Technical view

The flaw is in ext4 xattr block reuse through mbcache. A non-atomic update of the e_reusable bit can race with e_referenced in the same bitfield, leaving an inconsistent reusable state. ext4_xattr_block_set() may then retry indefinitely. Kernel stable commits fix this by using atomic bit operations.

Likely exposure

Exposure is most relevant to Linux systems using ext4 filesystems where extended attributes are manipulated. The provided affected data lists Linux kernel versions including 4.6 and stable lines around 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.18, 6.1.4, and 6.2, but exact distro package status requires vendor confirmation.

Exploitation context

No provided source reports active exploitation, and this CVE is not marked KEV. The issue appears to require conditions that trigger ext4 extended attribute block handling and a race in mbcache state. Public data supports an availability impact, not remote code execution or privilege escalation.

Researcher notes

The core condition is mbcache entry corruption from non-atomic bitfield updates to e_reusable and e_referenced. The fix uses atomic bitops. The source bundle lacks CVSS, CWE, precise distro package mapping, and exploitability analysis, so exposure assessment depends on kernel branch and vendor backport status.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable ext4 fixes.
  • Check your Linux distribution advisory for backported fixes and package names.
  • Prioritize critical servers using ext4 and extended attributes.
  • Schedule kernel updates through normal reboot or live-patching processes, where supported.

Validation and detection

  • Inventory Linux kernel versions across ext4-based systems.
  • Confirm whether the referenced stable commits are present or backported.
  • Review vendor changelogs for CVE-2022-50668 or the ext4 mbcache fix.
  • Monitor for kernel hangs or stack traces involving ext4_xattr_block_set().
  • After updating, verify the running kernel is the fixed build.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50668 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6048c64b26097a0ffbd966866b599f990e674e9b, 6048c64b26097a0ffbd966866b599f990e674e9b, 6048c64b26097a0ffbd966866b599f990e674e9b, 6048c64b26097a0ffbd966866b599f990e674e9b, 6048c64b26097a0ffbd966866b599f990e674e9b, 6048c64b26097a0ffbd966866b599f990e674e9b, 6048c64b26097a0ffbd966866b599f990e674e9bunaffected
LinuxLinux4.6, 0, 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.18, 6.1.4, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.