CVE-2026-46274
Last modified
CVE-2026-46274 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: io-wq: check that the predecessor is hashed in io_wq_remove_pending() io_wq_remove_pending() needs to fix up wq->hash_tail[] if the cancelled work was the tail of its hash bucket. When doing this, it checks whether the preceding entry in acct->work_list has the same hash value, but never checks that the predecessor is hashed at all. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: io-wq: check that the predecessor is hashed in io_wq_remove_pending() io_wq_remove_pending() needs to fix up wq->hash_tail[] if the cancelled work was the tail of its hash bucket. When doing this, it checks whether the preceding entry in acct->work_list has the same hash value, but never checks that the predecessor is hashed at all. io_get_work_hash() is simply atomic_read(&work->flags) >> IO_WQ_HASH_SHIFT, and the hash bits are never set for non-hashed work, so it returns 0. Thus, when a hashed bucket-0 work is cancelled while a non-hashed work is its list predecessor, the check spuriously passes and a pointer to the non-hashed io_kiocb is stored in wq->hash_tail[0]. Because non-hashed work is dequeued via the fast path in io_get_next_work(), which never touches hash_tail[], the stale pointer is never cleared. Therefore, after the non-hashed io_kiocb completes and is freed back to req_cachep, wq->hash_tail[0] is a dangling pointer. The io_wq is per-task (tctx->io_wq) and survives ring open/close, so the dangling pointer persists for the lifetime of the task; the next hashed bucket-0 enqueue dereferences it in io_wq_insert_work() and wq_list_add_after() writes through freed memory. Add the missing io_wq_is_hashed() check so a non-hashed predecessor never inherits a hash_tail[] slot.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.8.6, < 5.9 | — |
| Linux | Linux Kernel | >= 5.9.1, < 6.6.141 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.91 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.33 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 | — |
| Linux | Linux Kernel | 5.9 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-46274?
How severe is CVE-2026-46274?
How do I fix CVE-2026-46274?
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-46269In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4627A vulnerability was found in D-Link DIR-825 and DIR-825R 1.0…8.6
- CVE-2026-46270In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-46271In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46272In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-46273In the Linux kernel, the following vulnerability has been re…8.6
- CVE-2026-46275In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46276In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46277In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46278In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46279In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-4628A flaw was found in Keycloak. An improper Access Control vul…4.3
Are you affected by CVE-2026-46274?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
