Excessive Platform Resource Consumption within a Loop Affecting kernel6.18-tools-debuginfo package, versions <1:6.18.39-79.141.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-AMZN2023-KERNEL618TOOLSDEBUGINFO-18908917
- published18 Aug 2026
- disclosed25 Jul 2026
Introduced: 25 Jul 2026
NewCVE-2026-64425 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 kernel6.18-tools-debuginfo to version 1:6.18.39-79.141.amzn2023 or higher.
This issue was patched in ALAS2023-2026-2045.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel6.18-tools-debuginfo package and not the kernel6.18-tools-debuginfo package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item
commit 10dc95939817 ("io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop") fixed the obvious case where io_worker_handle_work() took one exit-bit snapshot before draining pending work, but the fix stops one level too early.
io_worker_handle_work() now re-checks IO_WQ_BIT_EXIT in its outer work run loop, yet it still snapshots that bit once before processing a whole dependent linked-work chain. If io_wq_exit_start() sets IO_WQ_BIT_EXIT after the first linked item has started, the remaining linked items can still reuse stale do_kill = false, skip IO_WQ_WORK_CANCEL, and continue running after exit has begun.
Move the check further inside, so it covers linked items too. Note: this is a syzbot special as it loves setting up tons of slow linked work on weird devices like msr that take forever to read, and immediately close the ring. Exit then takes a long time.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-64425
- https://git.kernel.org/stable/c/14b7ecad2ec56699325180a744f4b19f046401bb
- https://git.kernel.org/stable/c/1636d85dc139b07c0449308f2bb5e0c7a2e0da99
- https://git.kernel.org/stable/c/29bef9934b2521f787bb15dd1985d4c0d12ae02a
- https://git.kernel.org/stable/c/6e2f51f3e06773c2ee98ad09738f0908b48f76f9
- https://git.kernel.org/stable/c/ab85765cbe3258b43dc6729af0e6ce3a87a133d8
- https://git.kernel.org/stable/c/b6f179a653a934736c88d820fe0098c3c2532549
- https://git.kernel.org/stable/c/d179533c610e1b4c6aa436e3c1fd1b719d2c727c
- https://git.kernel.org/stable/c/ea61b04e1d7242cb37f5ed2cc91cf21a493f6597