linux-cve-announce - CVE-2022-49836: siox: fix possible memory leak in siox_device

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: <2025050138-CVE-2022-49836-510d@gregkh>
Date: Thu,  1 May 2025 16:10:26 +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-49836: siox: fix possible memory leak in siox_device_add()

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

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

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

siox: fix possible memory leak in siox_device_add()

If device_register() returns error in siox_device_add(),
the name allocated by dev_set_name() need be freed. As
comment of device_register() says, it should use put_device()
to give up the reference in the error path. So fix this
by calling put_device(), then the name can be freed in
kobject_cleanup(), and sdevice is freed in siox_device_release(),
set it to null in error path.

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


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

	Issue introduced in 4.16 with commit bbecb07fa0af9a41507ce06d4631fdb3b5059417 and fixed in 4.19.267 with commit 0a5da069603ecc3d7aa09167450235462adaa295
	Issue introduced in 4.16 with commit bbecb07fa0af9a41507ce06d4631fdb3b5059417 and fixed in 5.4.225 with commit f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb
	Issue introduced in 4.16 with commit bbecb07fa0af9a41507ce06d4631fdb3b5059417 and fixed in 5.10.156 with commit a4b5423f88a17a36550ae8c16c46779b1ee42f4b
	Issue introduced in 4.16 with commit bbecb07fa0af9a41507ce06d4631fdb3b5059417 and fixed in 5.15.80 with commit 5d03c2911c529ea4d6ebfec53425f1091e8d402b
	Issue introduced in 4.16 with commit bbecb07fa0af9a41507ce06d4631fdb3b5059417 and fixed in 6.0.10 with commit d9c31e728843259209fb530c59995e4fe262699f
	Issue introduced in 4.16 with commit bbecb07fa0af9a41507ce06d4631fdb3b5059417 and fixed in 6.1 with commit 6e63153db50059fb78b8a8447b132664887d24e3

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-49836
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/siox/siox-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/0a5da069603ecc3d7aa09167450235462adaa295
	https://git.kernel.org/stable/c/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb
	https://git.kernel.org/stable/c/a4b5423f88a17a36550ae8c16c46779b1ee42f4b
	https://git.kernel.org/stable/c/5d03c2911c529ea4d6ebfec53425f1091e8d402b
	https://git.kernel.org/stable/c/d9c31e728843259209fb530c59995e4fe262699f
	https://git.kernel.org/stable/c/6e63153db50059fb78b8a8447b132664887d24e3