Missing Release of Resource after Effective Lifetime 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-18908847
- published18 Aug 2026
- disclosed25 Jul 2026
Introduced: 25 Jul 2026
NewCVE-2026-64348 (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:
usb: free iso schedules on failed submit
EHCI and FOTG210 isochronous submits build an ehci_iso_sched before linking the URB to the endpoint queue, and keep the staged schedule in urb->hcpriv until iso_stream_schedule() and the link helpers consume it. If the controller is no longer accessible, or usb_hcd_link_urb_to_ep() fails, submit jumps to done_not_linked before that handoff happens and leaks the staged schedule still attached to urb->hcpriv.
Free the staged schedule from done_not_linked when submit fails before the URB is linked and clear urb->hcpriv after the free.
The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1.1.
An x86_64 allyesconfig build showed no new warnings. As we do not have an EHCI host controller with a USB isochronous device to test with, no runtime testing was able to be performed.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-64348
- https://git.kernel.org/stable/c/4bb88aee6b868cbf73bf453f62497802f5fe4769
- https://git.kernel.org/stable/c/6bc17a78a05671d303820224fb37ca339c1dc2cb
- https://git.kernel.org/stable/c/8890699eea19027ef6e4f9cbcf27cba5e789793f
- https://git.kernel.org/stable/c/b0d00d077f9738d215af9b50c74dffab7a1de19f
- https://git.kernel.org/stable/c/b9399d25fbb34a05bbe76eeedd730f62ff2670e9
- https://git.kernel.org/stable/c/be5004395dfd0b6ec310db359f887fa396fd0dd2