https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 29 Oct 2026 13:14:42 +0000 https://db.gcve.eu/vuln/cve-2026-99096 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/register: don&#39;t exempt disabled rings from task restrictions</p> <p>A ring created with IORING_SETUP_R_DISABLED is exempt from its register restrictions until it is enabled. This lets the creator register the restrictions and then enable the ring with IORING_REGISTER_ENABLE_RINGS, whether or not that opcode is in the allowed set.</p> <p>Since commit ed82f35b926b (&#34;io_uring: allow registration of per-task restrictions&#34;), a ring also inherits restrictions from the task that creates it, and the same exemption applies to those. A task whose register opcodes are restricted can therefore create a disabled ring, issue any register opcode on it, and then enable it.</p> <p>Mark rings whose restrictions were inherited from the task, and keep checking register opcodes for them while the ring is disabled. Enabling such a ring now requires IORING_REGISTER_ENABLE_RINGS to be in the task&#39;s allowed set. Per-ring restrictions registered on a disabled ring work as before.</p> <p>[axboe: amend with inheritance flag fixup]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>io_uring/register: don&#39;t exempt disabled rings from task restrictions</p> <p>A ring created with IORING_SETUP_R_DISABLED is exempt from its register restrictions until it is enabled. This lets the creator register the restrictions and then enable the ring with IORING_REGISTER_ENABLE_RINGS, whether or not that opcode is in the allowed set.</p> <p>Since commit ed82f35b926b (&#34;io_uring: allow registration of per-task restrictions&#34;), a ring also inherits restrictions from the task that creates it, and the same exemption applies to those. A task whose register opcodes are restricted can therefore create a disabled ring, issue any register opcode on it, and then enable it.</p> <p>Mark rings whose restrictions were inherited from the task, and keep checking register opcodes for them while the ring is disabled. Enabling such a ring now requires IORING_REGISTER_ENABLE_RINGS to be in the task&#39;s allowed set. Per-ring restrictions registered on a disabled ring work as before.</p> <p>[axboe: amend with inheritance flag fixup]</p> https://db.gcve.eu/vuln/cve-2026-99096