LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49994: bootmem: remove the vmemmap pages from kmemleak in put_page_bootmem

In the Linux kernel, the following vulnerability has been resolved: bootmem: remove the vmemmap pages from kmemleak in put_page_bootmem The vmemmap pages is marked by kmemleak when allocated from memblock. Remove it from kmemleak when freeing the page. Otherwise, when we reuse the page, kmemleak may report such an error and then stop working. kmemleak: Cannot insert 0xffff98fb6eab3d40 into the object search tree (overlaps existing) kmemleak: Kernel memory leak detector disabled kmemleak: Object 0xffff98fb6be00000 (size 335544320): kmemleak: comm "swapper", pid 0, jiffies 4294892296 kmemleak: min_count = 0 kmemleak: count = 0 kmemleak: flags = 0x1 kmemleak: checksum = 0 kmemleak: backtrace:

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause the kernel memory leak detector, kmemleak, to disable itself after reporting overlapping tracked objects. The cited material frames the impact as diagnostic failure, not system compromise. No CVSS score, CWE, or active exploitation evidence is provided.

Executive priority

Treat this as a targeted kernel maintenance item unless vendor guidance raises severity. It is not supported by the sources as actively exploited or broadly business-critical, but it can weaken kernel debugging and memory-leak detection assurance.

Technical view

The fix removes vmemmap pages from kmemleak tracking when put_page_bootmem frees them. Without that cleanup, later page reuse can overlap an existing kmemleak object entry, triggering an error and disabling kmemleak.

Likely exposure

Exposure appears limited to Linux kernels listed as affected in the CVE source bundle, especially environments using kmemleak for kernel memory leak detection. The affected version data is incomplete and should be verified against vendor kernel packages.

Exploitation context

The source bundle does not identify an exploit path, attacker requirements, public exploitation, or CISA KEV listing. The described behavior is a reliability problem in kernel diagnostic tooling rather than a documented privilege or remote-code-execution issue.

Researcher notes

Evidence is narrow: the record describes a resolved Linux kernel kmemleak bookkeeping bug and references three stable commits. There is no CVSS vector, CWE mapping, exploit description, or complete vendor-specific affected/fixed matrix in the provided bundle.

Mitigation direction

  • Check Linux vendor advisories for your exact kernel build and backport status.
  • Prioritize update planning for systems that rely on kmemleak diagnostics.
  • Review referenced stable kernel commits when validating source-built kernels.
  • Track distribution security notices for package-specific fixed versions.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Confirm whether kmemleak is enabled or used in affected environments.
  • Compare deployed kernel sources against the referenced stable commits.
  • Monitor kernel logs for kmemleak overlap errors or kmemleak disabling itself.
Prepared
Confidence
medium
Sources
5

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-49994 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
4Source 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
LinuxLinuxf41f2ed43ca5258d70d53290d1951a21621f95c8, f41f2ed43ca5258d70d53290d1951a21621f95c8, f41f2ed43ca5258d70d53290d1951a21621f95c8unaffected
LinuxLinux5.14, 0, 5.15.64, 5.19.6, 6.0affected
Weakness

CWE details

No CWE listed

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