CVE-2026-97594

The Linux kernel contains a use-after-free vulnerability in the landlock LSM. The current_check_refer_path() function reads old_dentry->d_parent without holding a reference or lock, leading to a race condition during filename_linkat(). Because hook_path_link() does not lock the parent, a concu...

EUVD-2026-86902

In the Linux kernel, the following vulnerability has been resolved: landlock: Fix use-after-free of the source's parent directory currentcheckreferpath reads olddentry-dparent without holding a reference nor a lock on it, and then dereferences it in collectdomainaccesses and in the audit record. ...

CVE-2026-97594 landlock: Fix use-after-free of the source's parent directory

In the Linux kernel, the following vulnerability has been resolved: landlock: Fix use-after-free of the source's parent directory currentcheckreferpath reads olddentry-dparent without holding a reference nor a lock on it, and then dereferences it in collectdomainaccesses and in the audit record. ...

CVE-2026-97593

The Linux kernel contains a NULL pointer dereference vulnerability in the iommu/s390 component. When using a 5-level translation table via ZPCI_TABLE_TYPE_RFX , the function get_rto_from_iova() fails to verify if the region-second origin rso is non-NULL before accessing rso[rsx] . This occurs bec...

EUVD-2026-86900

In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm In function ctraescrypt there is a buffer used to process remaining bytes AESBLOCKSIZE. This buffer was not scrubbed and thus could lead to expose of...

EUVD-2026-86901

In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Fix NULL dereference in iovatophys with ZPCITABLETYPERFX When using a 5-level translation table via ZPCITABLETYPERFX getrsofromiova returns NULL when the region-first entry is invalid. Yet in getrtofromiova the...

CVE-2026-97592

The Linux kernel contains a vulnerability in the s390/crypto component related to the AES CTR and GCM algorithms. Specifically, the ctr_aes_crypt() function failed to scrub a buffer used for processing remaining bytes smaller than AES_BLOCK_SIZE, potentially leading to the exposure of sensitive d...

EUVD-2026-86898

In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix missing scrub of temp buffers with PAES algorithm In function ctrpaesdocrypt there is a buffer used to process remaining bytes AESBLOCKSIZE. This buffer was not scrubbed and thus could lead to expose of unwanted...

CVE-2026-97590

The Linux kernel contains a vulnerability in the s390/crypto implementation where temporary buffers used with the PAES algorithm were not properly scrubbed. Specifically, in the ctr_paes_do_crypt() function, a buffer used to process remaining bytes (less than AES_BLOCK_SIZE) lacked explicit scrub...

CVE-2026-97591

The Linux kernel (specifically the s390/crypto architecture) contained a logic flaw in how it handled return codes when pushing requests to the crypto engine. In the PHMAC function, the crypto_transfer_hash_request_to_engine() call could return EBUSY in addition to EINPROGRESS to signal a success...

EUVD-2026-86899

In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine When a request is transferred to the engine via cryptotransferhashrequesttoengine there are two return codes signaling a successful transfer:...

CVE-2026-97589

The Linux kernel contains a vulnerability in the s390/crypto subsystem where asynch callbacks return an incorrect error code. Specifically, when crypto_finalize_hash_request() or crypto_finalize_skcipher_request() explicitly completes a request, the do_one_request callback must return 0. Returnin...

EUVD-2026-86897

In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix wrong return code to engine in asynch callbacks When cryptofinalizehashrequest or cryptofinalizeskcipherrequest explicitly completes a request, the doonerequest callback must return 0 to indicate successful...

CVE-2026-97589 s390/crypto: Fix wrong return code to engine in asynch callbacks

In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix wrong return code to engine in asynch callbacks When cryptofinalizehashrequest or cryptofinalizeskcipherrequest explicitly completes a request, the doonerequest callback must return 0 to indicate successful...

CVE-2026-97587

The Linux kernel contained a vulnerability in the perf subsystem affecting RISC-V architectures. The issue stemmed from the available-counter mask being stored as a single unsigned long , while the iteration process used RISCV_MAX_COUNTERS (64). On RV32 systems, this caused the kernel to read pas...

EUVD-2026-86895

In the Linux kernel, the following vulnerability has been resolved: perf: RISC-V: store available counter mask as bitmap The available-counter mask was a single unsigned long, but iteration uses RISCVMAXCOUNTERS, which is 64. On RV32 that reads past the object. Filling with an unsigned-long bit a...

EUVD-2026-86896

In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Map EBUSY to EIO when key conversion fails repeatedly When hardware persistently returns -EBUSY after exhausting retries, the error propagates to cryptofinalizerequest. The crypto API's completion wrapper treats -EBU...

CVE-2026-97588

The Linux kernel contains a vulnerability in the s390/crypto component where persistent -EBUSY errors from hardware during key conversion result in the error being swallowed by the crypto API's completion wrapper. Because the wrapper treats -EBUSY as a queueing status, the completion callback fai...

EUVD-2026-86894

In the Linux kernel, the following vulnerability has been resolved: afs: Fix missing kunmap in afsdirsearchbucket Fix afsdirsearchbucket to kunmap the block it's using in the "bad:" path...

CVE-2026-97586

The Linux kernel contains a vulnerability in the afs component related to the afs_dir_search_bucket() function. The root cause is a missing kunmap operation for the block utilized in the "bad:" path . The provided documents indicate that this issue has been resolved by ensuring the block is prope...