cve/published/2022/CVE-2022-49468.mbox

From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2022-49468: thermal/core: Fix memory leak in __thermal_cooling_device_register()

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

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

thermal/core: Fix memory leak in __thermal_cooling_device_register()

I got memory leak as follows when doing fault injection test:

unreferenced object 0xffff888010080000 (size 264312):
  comm "182", pid 102533, jiffies 4296434960 (age 10.100s)
  hex dump (first 32 bytes):
    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........
    ff ff ff ff ff ff ff ff 40 7f 1f b9 ff ff ff ff  ........@.......
  backtrace:
    [<0000000038b2f4fc>] kmalloc_order_trace+0x1d/0x110 mm/slab_common.c:969
    [<00000000ebcb8da5>] __kmalloc+0x373/0x420 include/linux/slab.h:510
    [<0000000084137f13>] thermal_cooling_device_setup_sysfs+0x15d/0x2d0 include/linux/slab.h:586
    [<00000000352b8755>] __thermal_cooling_device_register+0x332/0xa60 drivers/thermal/thermal_core.c:927
    [<00000000fb9f331b>] devm_thermal_of_cooling_device_register+0x6b/0xf0 drivers/thermal/thermal_core.c:1041
    [<000000009b8012d2>] max6650_probe.cold+0x557/0x6aa drivers/hwmon/max6650.c:211
    [<00000000da0b7e04>] i2c_device_probe+0x472/0xac0 drivers/i2c/i2c-core-base.c:561

If device_register() fails, thermal_cooling_device_destroy_sysfs() need be called
to free the memory allocated in thermal_cooling_device_setup_sysfs().

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


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

	Issue introduced in 4.17 with commit 8ea229511e06f9635ecc338dcbe0db41a73623f0 and fixed in 5.10.121 with commit 18530bedd221160823f63ccc20dd55c7a03edbcf
	Issue introduced in 4.17 with commit 8ea229511e06f9635ecc338dcbe0db41a73623f0 and fixed in 5.15.46 with commit 21ccc58b671aea924f2481cf5c1cf0ebbfd3552d
	Issue introduced in 4.17 with commit 8ea229511e06f9635ecc338dcbe0db41a73623f0 and fixed in 5.17.14 with commit 3802171f0b5b8b831f4ade5c827547cb323a5bb2
	Issue introduced in 4.17 with commit 8ea229511e06f9635ecc338dcbe0db41a73623f0 and fixed in 5.18.3 with commit 9abdf0c0184230f0cb5c6685aabf33dda89aa9fb
	Issue introduced in 4.17 with commit 8ea229511e06f9635ecc338dcbe0db41a73623f0 and fixed in 5.19 with commit 98a160e898c0f4a979af9de3ab48b4b1d42d1dbb

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-49468
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:
	drivers/thermal/thermal_core.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/18530bedd221160823f63ccc20dd55c7a03edbcf
	https://git.kernel.org/stable/c/21ccc58b671aea924f2481cf5c1cf0ebbfd3552d
	https://git.kernel.org/stable/c/3802171f0b5b8b831f4ade5c827547cb323a5bb2
	https://git.kernel.org/stable/c/9abdf0c0184230f0cb5c6685aabf33dda89aa9fb
	https://git.kernel.org/stable/c/98a160e898c0f4a979af9de3ab48b4b1d42d1dbb