LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49991: mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte In MCOPY_ATOMIC_CONTINUE case with a non-shared VMA, pages in the page cache are installed in the ptes. But hugepage_add_new_anon_rmap is called for them mistakenly because they're not vm_shared. This will corrupt the page->mapping used by page cache code.

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-49991 is a Linux kernel memory-management flaw involving huge pages. Under a specific huge-page copy path, the kernel can corrupt page-cache metadata. The public record does not provide CVSS, CWE, impact class, or confirmed exploitability, so business urgency depends on whether affected kernel versions are deployed and whether huge-page features are exposed.

Executive priority

Treat as a patch-management item with uncertain severity. It is kernel-level and can affect host stability or integrity, but the provided sources do not prove active exploitation or define business impact. Prioritize confirmation and vendor-backed updates over emergency response.

Technical view

The issue is in hugetlb_mcopy_atomic_pte. In MCOPY_ATOMIC_CONTINUE with a non-shared VMA, page-cache pages are installed into PTEs, but hugepage_add_new_anon_rmap is incorrectly called because the VMA is not VM_SHARED. That can corrupt page->mapping used by page-cache code.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds containing the vulnerable hugetlb code. The source lists Linux 5.13, 5.15.65, 5.19.6, and 6.0 as affected, but does not map every vendor kernel package.

Exploitation context

No source in the bundle reports active exploitation, and KEV is false. The issue appears tied to a specific kernel memory-management path involving huge pages and MCOPY_ATOMIC_CONTINUE. Public evidence does not establish remote exploitability, privilege impact, or practical attack conditions.

Researcher notes

The useful technical anchor is page->mapping corruption caused by the wrong rmap path in hugetlb_mcopy_atomic_pte. The bundle lacks CVSS, CWE, exploitability analysis, and downstream package mapping. Avoid assuming impact beyond kernel metadata corruption unless additional vendor analysis confirms it.

Mitigation direction

  • Review vendor kernel advisories for CVE-2022-49991 and matching package fixes.
  • Update affected Linux kernels to a vendor-supported build containing the stable fixes.
  • Prioritize hosts using huge pages, userfaultfd-related workflows, or untrusted local workloads.
  • If patch timing is unclear, ask the OS vendor for affected package ranges.

Validation and detection

  • Inventory running kernel versions across Linux hosts and containers with host kernel dependency.
  • Compare deployed kernels against vendor advisories and the referenced stable commits.
  • Identify systems using hugetlb or huge-page dependent workloads.
  • Record compensating controls only if vendor guidance supports them.
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-49991 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
LinuxLinuxf619147104c8ea71e120e4936d2b68ec11a1e527, f619147104c8ea71e120e4936d2b68ec11a1e527, f619147104c8ea71e120e4936d2b68ec11a1e527unaffected
LinuxLinux5.13, 0, 5.15.65, 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.