From: "Jürgen Groß" <jgross@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2022-49816: xen/pcpu: fix possible memory leak in register_pcpu()
Date: Thu, 1 May 2025 20:19:47 +0200 [thread overview]
Message-ID: <917da057-adfd-4002-ad2b-f2a6ac3a00ee@suse.com> (raw)
In-Reply-To: <2025050131-CVE-2022-49816-0190@gregkh>
[-- 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 --]
next parent reply other threads:[~2025-05-01 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025050131-CVE-2022-49816-0190@gregkh>
2025-05-01 18:19 ` Jürgen Groß [this message]
2025-05-02 5:35 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=917da057-adfd-4002-ad2b-f2a6ac3a00ee@suse.com \
--to=jgross@suse.com \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®