LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49442: drivers/base/node.c: fix compaction sysfs file leak

In the Linux kernel, the following vulnerability has been resolved: drivers/base/node.c: fix compaction sysfs file leak Compaction sysfs file is created via compaction_register_node in register_node. But we forgot to remove it in unregister_node. Thus compaction sysfs file is leaked. Using compaction_unregister_node to fix this issue.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49442 is a Linux kernel issue where a sysfs file related to memory compaction is not removed when a node is unregistered. The public record does not provide CVSS, impact metrics, or active exploitation evidence. Treat it as a kernel hygiene and stability risk until your Linux vendor maps it to shipped packages.

Executive priority

Handle through normal kernel patch management unless vendor intelligence raises impact. There is no sourced evidence of active exploitation or severe impact, but kernel defects can affect critical infrastructure and should not be ignored indefinitely.

Technical view

The issue is in drivers/base/node.c. compaction_register_node creates a compaction sysfs file during register_node, but unregister_node did not remove it. The resolved change adds the matching compaction_unregister_node cleanup. The record lists Linux kernel versions and stable commit references, but no CWE, CVSS vector, or exploitation details.

Likely exposure

Exposure is limited to Linux systems running affected kernel code paths. The record lists Linux as affected across multiple kernel versions and stable branches, but does not identify distributions, appliances, cloud images, or package names. Organizations should map kernel package versions through their OS vendor advisories.

Exploitation context

The source bundle does not report active exploitation, public exploit code, or CISA KEV listing. The described condition is a sysfs file leak during node unregister handling, so validation should focus on patch presence and vendor package status, not offensive testing.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or distribution-specific fixed versions are provided. The key technical artifact is the cleanup mismatch in drivers/base/node.c and the stable commit set adding compaction_unregister_node on unregister.

Mitigation direction

  • Update to a vendor kernel containing the matching stable fix for your branch.
  • Track Linux distribution advisories for package-level fixed versions.
  • Prioritize systems using memory hotplug, NUMA, or node lifecycle operations.
  • Avoid ad hoc kernel patching unless your kernel vendor supports it.
  • Document compensating operational monitoring if patching must be deferred.

Validation and detection

  • Inventory running kernel versions across servers, images, and appliances.
  • Compare kernel packages against vendor advisories and listed stable commits.
  • Confirm patched source calls compaction_unregister_node during node unregister cleanup.
  • Check vulnerability scanners for CVE mapping accuracy against distro backports.
  • Record exceptions where vendor status remains unavailable or ambiguous.
Prepared
Confidence
medium
Sources
11

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-49442 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
10Source 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
LinuxLinuxed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307, ed4a6d7f0676db50b5023cc01f6cda82a2f2a307unaffected
LinuxLinux2.6.35, 0, 4.9.318, 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.