Bug 2373639 (CVE-2022-49991) - CVE-2022-49991 kernel: mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
Summary: CVE-2022-49991 kernel: mm/hugetlb: avoid corrupting page->mapping in hugetlb_...
Keywords:
Status: NEW
Alias: CVE-2022-49991
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-18 12:11 UTC by OSIDB Bzimport
Modified: 2025-08-27 13:19 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:14744 0 None None None 2025-08-27 11:39:57 UTC
Red Hat Product Errata RHSA-2025:14749 0 None None None 2025-08-27 13:19:54 UTC

Description OSIDB Bzimport 2025-06-18 12:11:47 UTC
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.

Comment 1 Avinash Hanwate 2025-06-18 23:34:10 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025061824-CVE-2022-49991-c44f@gregkh/T

Comment 6 errata-xmlrpc 2025-08-27 11:39:56 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2025:14744 https://access.redhat.com/errata/RHSA-2025:14744

Comment 7 errata-xmlrpc 2025-08-27 13:19:53 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2025:14749 https://access.redhat.com/errata/RHSA-2025:14749


Note You need to log in before you can comment on or make changes to this bug.