CVE-2026-72093

CVE-2026-72093 (Linux kernel) : The vulnerability concerns the accel/amdxdna path for amdxdna_gem_dmabuf_mmap. When vm_insert_pages() fails, the error path invokes vma->vm_ops->close(vma), which calls drm_gem_vm_close() → drm_gem_object_put() to release the GEM object. However, the close_vm...

CVE-2026-72092

The CVE-2026-72092 issue affects the Linux kernel’s accel/amdxdna path: aie2_dev_ops defines cmd_submit while aie4_vf_ops does not, so the AMDXDNA_EXEC_CMD ioctl on AIE4 devices may call a NULL function pointer and oops. The kernel now rejects submission early with -EOPNOTSUPP when no cmd_submit ...

CVE-2026-72091

The CVE-2026-72091 in the Linux kernel accelerator amdxdna driver describes a NULL dereference when a user submits an AMDXDNA_EXEC_CMD with cmd handle 0 (AMDXDNA_INVALID_BO_HANDLE). The sequence: accel/amdxdna: submit_execbuf passes a user BO handle to amdxdna_cmd_submit with drv_cmd == NULL; sin...

CVE-2026-72090

CVE-2026-72090 affects the Linux kernel component accel/amdxdna. The root cause is in the ioctl flow for SYNC_DIRECT_FROM_DEVICE: amdxdna_drm_sync_bo_ioctl() looked up args->handle in the caller’s drm_file and then invoked amdxdna_hwctx_sync_debug_bo() with abo->client. The function uses th...

CVE-2026-72089

The CVE-2026-72089 entry describes a Linux kernel issue in accel/ivpu firmware log handling. fw_log_from_bo() validates header_size but not log->size, so if a log’s size is smaller than header (including 0), fw_log_print_buffer() computes data_size = log->size - log->header_size and unde...

CVE-2026-72088

The CVE-2026-72088 entry concerns the Linux kernel SCSI HPSA driver IOACCEL2 reset path. The root cause was a DMA mapping leak when phys_disk->in_reset is set, causing an early return without cleaning up resources allocated for the command. The fix adds proper error cleanup: unmapping the IOAC...

CVE-2026-72087

CVE-2026-72087 affects the Linux kernel SCSI LPFC driver, specifically the lpfc_sli4_driver_resource_setup() path. The vulnerability is a memory leak: memory allocated for mboxq via mempool_alloc() is not freed in some early exit error paths. The cited fixes relocate mempool_free() to an earlier ...

CVE-2026-72086

The CVE-2026-72086 entry describes a Linux kernel vulnerability in the pvSCSI/scsiback path for Xen where, on the TMR submit-failure path, a command tag could be leaked instead of freed. Specifically, scsiback_device_action() obtains a tag, submits target_submit_tmr(), and on failure the err path...

CVE-2026-72085

CVE-2026-72085 concerns the Linux kernel SCSI xen scsiback path. A path in scsiback_get_pend_req() creates a pending command with an uninitialized or not-yet-kref’d se_cmd; if a submission is aborted via a bad grant or unknown ring_req.act, transport_generic_free_cmd() underflows the reference co...

CVE-2026-72084

The CVE-2026-72084 vulnerability affects the Linux kernel SCSI subsystem: PR-OUT TransportID parsing for iSCSI can over-read when the provided buffer length isn’t properly validated, potentially allowing out-of-bounds reads. The fix introduces length checks on the iSCSI TransportID (ADDITIONAL LE...

CVE-2026-72083

CVE-2026-72083 affects the Linux kernel SCSI target core code. The vulnerability (iSCSI ISID use-after-free in REGISTER AND MOVE) arises when core_scsi3_emulate_pro_register_and_move() maps the PERSISTENT RESERVE OUT parameter list with transport_kmap_data_sg(), parses the iSCSI TransportID, and ...

CVE-2026-72082

The CVE concerns the Linux kernel SCSI elx/efct path. When efct_hw_reqtag_alloc() fails in efct_hw_io_abort(), the error path returns -ENOSPC without releasing the reference obtained via kref_get_unless_zero(), causing a permanent reference leak on the io_to_abort object. Additionally, the abort_...

CVE-2026-72081

This CVE (CVE-2026-72081) concerns the Linux kernel SCSI elx/efct path. The issue occurs in efct_dispatch_fcp_cmd() which allocates an efct_io before dispatching an unsolicited FCP command; if the command includes an unsupported additional CDB, the function returns -EIO before handing the IO to t...

CVE-2026-72080

CVE-2026-72080 affects the Linux kernel resctrl filesystem (fs/resctrl). The issue is a use-after-free during unmount/failure teardown: mon_data structures for the default resource group can be freed while a concurrent reader still holds references, due to RDT_DELETED not being set for the static...

CVE-2026-72079

The CVE-2026-72079 issue affects the Linux kernel’s ims_pcu_disconnect path, where use-after-free/double-free could occur if a data interface is misidentified as the control interface due to relying on interface class for cleanup. The fix switches validation to ensure the disconnected interface i...

CVE-2026-72078

CVE-2026-72078 affects the Linux kernel’s ims-pcu driver. The vulnerability arises because the driver assumes the first control-endpoint is an interrupt IN endpoint without verification, which a malicious USB device could exploit by presenting a different endpoint type. This could cause the endpo...

CVE-2026-72077

CVE-2026-72077 pertains to the Linux kernel. The issue is a firmware leak in the ims-pcu path during async firmware update: when validation fails, the firmware object was not released. The fix ensures the firmware is always released by calling __free(firmware). This is a kernel memory/resource le...

CVE-2026-72075

In the Linux kernel, a race condition was fixed in the ims-pcu reset_device sysfs callback. The ims_pcu_reset_device() path called IMS_PCU_execute_command() without holding pcu->cmd_mutex, allowing data races and possible corruption of the shared command buffer when commands execute concurrent...

CVE-2026-72076

Summary (CVE-2026-72076): In the Linux kernel driver for ims-pcu, a debugging print in ims_pcu_irq() could read beyond the buffer. When an interrupt was for pcu->urb_ctrl, the actual data lives in pcu->urb_ctrl_buf, but the code unconditionally printed from pcu->urb_in_buf. If urb->ac...

CVE-2026-72074

The CVE-2026-72074 entry concerns a Linux kernel USB IMS-PCU driver issue where the bMasterInterface0 from the CDC union descriptor is trusted without verifying it matches the interface being probed. This type confusion in CDC descriptor parsing could allow the driver to overwrite private data of...