LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49343: ext4: avoid cycles in directory h-tree

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid cycles in directory h-tree A maliciously corrupted filesystem can contain cycles in the h-tree stored inside a directory. That can easily lead to the kernel corrupting tree nodes that were already verified under its hands while doing a node split and consequently accessing unallocated memory. Fix the problem by verifying traversed block numbers are unique.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A maliciously corrupted ext4 filesystem can confuse the Linux kernel into revisiting directory index blocks during an update. This may cause access to unallocated memory, potentially crashing the system or compromising confidentiality and integrity. An attacker must get a victim to interact with a crafted filesystem, so exposure is concentrated around removable media, disk images, and other untrusted storage.

Executive priority

Prioritize patching systems that routinely handle untrusted storage or disk images. Treat general-purpose systems as a scheduled high-severity kernel update, with faster action where crafted filesystems can reach privileged infrastructure. There is no supplied evidence of active exploitation, so urgency should be exposure-driven rather than incident-driven.

Technical view

Cycles in an ext4 directory h-tree can cause previously verified nodes to be corrupted during a node split, followed by access to unallocated memory. The fix verifies that traversed block numbers are unique. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high potential impact.

Likely exposure

Potentially exposed systems run an affected Linux kernel and process attacker-influenced ext4 filesystems. Higher-risk environments include those handling untrusted removable storage or filesystem images. The supplied affected-version data is unusual and incomplete for distribution-specific kernels, so administrators should confirm status with their Linux vendor rather than rely solely on upstream version strings.

Exploitation context

The supplied record reports no CISA KEV listing and provides no cited evidence of active exploitation. Exploitation requires a maliciously corrupted ext4 filesystem plus victim interaction. The exact interaction necessary and the practical reliability of achieving confidentiality, integrity, or availability impact are not established by the supplied sources.

Researcher notes

The vulnerable path involves cyclic block references in an ext4 directory h-tree during node splitting. Upstream remediation checks traversed block-number uniqueness. Eight stable-kernel commit references are supplied, indicating branch-specific backports. No CWE, proof of concept, exploit telemetry, or distribution-package mapping is provided; researchers should avoid inferring exploitability beyond the documented unallocated-memory access.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable upstream stable fix.
  • Reboot systems after updating so the corrected kernel is running.
  • Restrict attachment or processing of untrusted filesystem images and removable media until patched.
  • Consult the Linux distribution vendor for backport and package status.

Validation and detection

  • Inventory running kernels on systems that can process ext4 filesystems.
  • Check vendor advisories or package changelogs for CVE-2022-49343 coverage.
  • Confirm the running kernel after reboot matches the patched package.
  • Review workflows that accept removable media, disk images, or other attacker-controlled storage.
Prepared
Confidence
high
Sources
10

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-49343 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-49343Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinuxac27a0ec112a089f1a5102bc8dffc79c8c815571, ac27a0ec112a089f1a5102bc8dffc79c8c815571, ac27a0ec112a089f1a5102bc8dffc79c8c815571, ac27a0ec112a089f1a5102bc8dffc79c8c815571, ac27a0ec112a089f1a5102bc8dffc79c8c815571, ac27a0ec112a089f1a5102bc8dffc79c8c815571, ac27a0ec112a089f1a5102bc8dffc79c8c815571, ac27a0ec112a089f1a5102bc8dffc79c8c815571unaffected
LinuxLinux2.6.19, 0, 4.14.283, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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