Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the JFFS2 filesystem mount path. A local user with mount-related capability could trigger failed mount handling that leaves kernel memory allocated, potentially degrading availability. No source in the bundle shows active exploitation.
Executive priority
Treat as routine but time-bound kernel maintenance. Prioritize embedded or multi-user Linux systems where JFFS2 mounting is possible. This is not supported as an internet worm or data-theft issue by the supplied sources.
Technical view
CVE-2022-49381 is CWE-401 in JFFS2. When jffs2_iget() or d_make_root() fails inside jffs2_do_fill_super(), resources allocated by jffs2_sum_init() were not released. The fix calls jffs2_sum_exit() on those error paths. CVSS 3.1 is 5.5, local, low complexity, low privileges, availability impact high.
Likely exposure
Exposure is most relevant to Linux systems using or allowing mounting of JFFS2 filesystems, especially embedded, flash-storage, or appliance-style deployments. Internet-facing exposure is not indicated because the CVSS vector is local.
Exploitation context
The bundle does not cite public exploitation or KEV listing. Exploitation requires local access and low privileges according to the CVSS vector. The practical risk is availability degradation from leaked kernel memory during affected JFFS2 mount failure paths.
Researcher notes
The root cause is missing cleanup after jffs2_sum_init() allocation when later root inode or root dentry creation fails. Evidence is source-level and kernel-stable references only; no exploit proof, affected distributions, or operational workarounds are included in the bundle.
Mitigation direction
Update to a vendor kernel containing the referenced stable JFFS2 fix.
Check Linux distribution advisories for backported fixes before relying on version numbers alone.
Limit untrusted users from mounting filesystems until patched.
Review whether JFFS2 support is needed on affected systems.
Validation and detection
Inventory Linux kernel versions and vendor backport status.
Identify systems where JFFS2 is enabled or used operationally.
Confirm the kernel includes the stable commit fixing jffs2_do_fill_super cleanup.
Review monitoring for unusual memory pressure on systems handling JFFS2 mounts.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.