CVE-2026-74381

The CVE-2026-74381 entry describes a Linux kernel vulnerability in gpu: host1x where entries in BO caches could be freed. A mapping pinned via host1x_bo_pin() with a cache kept a reference to the underlying host1x_bo, preventing theBO from being freed as long as cached. The fix introduces a weak ...

CVE-2026-74380

CVE-2026-74380 involves the Linux kernel gpu: host1x path where iommu_map_sgtable() return value check was fixed. The change switches iommu_map_sgtable() to return an ssize_t and to return negative error codes instead of a size_t zero, and pin_job() now correctly handles errors (previously might ...

CVE-2026-74379

CVE-2026-74379 affects the Linux kernel dax/kmem driver. The root cause is a partial success in dev_dax_kmem_probe() where at least one resource range is mapped but a subsequent range fails, leading to the range resource being NULL and the probe reporting success. Consequently, dev_dax_kmem_remov...

CVE-2026-74378

CVE-2026-74378 affects the Linux kernel RDMA/rxe path: get_srq_wqe() reads wqe->dma.num_sge from a shared userspace-mapped buffer. The issue is a TOCTOU heap overflow caused by validating num_sge against max_sge and then re-reading the same field to compute memcpy size, allowing a concurrent u...

CVE-2026-74376

CVE-2026-74376 affects the Linux kernel in the md/raid10 path. The issue arises when reusing an r10bio for discard: if discard reuses an r10bio that previously handled a read, read_slot may remain non-negative and discard cleanup could skip releasing the replacement bio. The documented fix resets...

CVE-2026-74377

CVE-2026-74377 affects Linux kernel RDMA/rxe in non-SRQ receive path. The issue arises when the responder reads WQE fields directly from a userspace-mapped shared queue, allowing a malicious user to modify fields such as num_sge or sge entries while the kernel processes the WQE, leading to out-of...

CVE-2026-74375

In the Linux kernel, md/raid1 and raid10 components were hardened to prevent a deadlock during read-error recovery. Specifically, when handling a read error, raid1d/raid10d could resubmit a split md cloned bio while an array is suspended, and attempt to acquire a second active_io reference via pe...

CVE-2026-74374

CVE-2026-74374 affects the Linux kernel’s md/raid1 and md/raid10 code paths. The fix replaces error-path detection that relied on r1_bio or raid10’s read_slot with md_cloned_bio(), addressing cases where the error path is NULL or -1 after bio splitting/resubmission. The consequence previously cou...

CVE-2026-74372

CVE-2026-74372 concerns the Linux kernel RAID1 code path. In raid1_write_request(), every per-mirror iteration starts by incrementing rdev->nr_pending. If a REQ_ATOMIC write hits a badblock within the range, control jumps to err_handle without dropping the reference for the current mirror. The...

CVE-2026-74373

The CVE-2026-74373 entry documents a Linux kernel issue in md/raid1 and raid10 where bio accounting was incorrect for split md cloned bios. The mitigation implemented is to use md_cloned_bio() to detect md cloned bios and skip accounting accordingly, replacing reliance on r1bio_existed (raid1) or...

CVE-2026-74371

CVE-2026-74371 concerns a Linux kernel BPF issue where BPF_PROG_QUERY could cause an OOB write by unconditionally writing query.revision to userspace when a smaller bpf_attr buffer is provided. The fixes propagate the user-supplied attribute size (uattr_size) down to cgroup query handlers and ski...

CVE-2026-74370

The CVE-2026-74370 issue affects the Linux kernel and is resolved by a liveupdate fix for a TOCTOU race in luo_session_retrieve(). The root cause was a race between the lookup and the session mutex where a thread could release and free the session; the patch extends the scope of the rwsem_read lo...

CVE-2026-74369

The CVE-2026-74369 entries describe a Linux kernel vulnerability fix in the liveupdate path, specifically in luo_file_unpreserve_files() and luo_file_finish(). The issue was improper ordering of module_put() and xa_erase() which could affect a file handler module while its operations were accesse...

CVE-2026-74368

The CVE-2026-74368 entry documents a memory leak in the Linux kernel’s ath12k wifi path (ath12k_wifi7_dp_rx_h_verify_tkip_mic) triggered when NWIFI header length validation fails. The root cause is a false return from ath12k_dp_rx_check_nwifi_hdr_len_valid() for invalid NWIFI headers, causing ear...

CVE-2026-74367

CVE-2026-74367 describes a Linux kernel vulnerability in the ath12k WiFi driver (ath12k_mac_vdev_create) where three error-paths can leave arvif in an inconsistent state. Specifically: (1) on failure of ath12k_wmi_vdev_create, arvif->ar isn’t cleared, making vdev readiness checks see a non-NUL...

CVE-2026-74366

CVE-2026-74366 concerns a NULL dereference in the Linux kernel’s ath12k wifi driver when handling unready links. The issue occurs because a path that validates a MAC channel may not create the vdev, leaving arvif->is_created as false and arvif->ar NULL. Subsequent code paths allocate an ars...

CVE-2026-74365

The CVE-2026-74365 entry describes a race in BTT lane acquisition inside the Linux kernel’s nvdimm subsystem. A spinlock-based per-lane recursion model could be bypassed when preemption occurred, allowing concurrent use of the same lane and risking silent data corruption during BTT I/O. The fix r...

CVE-2026-74363

The CVE-2026-74363 entry concerns a Linux kernel BPF/bpffs use-after-free related to inode cleanup. The root cause was that moved cleanup from ->free_inode() into ->destroy_inode() to avoid sleeping in RCU when calling bpf_any_put(), which inadvertently removed the RCU delay on freeing the ...

CVE-2026-74364

The CVE-2026-74364 issue concerns the Linux kernel’s BPF map-in-map handling. A map created as an exclusive map (excl_prog_hash) is bound to a single program by hash. check_map_prog_compatibility() refuses to load programs unless their digest matches map->excl_prog_sha, but this check only cov...

CVE-2026-74362

In the Linux kernel CVE-2026-74362, the vulnerability stems from ext2_write paths where ext2_dio_write_iter() does not propagate the error returned by generic_write_sync(), potentially causing write(2) to report success for O_SYNC/O_DSYNC files even when the sync failed. The corrective pattern is...