linux-cve-announce - CVE-2022-49994: bootmem: remove the vmemmap pages from kmemleak in put_page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025061825-CVE-2022-49994-e212@gregkh>
Date: Wed, 18 Jun 2025 13:00:59 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49994: bootmem: remove the vmemmap pages from kmemleak in put_page_bootmem

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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:

The Linux kernel CVE team has assigned CVE-2022-49994 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.14 with commit f41f2ed43ca5258d70d53290d1951a21621f95c8 and fixed in 5.15.64 with commit 16a12ee619e39e8112f61b603255c16b73b6264b
	Issue introduced in 5.14 with commit f41f2ed43ca5258d70d53290d1951a21621f95c8 and fixed in 5.19.6 with commit 9ae15c4ba2be1e5a62503b6d873e84beb5fcbb5a
	Issue introduced in 5.14 with commit f41f2ed43ca5258d70d53290d1951a21621f95c8 and fixed in 6.0 with commit dd0ff4d12dd284c334f7e9b07f8f335af856ac78

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-49994
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	mm/bootmem_info.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/16a12ee619e39e8112f61b603255c16b73b6264b
	https://git.kernel.org/stable/c/9ae15c4ba2be1e5a62503b6d873e84beb5fcbb5a
	https://git.kernel.org/stable/c/dd0ff4d12dd284c334f7e9b07f8f335af856ac78