mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2022-49816: xen/pcpu: fix possible memory leak in register_pcpu()
Date: Fri, 2 May 2025 07:35:45 +0200	[thread overview]
Message-ID: <2025050238-gents-policy-dc22@gregkh> (raw)
In-Reply-To: <917da057-adfd-4002-ad2b-f2a6ac3a00ee@suse.com>

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

      reply	other threads:[~2025-05-02  5:35 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ß
2025-05-02  5:35   ` Greg KH [this message]

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=2025050238-gents-policy-dc22@gregkh \
    --to=greg@kroah.com \
    --cc=cve@kernel.org \
    --cc=jgross@suse.com \
    --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®