linux-cve-announce - CVE-2022-49190: kernel/resource: fix kfree() of bootmem memory again

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: <2025022616-CVE-2022-49190-3c68@gregkh>
Date: Wed, 26 Feb 2025 02:56:35 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49190: kernel/resource: fix kfree() of bootmem memory again

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

In the Linux kernel, the following vulnerability has been resolved:

kernel/resource: fix kfree() of bootmem memory again

Since commit ebff7d8f270d ("mem hotunplug: fix kfree() of bootmem
memory"), we could get a resource allocated during boot via
alloc_resource().  And it's required to release the resource using
free_resource().  Howerver, many people use kfree directly which will
result in kernel BUG.  In order to fix this without fixing every call
site, just leak a couple of bytes in such corner case.

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


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

	Issue introduced in 3.10 with commit ebff7d8f270d045338d9f4796014f4db429a17f9 and fixed in 5.15.33 with commit a9e88c2618d228d7a4e7e515cf30dc0d0d813f27
	Issue introduced in 3.10 with commit ebff7d8f270d045338d9f4796014f4db429a17f9 and fixed in 5.16.19 with commit d7faa04a44a0c37ac3d222fa8e0bdcbfcee9c0c8
	Issue introduced in 3.10 with commit ebff7d8f270d045338d9f4796014f4db429a17f9 and fixed in 5.17.2 with commit ab86020070999e758ce2e60c4348f20bf7ddba56
	Issue introduced in 3.10 with commit ebff7d8f270d045338d9f4796014f4db429a17f9 and fixed in 5.18 with commit 0cbcc92917c5de80f15c24d033566539ad696892

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-49190
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:
	kernel/resource.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/a9e88c2618d228d7a4e7e515cf30dc0d0d813f27
	https://git.kernel.org/stable/c/d7faa04a44a0c37ac3d222fa8e0bdcbfcee9c0c8
	https://git.kernel.org/stable/c/ab86020070999e758ce2e60c4348f20bf7ddba56
	https://git.kernel.org/stable/c/0cbcc92917c5de80f15c24d033566539ad696892