CVE-2022-49468

thermal/core: Fix memory leak in __thermal_cooling_device_register()

MEDIUM

5.5

CVSS Score

Published: February 26, 2025 at 02:13 AM UTC

Updated: June 17, 2026 at 05:18 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.14 ≤ v < 5.10.1214.17 ≤ v < 5.10.1214.17 ≤ v < 5.15.464.17 ≤ v < 5.17.144.17 ≤ v < 5.18.34.17 ≤ v < 5.195.11 ≤ v < 5.15.465.16 ≤ v < 5.17.145.18 ≤ v < 5.18.34.178ea229511e06f9635ecc338dcbe0db41a73623f0

Vendor states this is fixed in 18530bedd221160823f63ccc20dd55c7a03edbcf (fixed)

Vendor states this is fixed in 21ccc58b671aea924f2481cf5c1cf0ebbfd3552d (fixed)

Vendor states this is fixed in 3802171f0b5b8b831f4ade5c827547cb323a5bb2 (fixed)

Vendor states this is fixed in 98a160e898c0f4a979af9de3ab48b4b1d42d1dbb (fixed)

Vendor states this is fixed in 9abdf0c0184230f0cb5c6685aabf33dda89aa9fb (fixed)

Vendor states this is fixed in 4.17 (unaffected)

Vendor states this is fixed in 5.10.121 (unaffected)

Vendor states this is fixed in 5.15.46 (unaffected)

Vendor states this is fixed in 5.17.14 (unaffected)

Vendor states this is fixed in 5.18.3 (unaffected)

Vendor states this is fixed in 5.19 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references