Public bug reported:

Release: Ubuntu 26.04 LTS (resolute), Canonical's official AWS images
(ami-0547ecbf0e9b4aeb5 x86_64, ami-06b1a03fa3561aefb arm64, us-east-1).

Package: linux-aws 7.0.0-1016.17. uname -rv:
  - x86_64: 7.0.0-1016-aws #17-Ubuntu SMP PREEMPT Mon Oct 19 17:36:33 UTC 2026
  - arm64:  7.0.0-1016-aws #17-Ubuntu SMP PREEMPT Mon Oct 19 17:54:18 UTC 2026

Expected: a registered io_uring eventfd becomes readable each time that
deferred task work is queued, as on Debian 12's 6.1 kernel and on
kernels that have 04fe9aeb4f3c.

What happened: the eventfd becomes readable for the first deferred task
work only. Later task work never signals it, and poll() on it blocks
until io_uring_enter(IORING_ENTER_GETEVENTS) runs the work.

apport: the affected systems were short-lived EC2 instances, so apport-
collect is not available. The cause is in the kernel source, as
described below.

---

Upstream report:
https://lore.kernel.org/stable/oMhla8VwCWoihfrmgn8znIy60W1QXI8g_v2OyB9i6sWESIDlVJlwoGGOLylJgIHRARNoieXUVRGqzeB__KvHMdXgnCfPPovs8vLMOzaMPEw=@rebasedinc.com/T/#u

---

While working on my own async runtime on io_uring, I found what looks
like a defect in the stable backports. I first saw it on Ubuntu 26.04's
kernel, and I can't find any existing report of it.

A registered io_uring eventfd stops signaling after its first deferred
signal on kernels that carry the backport of cd305ee3633a ("io_uring:
defer eventfd signaling when queued from a wakeup handler") but not
04fe9aeb4f3c ("io_uring/eventfd: reset deferred signal state").

What I see, on Ubuntu 26.04 7.0.0-1016-aws, x86_64 and arm64. Ubuntu's
7.0 kernel took the cd305ee3633a backport through the 6.18.49 stable
update:

1. A ring with IORING_SETUP_SINGLE_ISSUER | IORING_SETUP_DEFER_TASKRUN | 
IORING_SETUP_TASKRUN_FLAG, and an eventfd registered with 
IORING_REGISTER_EVENTFD.
2. Two IORING_OP_RECV on a nonblocking TCP socket. Each gets -EAGAIN, arms 
poll, and later has data.
3. The first receive's task work signals the eventfd. For the second, tracing 
shows io_uring_task_add, but the eventfd never becomes readable, and poll() on 
it blocks.
4. io_uring_enter with IORING_ENTER_GETEVENTS then runs the work and posts the 
completion.

Debian 12's 6.1 kernel does not show this.

What I THINK is going on (I read the source, w/ help from Opus 5.5;
please correct me if I'm wrong): after cd305ee3633a, task work queued
from a poll wakeup signals through the deferred path, which sets
IO_EVENTFD_OP_SIGNAL_BIT. Without 04fe9aeb4f3c, io_eventfd_do_signal()
never clears that bit, so each later deferred signal is skipped.

Where it applies: cd305ee3633a is in 6.18.49 and 6.12.114. 04fe9aeb4f3c
(Fixes: 60b6c075e8eb, in v7.1, no stable tag) is in neither branch, and
I didn't find a copy in the stable queue. I read this in the source of
the linux-6.18.y and linux-6.12.y heads, but I didn't run those kernels.

If this is correct, a backport of 04fe9aeb4f3c to 6.18.y and 6.12.y
looks like the right fix; it keeps the CVE-2026-80920 fix in place. The
6.12.y code differs, so it may need a small change. I will obviously
leave the fix to you, but I'm happy to test a candidate on the affected
Ubuntu kernel.

Thanks,

Nathan - Founder, Lead Developer @ Rebased, Inc.

---

Affected:
linux-aws 7.0.0-1016.17 and 7.0.0-1018.19 (-proposed). linux master-next 
7.0.0-44.44 also lacks the clear. cd305ee3633a arrived in linux 7.0.0-39.39 
("Upstream stable to v6.18.49, v7.1.13"). 04fe9aeb4f3c reached v7.1 in the main 
release, not in a 7.1.y update, so the stable updates didn't carry it.

** Affects: linux-aws (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: resolute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2174458

Title:
  io_uring: registered eventfd signals only once after the cd305ee3633a
  backport (7.0.0-1016-aws)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2174458/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to