Amazon Linux 2 : kernel, --advisory ALAS2-2026-3862 (ALAS-2026-3862)

The version of kernel installed on the remote host is prior to 4.14.152-124.171. It is, therefore, affected by a vulnerability as referenced in the ALAS2-2026-3862 advisory. In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect...

Important: kernel

Issue Overview: In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect CVE-2026-64342 Affected Packages: kernel Note: This advisory is applicable to Amazon Linux 2 AL2 Core repository. Visit this FAQ section for the difference between...

CVE-2026-64341

A flaw was found in the Linux kernel's USB iowarrior driver. This vulnerability involves a use-after-free error, which occurs when the system attempts to use memory that has already been deallocated. This specific issue arises from a race condition during device disconnection, where the mutexunlo...

CVE-2026-64342

A flaw was found in the Linux kernel's USB iowarrior driver. This vulnerability, a use-after-free, occurs because write operations are not properly halted when a device disconnects. An attacker could potentially exploit this to cause system instability or execute arbitrary code...

SUSE CVE-2026-64341

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

SUSE CVE-2026-64342

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

CVE-2026-64341

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

CVE-2026-64342

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

UBUNTU-CVE-2026-64342

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

CVE-2026-64342

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

UBUNTU-CVE-2026-64341

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

CVE-2026-64341

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

EUVD-2026-48886

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

CVE-2026-64342

CVE-2026-64342 is a use-after-free vulnerability in the Linux kernel's iowarrior USB driver . Submitted write URBs are not stopped on close(), so they must be stopped unconditionally on disconnect() to prevent the completion handler from accessing freed memory. NVD scores it 7.8 HIGH (AV:L/AC:L/P...

CVE-2026-64342 USB: iowarrior: fix use-after-free on disconnect

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

CVE-2026-64342

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

CVE-2026-64342 USB: iowarrior: fix use-after-free on disconnect

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect Submitted write URBs are not stopped on close and therefore need to be stopped unconditionally on disconnect to avoid use-after-free in the completion handler...

EUVD-2026-48885

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

CVE-2026-64341 USB: iowarrior: fix use-after-free on disconnect race

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutexunlock may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly unlike spinlocks and refcounts. 12 Use ...

CVE-2026-64341

A use-after-free in the Linux kernel's USB iowarrior driver is triggered by a race between release() and disconnect(). Because mutex_unlock() is non-atomic, it may access a freed mutex structure after driver data is deallocated during disconnect. The fix replaces mutex-based lifetime management w...