CVE-2026-99096
Last modified
CVE-2026-99096 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: io_uring/register: don't exempt disabled rings from task restrictions 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. Since commit ed82f35b926b ("io_uring: allow registration of per-task restrictions"), a ring also inherits restrictions from the task that creates it, and the same exemption applies to those.
Description
In the Linux kernel, the following vulnerability has been resolved: io_uring/register: don't exempt disabled rings from task restrictions 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. Since commit ed82f35b926b ("io_uring: allow registration of per-task restrictions"), 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. 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's allowed set. Per-ring restrictions registered on a disabled ring work as before. [axboe: amend with inheritance flag fixup]
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= ed82f35b926b2e505c14b7006473614b8f58b4f4, < f55c240192ded562386de843bfa067671d2731d5; >= ed82f35b926b2e505c14b7006473614b8f58b4f4, < 6da8f402e362b2f546e2efb7167fc9597aef6faf |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-99096?
How severe is CVE-2026-99096?
How do I fix CVE-2026-99096?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-99090In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99091In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99092In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99093In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99094In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-99095In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99097In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99098In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99099In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-9910Out of bounds memory access in ANGLE in Google Chrome prior …8.8
- CVE-2026-99100In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99101In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-99096?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
