Security readout for executives and security teams
Plain-English summary
CVE-2022-50367 is a high-severity Linux kernel memory-safety flaw in NILFS metadata inode cleanup. A local user could trigger kernel memory corruption conditions; the description specifically notes crashes such as use-after-free or general protection faults. This is not listed as known exploited in KEV based on the provided data.
Executive priority
Treat as a high-priority routine kernel patching item, especially for multi-user and workload-dense Linux systems. There is no cited evidence of active exploitation, so emergency response is not indicated from the provided sources alone.
Technical view
The flaw occurs when inode_init_always() fails after security_inode_alloc(), leaving inode->i_private uninitialized. NILFS metadata inode detection can then cause nilfs_free_inode() to call nilfs_mdt_destroy() on that uninitialized pointer, causing UAF/GPF. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or vendor kernels without the referenced stable fixes. Risk is higher on systems where untrusted local users, workloads, or containers can exercise kernel filesystem paths. Distribution backports may change version-based conclusions, so package-level vendor status matters.
Exploitation context
The provided sources do not show active exploitation, and KEV status is false. Exploitation requires local privileges according to the CVSS vector. Public details describe the bug and fixes, but do not establish a weaponized exploit or remote attack path.
Researcher notes
The record maps to CWE-416 and Linux kernel stable commits. The affected-version data is broad and commit-based, so exact exposure should be confirmed through vendor kernel trees and backport metadata. Avoid assuming upstream version numbers alone reflect distro risk.
Mitigation direction
- Apply a Linux vendor kernel update that includes the upstream stable fix commits.
- Check distribution advisories for CVE-2022-50367 package status and backport notes.
- Prioritize shared servers, developer workstations, and container hosts with untrusted local workloads.
- Reboot systems after kernel updates to ensure the fixed kernel is running.
Validation and detection
- Inventory running kernel versions across Linux assets.
- Compare installed kernel packages against vendor advisories for CVE-2022-50367.
- Verify whether applied kernels include the referenced upstream stable commits or vendor backports.
- Confirm hosts rebooted into the updated kernel after patching.
- Review vulnerability scanner findings for distro backport awareness before accepting version-only results.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-416: 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.
Open ATT&CK lookupCVE-2022-50367 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/d1ff475d7c83289d0a7faef346ea3bbf90818badCVE reference, Linux
- https://git.kernel.org/stable/c/c0aa76b0f17f59dd9c9d3463550a2986a1d592e4CVE reference, Linux
- https://git.kernel.org/stable/c/ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48CVE reference, Linux
- https://git.kernel.org/stable/c/70e4f70d54e0225f91814e8610477d65f33cefe4CVE reference, Linux
- https://git.kernel.org/stable/c/1e555c3ed1fce4b278aaebe18a64a934cece57d8CVE reference, Linux
- https://git.kernel.org/stable/c/64b79e632869ad3ef6c098a4731d559381da1115CVE reference, Linux
- https://git.kernel.org/stable/c/81de80330fa6907aec32eb54c5619059e6e36452CVE reference, Linux
- https://git.kernel.org/stable/c/2a96b532098284ecf8e4849b8b9e5fc7a28bdee9CVE reference, Linux
- https://git.kernel.org/stable/c/2e488f13755ffbb60f307e991b27024716a33b29CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.