LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50306: ext4: fix potential out of bound read in ext4_fc_replay_scan()

In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential out of bound read in ext4_fc_replay_scan() For scan loop must ensure that at least EXT4_FC_TAG_BASE_LEN space. If remain space less than EXT4_FC_TAG_BASE_LEN which will lead to out of bound read when mounting corrupt file system image. ADD_RANGE/HEAD/TAIL is needed to add extra check when do journal scan, as this three tags will read data during scan, tag length couldn't less than data length which will read.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is an out-of-bounds read in ext4 journal replay when mounting a corrupt filesystem image. Business risk depends on whether systems mount untrusted ext4 media or images. The provided sources do not give CVSS, confirmed impact, or active exploitation evidence.

Executive priority

Treat this as a targeted Linux exposure review, not an emergency, based on the available sources. Prioritize environments that mount untrusted ext4 images and fold remediation into normal kernel patching unless vendor guidance raises severity.

Technical view

The flaw is in ext4_fc_replay_scan(). During fast commit replay scanning, insufficient remaining-space and tag-length checks can allow reads beyond expected bounds for corrupt filesystem images, including ADD_RANGE, HEAD, and TAIL tag handling. The kernel stable references contain the fixes.

Likely exposure

Exposure is most relevant for Linux systems that mount corrupt or attacker-supplied ext4 filesystem images. Ordinary servers with controlled storage are less clearly exposed from the provided evidence. The source bundle lists Linux kernel versions including 5.10, 5.15.87, 6.0.6, and 6.1 as affected.

Exploitation context

The source bundle describes the trigger as mounting a corrupt filesystem image. It does not provide proof of active exploitation, public weaponization, privilege impact, crash behavior, or data disclosure. The bundle marks KEV as false.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. The core validation question is whether vulnerable ext4 fast commit replay code is present in deployed kernels and reachable through untrusted filesystem mounts.

Mitigation direction

  • Update to a Linux kernel build containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes and supported package versions.
  • Avoid mounting untrusted ext4 filesystem images on production systems.
  • Use isolated analysis hosts for corrupt or externally supplied filesystem images.
  • Prioritize systems that process removable media, disk images, or user-supplied storage.

Validation and detection

  • Inventory Linux hosts and record kernel versions in scope.
  • Check whether deployed kernels include the referenced stable commits or distro backports.
  • Identify workflows that mount external, corrupt, or user-supplied ext4 images.
  • Confirm remediation through vendor package metadata or kernel changelogs.
  • Document that the provided source bundle has no KEV or CVSS evidence.
Prepared
Confidence
medium
Sources
5

Public sources used

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-50306 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
4Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2, 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2, 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2unaffected
LinuxLinux5.10, 0, 5.15.87, 6.0.6, 6.1affected
Weakness

CWE details

No CWE listed

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