LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50286: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline

In the Linux kernel, the following vulnerability has been resolved: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline When converting files with inline data to extents, delayed allocations made on a file system created with both the bigalloc and inline options can result in invalid extent status cache content, incorrect reserved cluster counts, kernel memory leaks, and potential kernel panics. With bigalloc, the code that determines whether a block must be delayed allocated searches the extent tree to see if that block maps to a previously allocated cluster. If not, the block is delayed allocated, and otherwise, it isn't. However, if the inline option is also used, and if the file containing the block is marked as able to store data inline, there isn't a valid extent tree associated with the file. The current code in ext4_clu_mapped() calls ext4_find_extent() to search the non-existent tree for a previously allocated cluster anyway, which typically finds nothing, as desired. However, a side effect of the search can be to cache invalid content from the non-existent tree (garbage) in the extent status tree, including bogus entries in the pending reservation tree. To fix this, avoid searching the extent tree when allocating blocks for bigalloc + inline files that are being converted from inline to extent mapped.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel ext4 bug can corrupt internal allocation bookkeeping when a filesystem uses both bigalloc and inline-data features. The documented outcomes include incorrect reservations, kernel memory leaks, and possible kernel panics. Exposure appears configuration-specific rather than broad.

Executive priority

Treat as targeted operational risk for Linux systems using uncommon ext4 feature combinations. Prioritize validation on storage-heavy or availability-sensitive hosts, then patch through normal kernel maintenance if exposure is confirmed.

Technical view

The flaw is in ext4_clu_mapped() during conversion from inline data to extent mapping on ext4 filesystems created with bigalloc and inline. The kernel may search a non-existent extent tree, caching invalid extent status and pending reservation data.

Likely exposure

Systems are most likely exposed if they run affected Linux kernel versions and use ext4 filesystems created with both bigalloc and inline options. Ordinary ext4 deployments without that feature combination are less likely to be affected based on the provided description.

Exploitation context

The source bundle does not show active exploitation, public exploit details, or KEV listing. The impact described is local filesystem corruption of kernel metadata state, memory leaks, and potential kernel panics under the specific ext4 feature combination.

Researcher notes

Key evidence is the kernel fix description and stable commit references. No CVSS, CWE, exploit status, or vendor package mapping is provided in the bundle, so impact scoring and distribution-specific exposure require follow-up with vendor advisories.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable ext4 fixes.
  • Use distribution vendor advisories to map fixed kernel packages for your platform.
  • Prioritize hosts using ext4 bigalloc and inline features together.
  • Avoid inventing local workarounds; follow kernel or distribution guidance.

Validation and detection

  • Inventory Linux kernel versions against the affected ranges in the CVE record.
  • Identify ext4 filesystems created with both bigalloc and inline features.
  • Confirm deployed kernels include the relevant stable fix commit.
  • Review kernel logs for ext4 errors, memory leaks, or panic events.
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-50286 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
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd40e09f701cf7a44e595a558b067b2b4f67fbf87, 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6, 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6, 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6, 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6, 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6, 0b02f4c0d6d9e2c611dfbdd4317193e9dca740e6unaffected
LinuxLinux4.20, 0, 4.19.271, 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.