392097 matches found
CVE-2026-74471
In the Linux kernel tracing subsystem, CVE-2026-74471 is caused by trace_module_add_events() ignoring the return value of __register_event(): if registration fails, a trace_event_call may still be linked via __add_event_to_tracers(), creating a stale pointer that can lead to a use-after-free when...
CVE-2026-74472
CVE-2026-74472 affects the Linux kernel ublk path. The vulnerability arises because ublk_ctrl_add_dev() memcpy()s userspace dev_info into ub->dev_info but does not reset two driver-owned fields: ->state and ->ublksrv_pid. This can cause a device added with state LIVE to pass a test for “...
CVE-2026-74470
The CVE-2026-74470 issue affects the Linux kernel in the scsi_debug path for REPORT ZONES replies. The vulnerability arises from an alloc_len handling bug where resp_report_zones() derives arr_len and rep_max_zones from the CDB alloc_len; for large alloc_len (0xFFFFFFC1..0xFFFFFFFF) ALIGN() can p...
CVE-2026-74469
The CVE-2026-74469 issue affects the Linux kernel SCTP implementation. It occurs in sctp_assoc_add_peer(), where a 16-bit transport_count is incremented for each new unique peer; once the 65,536th transport is added, the counter wraps to zero. SCTP sock_diag uses transport_count to reserve the IN...
CVE-2026-74468
The CVE-2026-74468 vulnerability affects the Linux kernel GPIO subsystem for the pch (Platform Controller Hub) driver. The root cause is that pch_irq_type() uses a spinlock (chip->spinlock) with spin_lock_irqsave() while __irq_set_trigger() is invoked with desc->lock held (a raw_spinlock_t)...
CVE-2026-74466
The CVE-2026-74466 vulnerability concerns the Linux kernel’s s390/zcrypt path. A domain value is extracted from a CCA or EP11 ioctl struct and, under certain conditions (custom device node, administrative load), is used as an array index after bounds checking without a speculation barrier. This c...
CVE-2026-74467
CVE-2026-74467 concerns the Linux kernel: the s390/qeth code failed to enforce CAP_NET_ADMIN for private ioctl commands (SIOC_QETH_ADP_SET_SNMP_CONTROL, SIOC_QETH_GET_CARD_TYPE, SIOC_QETH_QUERY_OAT). The vulnerability is mitigated by gating these SIOCDEVPRIVATE ioctls with a CAP_NET_ADMIN check t...
CVE-2026-74465
The CVE-2026-74465 entry describes a potential use-after-free in Linux kernel/Open vSwitch meter handling: attach_meter() may briefly expose a newly created meter and later free it on failure via ovs_meter_cmd_set(), risking UAF if RC reader/window timing allows access. The fix (per the reports) ...
CVE-2026-74464
CVE-2026-74464 affects the Linux kernel net/openvswitch path where skb leaks can occur on flow key update failure during connection tracking. The issue stems from ovs_ct_execute() freeing the skb on failure while ovs_flow_key_update() does not; if update fails and returns early, the skb may be le...
CVE-2026-74463
The CVE-2026-74463 issue concerns the Linux kernel: i2c: jz4780: Cache host clock rate at probe to prevent CCF prepare_lock deadlock. The root cause is that during an I2C clock frequency change, the Common Clock Framework (CCF) can deadlock with the I2C adapter lock when clk_get_rate() is invoked...
CVE-2026-74462
CVE-2026-74462 – Linux kernel i2c: imx vulnerable window during suspend/resume on i.MX platforms where a periodic I2C workqueue could trigger transfers while hardware resources (clock/pinctrl) are unavailable. Root cause: I2C adapter may be accessed in the window between suspend_noirq and resume_...
CVE-2026-74461
Summary (CVE-2026-74461) In the Linux kernel’s i2c_imx driver, the failure path occurs when an interrupt-driven hrtimer can fire after the slave pointer is set to NULL but before the pointer is cleared, leading to a use-after-free/NULL pointer dereference in the timer callback (i2c_imx_slave_fini...
CVE-2026-74460
The CVE-2026-74460 issue affects the Linux kernel’s ems_usb path for CPC messages. The vulnerability arises in can: ems_usb: validate CPC message lengths, where ems_usb_read_bulk_callback() processes CPC messages in a USB receive buffer. The fix enforces that each declared CPC message fits within...
CVE-2026-74459
CVE-2026-74459 (Linux kernel) affects the can: etas_es58x driver, specifically es58x_read_bulk_callback(). When RX URB resubmission fails (usb_submit_urb()), the callback currently does not release the allocated coherent transfer buffer, causing a buffer leak. The fixes documented in multiple sou...
CVE-2026-74458
Summary: CVE-2026-74458 affects the Linux kernel can: kvaser_usb_leaf code. The flaw allowed dispatch of variable-length USB commands when a nonzero command shorter than CMD_HEADER_LEN was received; a matching command could be copied into a caller-owned kvaser_cmd using the device-provided length...
CVE-2026-74457
The CVE-2026-74457 entry describes a Linux kernel issue in the can: peak_usb driver where ctrl_idx is derived from rx->len (USB payload). The mask 0x0f allows 0–15, but usb_if->dev[] is only size 2, causing heap out-of-bounds read and kernel panic in IRQ context. The fix adds bounds checks ...
CVE-2026-74455
The CVE-2026-74455 vulnerability in the Linux kernel concerns the peak_usb driver for CAN (uCAN) payloads. pcan_usb_fd_decode_buf() parses multiple CAN records packed in a single USB receive buffer and now requires each record to include the fixed header for its type and validates the CAN payload...
CVE-2026-74456
Summary (CVE-2026-74456): In the Linux kernel, the peak_usb path has a double-free in peak_usb_start() when URB_SUBMIT fails. Each RX URB transfer buffer is allocated with kmalloc() and flagged URB_FREE_BUFFER so that usb_free_urb() frees the transfer buffer. If usb_submit_urb() fails, the error ...
CVE-2026-74454
CVE-2026-74454 affects the Linux kernel driv3rs/drm vc4 by correcting how the overflow slot size is written during binner memory handling. The issue arises when vc4_overflow_mem_work() sets BPOA to a 512KB slot but BPOS stores the size of the entire 16MB binner BO, enabling the PTB to write tile ...
CVE-2026-74452
The CVE-2026-74452 issue affects the Linux kernel DRM Panthor firmware loading. In panthor_fw_load_section_entry(), the copied data size is computed as hdr.data.end - hdr.data.start without validating against the allocated section_size, permitting a crafted firmware to set section->data.size l...