Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in huge memory/xarray handling. A local authenticated user could potentially exhaust resources and cause denial of service. The provided sources do not indicate data theft, data modification, remote exploitation, or active exploitation.
Executive priority
Handle through normal kernel patch management unless the environment has high-risk multi-user Linux systems. Business impact is availability-focused: a local low-privilege actor may be able to consume kernel memory. No source indicates active exploitation or confidentiality impact.
Technical view
The flaw is in mm/huge_memory. When xas_split_alloc() fails, xa_state is set to -ENOMEM, and xas_nomem() treats that as a request for more allocation rather than cleanup. The fix uses xas_destroy() to release xarray nodes. CVSS 3.1 is 5.5, with local, low-complexity, low-privilege availability impact.
Likely exposure
Systems running affected Linux kernel versions may be exposed, especially where untrusted local users or workloads share a host. The bundle lists Linux as affected around 5.17, 5.17.15, 5.18.4, and 5.19, but operators should confirm against their distribution kernel packages.
Exploitation context
The CVSS vector requires local access and low privileges, with no user interaction. The source bundle marks KEV as false and provides no evidence of public exploitation. Treat this as a local denial-of-service risk, not a confirmed remote compromise path.
Researcher notes
The key behavior is incorrect cleanup after xas_split_alloc() allocation failure during xarray entry splitting. The fix changes cleanup semantics by calling xas_destroy(). Evidence is limited to the CVE record and upstream stable commits; no exploitability details beyond CVSS are provided.
Mitigation direction
- Apply vendor or distribution kernel updates that include the referenced stable fixes.
- Prioritize shared Linux hosts with untrusted shell users, containers, or multi-tenant workloads.
- Check Linux vendor advisories before assuming upstream version strings match packaged kernels.
- Use existing local access controls to limit untrusted users on affected systems.
Validation and detection
- Inventory Linux kernel versions across servers, containers hosts, and appliances.
- Compare running kernels with vendor advisories and the referenced upstream commits.
- Confirm patched systems are booted into the updated kernel, not only installed.
- Review monitoring for unusual kernel memory pressure or local denial-of-service symptoms.
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-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.
Open ATT&CK lookupCVE-2022-49334 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
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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/c0c84962e297927ba57fd6ddc2bb000c9d149655CVE reference, Linux
- https://git.kernel.org/stable/c/95c8181b4947e000f3b9b8e5918d899fce77b93dCVE reference, Linux
- https://git.kernel.org/stable/c/69a37a8ba1b408a1c7616494aa7018e4b3844cbeCVE 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.
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.