* Re: CVE-2022-49816: xen/pcpu: fix possible memory leak in register_pcpu()
[not found] <2025050131-CVE-2022-49816-0190@gregkh>
@ 2025-05-01 18:19 ` Jürgen Groß
2025-05-02 5:35 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: Jürgen Groß @ 2025-05-01 18:19 UTC (permalink / raw)
To: cve, linux-kernel
[-- Attachment #1.1.1: Type: text/plain, Size: 879 bytes --]
On 01.05.25 16:10, Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman <gregkh@kernel.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
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: CVE-2022-49816: xen/pcpu: fix possible memory leak in register_pcpu()
2025-05-01 18:19 ` CVE-2022-49816: xen/pcpu: fix possible memory leak in register_pcpu() Jürgen Groß
@ 2025-05-02 5:35 ` Greg KH
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2025-05-02 5:35 UTC (permalink / raw)
To: Jürgen Groß; +Cc: cve, linux-kernel
On Thu, May 01, 2025 at 08:19:47PM +0200, Jürgen Groß wrote:
> On 01.05.25 16:10, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman <gregkh@kernel.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.
Now rejected, thanks.
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-05-02 5:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <2025050131-CVE-2022-49816-0190@gregkh>
2025-05-01 18:19 ` CVE-2022-49816: xen/pcpu: fix possible memory leak in register_pcpu() Jürgen Groß
2025-05-02 5:35 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®