All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>, cve@kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>
Subject: proposed io_uring CVEs for 7.3.2
Date: Thu, 19 Nov 2026 15:19:28 +0100	[thread overview]
Message-ID: <2026111949-tinker-symptom-4279@gregkh> (raw)
In-Reply-To: <2026111722-unfocused-ride-065c@gregkh>

On Tue, Nov 17, 2026 at 08:42:31AM +0100, Greg Kroah-Hartman wrote:
> How about we make the "rule" that we don't assign any kernel CVEs to
> io_uring things unless you ask for us to?  We do this already with the
> xen portions of the kernel, but it requires you to remember to ask us
> for an id "manually" if you want one.

Along these lines, here is a list of git ids that our initial review
pass marked as "should be given a CVE id".  Any opinions on how far off
it is, and if we should assign these or not?

  3de16279b43d io_uring: defer foreign io-wq enqueues to task_work
  360395e8dbf9 io_uring/sqpoll: don't wait for the thread to exit
  9f5315d3f436 io_uring: free the task context after a grace period
  8543a39f03db io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
  51bab09b7ca1 io_uring: free XArray nodes left by a failed store
  0b34e7b20a48 io_uring: charge tctx nodes and personalities
  075d5837bafc io_uring/rsrc: charge buffer arrays and nodes to memcg
  4a93427e99a8 io_uring/register: enforce per-task restrictions in io_uring_register_blind()
  e66907c3ba22 io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
  37e425460b7c io_uring/io-wq: save worker type before dropping its reference
  b42c85c20d84 exec: cancel io_uring requests before de_thread()
  3eff68bce255 io_uring/futex: allocate private hash before waiting
  5cb049d2203d io_uring: don't lose a cancel as io-wq parks a request
  8257f6ec45ee io_uring: don't lose the DEFER_TASKRUN wake up

thanks,

greg k-h


  parent reply	other threads:[~2026-11-19 14:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 23:22 Subject: io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04) dev
2026-11-14  2:00 ` Greg KH
2026-11-15  1:13   ` dev
2026-11-14 17:42 ` Sasha Levin
2026-11-14 18:12   ` Jens Axboe
2026-11-16  9:52     ` Greg Kroah-Hartman
2026-11-17  2:21       ` Jens Axboe
2026-11-17  7:42         ` Greg Kroah-Hartman
2026-11-17 12:41           ` Jens Axboe
2026-11-19 14:19           ` Greg Kroah-Hartman [this message]
2026-11-19 15:32             ` proposed io_uring CVEs for 7.3.2 Greg Kroah-Hartman
2026-11-19 17:40               ` Jens Axboe
2026-11-19 23:54                 ` Sasha Levin
2026-11-20  6:58                 ` Greg Kroah-Hartman
2026-11-19 17:39             ` Jens Axboe
2026-11-19 23:55               ` Sasha Levin
2026-11-20  7:01               ` Greg Kroah-Hartman
2026-11-17 12:42         ` io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04) Sasha Levin
2026-11-17 12:45           ` Jens Axboe
2026-11-17 12:59             ` Sasha Levin
2026-11-19 18:10               ` Jens Axboe
2026-11-19 20:39                 ` Sasha Levin
2026-11-19 23:25                   ` Jens Axboe
2026-11-20  5:17                     ` Greg Kroah-Hartman
2026-11-20 20:39                       ` Sasha Levin

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=2026111949-tinker-symptom-4279@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=cve@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=sashal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.