SUSE CVE-2026-43493

In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix handling of MAYBACKLOG requests MAYBACKLOG requests can return EBUSY. Handle them by checking for that value and filtering out EINPROGRESS notifications...

CVE-2026-43493

A flaw was found in the Linux kernel's pcrypt component. This vulnerability involves how the system handles certain requests, specifically MAYBACKLOG requests, which can indicate a temporary busy state. If not properly managed, the system's processing of these requests could lead to resource...

CVE-2026-43493

In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix handling of MAYBACKLOG requests MAYBACKLOG requests can return EBUSY. Handle them by checking for that value and filtering out EINPROGRESS notifications...

PT-2026-41875

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the pcrypt crypto component regarding the handling of MAY BACKLOG requests. These requests can return an EBUSY error, which requires proper handling by checking for th...

CVE-2026-31719

CVE-2026-31719 concerns the Linux kernel crypto/krb5enc async decrypt path where the skcipher completion could bypass the hash verification, bypassing integrity checks. The root cause is krb5enc_dispatch_decrypt() signaling completion without invoking krb5enc_dispatch_decrypt_hash(). The fix adds...

Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-013560)

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013560 advisory. In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Handle EBUSY correctly As it is essiv only handles the special return value of...

Unity Linux 20.1070a Security Update: kernel (UTSA-2026-005777)

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-005777 advisory. In the Linux kernel, the following vulnerability has been resolved: crypto: xts - Handle EBUSY correctly As it is xts only handles the special return value of...

Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992532)

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992532 advisory. In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special return value of...

UBUNTU-CVE-2023-54046

In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Handle EBUSY correctly As it is essiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller of essiv may specify...

kernel: crypto: seqiv - Handle EBUSY correctly

In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller of seqiv may specify...

kernel: crypto: seqiv - Handle EBUSY correctly

In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request. However, as the caller of seqiv may specify...

CVE-2023-53494 crypto: xts - Handle EBUSY correctly

In the Linux kernel, the following vulnerability has been resolved: crypto: xts - Handle EBUSY correctly As it is xts only handles the special return value of EINPROGRESS, which means that in all other cases it will free data related to the request. However, as the caller of xts may specify...

CVE-2023-53373

CVE-2023-53373 in the Linux kernel affects the crypto/seqiv path. The vulnerability arises because seqiv only handles EINPROGRESS and does not account for EBUSY, risking a use-after-free for backlogged requests. The fix is to treat EBUSY the same as EINPROGRESS, preventing premature data free on ...