From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: cve@kernel.org, Jesper Dangaard Brouer <hawk@kernel.org>,
netdev@vger.kernel.org,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
wei.liu@kernel.org, paul@xen.org,
Jakub Kicinski <kuba@kernel.org>,
kirjanov@gmail.com, dkirjanov@suse.de,
kernel-team@cloudflare.com, security@xenproject.org,
xen-devel@lists.xenproject.org, George Dunlap <dunlapg@umich.edu>
Subject: Re: [PATCH net] xen-netfront: Add missing skb_mark_for_recycle
Date: Wed, 8 May 2024 20:33:10 +0100 [thread overview]
Message-ID: <2024050802-playful-brick-0c67@gregkh> (raw)
In-Reply-To: <9a2018c6-4efb-4bfe-b90f-531a072f0ef8@citrix.com>
On Tue, May 07, 2024 at 02:57:08PM +0100, Andrew Cooper wrote:
> Hello,
>
> Please could we request a CVE for "xen-netfront: Add missing
> skb_mark_for_recycle" which is 037965402a010898d34f4e35327d22c0a95cd51f
> in Linus' tree.
>
> This is a kernel memory leak trigger-able from unprivileged userspace.
>
> I can't see any evidence of this fix having been assigned a CVE thus far
> on the linux-cve-annouce mailing list.
CVE-2024-27393 is now created for this, thanks.
greg k-h
prev parent reply other threads:[~2024-05-08 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 12:14 [PATCH net] xen-netfront: Add missing skb_mark_for_recycle Jesper Dangaard Brouer
2024-03-28 22:31 ` Marek Marczykowski-Górecki
2024-03-29 1:30 ` patchwork-bot+netdevbpf
2024-03-29 9:47 ` Arthur Borsboom
2024-04-02 8:20 ` Arthur Borsboom
2024-04-02 20:25 ` Arthur Borsboom
[not found] ` <CAFLBxZaLKGgrZRUDMQ+kCAYKD7ypzsjO55mWvkZHtMTBxdw51A@mail.gmail.com>
2024-04-25 15:13 ` Greg KH
2024-05-07 13:57 ` Andrew Cooper
2024-05-08 19:33 ` 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=2024050802-playful-brick-0c67@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=cve@kernel.org \
--cc=dkirjanov@suse.de \
--cc=dunlapg@umich.edu \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kernel-team@cloudflare.com \
--cc=kirjanov@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@xen.org \
--cc=security@xenproject.org \
--cc=wei.liu@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).