linux-kernel - Re: CVE-2022-49816: xen/pcpu: fix possible memory leak in register

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <917da057-adfd-4002-ad2b-f2a6ac3a00ee@suse.com>
Date: Thu, 1 May 2025 20:19:47 +0200
From: Jürgen Groß <jgross@...e.com>
To: cve@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: CVE-2022-49816: xen/pcpu: fix possible memory leak in
 register_pcpu()

On 01.05.25 16:10, Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman <gregkh@...nel.org>
> 
> Description
> ===========
> 
> In the Linux kernel, the following vulnerability has been resolved:
> 
> xen/pcpu: fix possible memory leak in register_pcpu()
> 
> In device_add(), dev_set_name() is called to allocate name, if it returns
> error, the 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().
> 
> The Linux kernel CVE team has assigned CVE-2022-49816 to this issue.

Please revoke this CVE.

The issue can in no way be triggered by an unprivileged user.

The memory leak could happen only either during boot of dom0, or when
hotplugging a physical CPU to a Xen server.


Juergen

Download attachment "OpenPGP_0xB0DE9DD628BF132F.asc" of type "application/pgp-keys" (3684 bytes)

Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (496 bytes)