CVE-2026-93086

CVE-2026-93086 affects the Linux kernel's arm_scmi firmware driver. The vulnerability resides in scmi_cleanup_channels(), which iterates over TX/RX channel IDRs using idr_for_each() to free transport resources. The destroy callback incorrectly removed each entry from the IDR being walked, which c...

CVE-2026-93089

In the Linux kernel , the firmware: arm_scmi driver contains a resource-leak vulnerability in its error handling path. When the transport channel setup succeeds but the subsequent IDR insertion fails, the error path destroys the transport device and frees the channel info without invoking the tra...

CVE-2026-93085

CVE-2026-93085 affects the Linux kernel arm_scmi firmware driver . The Device Tree parsing paths accepted SCMI protocol IDs outside the valid range defined by MSG_PROTOCOL_ID_MASK , logging an error but continuing to process the invalid value. A malformed 32-bit DT reg value could reach helpers e...

CVE-2026-93084

CVE-2026-93084 affects the ARM SCMI (System Control and Management Interface) firmware driver in the Linux kernel . The SCMI bus notifier acquires a handle on BUS_NOTIFY_BIND_DRIVER but only releases it on BUS_NOTIFY_UNBOUND_DRIVER . When device_link_add() fails, the handle is retained without a ...

CVE-2026-93083

In the Linux kernel , the firmware: arm_scmi driver's mailbox_chan_setup() function acquires a primary mailbox channel and then requests an additional unidirectional TX receiver channel . If that second request fails, the function returns immediately without releasing the primary channel , leavin...

CVE-2026-93082

CVE-2026-93082 affects the arm_scmi firmware driver in the Linux kernel . The vulnerable function is mailbox_chan_setup() , which acquires a primary P2A mailbox channel and then attempts to request an additional P2A receiver channel. If the secondary request fails, the function returns the error ...

CVE-2026-93081

CVE-2026-93081 affects the Linux kernel 's firmware: arm_scmi driver, specifically the SCMI device destroy path. The root cause is that scmi_child_dev_find() drops the reference returned by device_find_child() before returning the scmi_device pointer, so a concurrent unregister can release the de...

CVE-2026-93080

CVE-2026-93080 affects the arm_scmi firmware driver in the Linux kernel . SCMI transport devices are deliberately excluded from normal bus matching so protocol drivers cannot bind to them, but scmi_device_destroy() reused the same protocol/name lookup to locate devices for channel teardown. The f...

CVE-2026-93079

CVE-2026-93079 is a heap out-of-bounds write in the Linux kernel's CXL subsystem. In cxlctl_get_feature(), the output buffer is sized from the user-supplied fwctl_rpc.out_len, but the device is instructed to write cxl_mbox_get_feat_in.count bytes into that buffer. Because count is a separate user...

CVE-2026-93078

CVE-2026-93078 is a vulnerability in the Linux kernel 's cxl/features subsystem. The function cxlctl_set_feature() sizes its output buffer from the user-supplied fwctl_rpc.out_len without verifying it is large enough to hold the fwctl_rpc_cxl_out header. When out_len is zero, kvzalloc() returns Z...

CVE-2026-93077

CVE-2026-93077 affects the Linux kernel CXL (Compute Express Link) subsystem, specifically the cxl_get_feature() function in the cxl/features code. The function reads a device feature in a loop but passes a fixed output size as the capacity on every iteration. On the last partial iteration, the b...

CVE-2026-93076

CVE-2026-93076 affects the Linux kernel 's DAX (Direct Access) driver subsystem, specifically the fsdev_dax path for static devices. When a static DAX device is rebound from device_dax to fsdev_dax , a stale vmemmap_shift value—set by device_dax based on alignment—persists on the shared pgmap str...

CVE-2026-93074

CVE-2026-93074 affects the Linux kernel 's dax/fsdev subsystem. The root cause is in __fsdev_dax_direct_access(), which computed the kernel virtual address by adding a device-linear byte offset to virt_addr (the direct-map address of ranges[0]). For multi-range devices with physical gaps between ...

CVE-2026-93075

CVE-2026-93075 is a Linux kernel vulnerability in the dax/fsdev subsystem. When fsdev_dax_probe() sets pgmap->ops and pgmap->owner, these fields are never cleared on unbind for static devices . Because the shared pgmap is long-lived (owned by the dax bus), stale fsdev_pagemap_ops persist af...

CVE-2026-93073

This TOCTOU race condition affects the Linux kernel DAX subsystem in the dax_holder_notify_failure() function. The function reads dax_dev->holder_ops twice without READ_ONCE()—once for a NULL check and once for the indirect notify_failure() call. A concurrent fs_put_dax() can clear holder_ops ...

CVE-2026-93071

CVE-2026-93071 is a memory leak in the Linux kernel's bcm2835-unicam media driver. The function v4l2_async_nf_add_fwnode_remote() allocates an async sub-device (asc) object that is only freed when v4l2_async_nf_cleanup() is called, but that cleanup was not invoked in the driver's error and remove...

CVE-2026-93072

CVE-2026-93072 affects the Linux kernel irqchip/renesas-irqc driver. During probe, the driver allocates generic interrupt chips in the interrupt domain but fails to set the IRQ_DOMAIN_FLAG_DESTROY_GC flag. On driver removal, the generic chips are therefore not freed, causing a resource leak . Bec...

CVE-2026-93070

CVE-2026-93070 is a double-free vulnerability in the Linux kernel's Intel IPU6 media driver (media: ipu6). After ipu6_bus_initialize_device() stores the isys/psys pdata pointer and initializes the auxiliary device, error-unwinding paths in the callers perform an extra kfree(pdata). Since the auxi...

CVE-2026-93069

CVE-2026-93069 affects the Linux kernel OPP (Operating Performance Points) subsystem . A prior commit (173e02d67494) changed the initialization order so that *opp_table was initialized after *opp, which reversed the order of registered cleanup functions. This can cause a use-after-free in _opp_kr...

CVE-2026-93067

CVE-2026-93067 affects the Linux kernel's tc358767 DRM bridge driver. In tc_aux_read_data(), the byte count reported by the controller via the AUX_BYTES field (which can be up to 255) is used directly to read into a 16-byte stack buffer (auxrdata) and then copied to the caller buffer, without cla...