CVE-2026-89501

CVE-2026-89501 affects the Linux kernel ring-buffer subsystem. The root cause is a race condition : ring_buffer_subbuf_order_set() can clear cpu_buffer->free_page without holding cpu_buffer::lock, creating a concurrency conflict with ring_buffer_alloc_read_page() and ring_buffer_free_read_page...

CVE-2026-89500

CVE-2026-89500 is a flaw in the Linux kernel's ring-buffer component. When a cached reader page is discarded after a concurrent ring buffer resize, the kernel uses the new global subbuf_order for the free_pages() call rather than the order under which the page was originally allocated. This misma...

CVE-2026-89499

CVE-2026-89499 affects the Linux kernel ring-buffer component. When the remote swap_reader_page callback returns -EBUSY (e.g., during an event storm on a small buffer), __rb_get_reader_page_from_remote() incorrectly continues with an unchanged reader ID and rearranges the local page list as thoug...

CVE-2026-89498

CVE-2026-89498 affects the orangefs (PVFS2) module in the Linux kernel. On a readdir downcall, orangefs_devreq_write_iter() frees op->downcall.trailer_buf via vfree() when copy_from_iter_full() fails but does not clear the pointer before jumping to the error path. The waiter in do_readdir() is...

CVE-2026-89497

A heap buffer overflow exists in the Linux kernel's OrangeFS (orangefs) client, specifically in the function orangefs_prepare_cdm_array(). The function sizes each client debug keyword buffer using strcspn(cds_head, " "), which does not skip leading spaces, but then parses the keyword with the %s ...

CVE-2026-89495

CVE-2026-89495 affects the OCFS2/DLM (o2dlm) subsystem in the Linux kernel . The migration and recovery message handlers trust peer-supplied u8 length fields (namelen, lockname_len, num_locks) without bounding them before passing them to memcpy, resulting in a heap out-of-bounds write of up to ~2...

CVE-2026-89496

CVE-2026-89496 is a memory leak in the Linux kernel OCFS2 filesystem, discovered via local fuzzing of version 6.12.94 . The leak occurs when copy_file_range() is called within the same OCFS2 filesystem, triggering a copy-on-write path that fails to release deallocation caches (ocfs2_cache_block_d...

CVE-2026-89494

CVE-2026-89494 is a CRITICAL (CVSS 9.8) vulnerability in the OCFS2 Distributed Lock Manager (DLM) within the Linux kernel. The dlm_mig_lockres_handler trusts peer-supplied num_locks and lockname_len fields without validation, leading to an out-of-bounds read (triggering a BUG_ON panic) and a heap...

CVE-2026-89492

CVE-2026-89492 is a slab out-of-bounds read in the Linux kernel's OCFS2 filesystem. The functions ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() fail to bound the ocfs2_dx_entry_list counts against the 4 KB block capacity. As a result, ocfs2_dx_dir_search() can walk up to 0xffff entries pa...

CVE-2026-89493

CVE-2026-89493 is an out-of-bounds read/write in the Linux kernel's OCFS2 filesystem module. The root cause is that ocfs2_validate_refcount_block() never validates rl_used and rl_count against the block's fixed on-disk capacity (247 records in a 4K block). A crafted or corrupted refcount block wi...

CVE-2026-89491

CVE-2026-89491 affects the OCFS2 cluster subsystem in the Linux kernel. The o2hb_region_pin() function is called while holding the o2hb_live_lock spinlock, yet it invokes configfs_depend_item(), which sleeps by taking the configfs root inode rwsem and pinning the filesystem. Under CONFIG_DEBUG_AT...

CVE-2026-89489

CVE-2026-89489 affects the Linux kernel on the openrisc (or1k) architecture. The sys_or1k_atomic() syscall (number 244) swaps two user-supplied words via hand-written assembly without validating the pointers with access_ok() and without exception table entries for the four memory accesses. An unp...

CVE-2026-89490

CVE-2026-89490 affects the ocfs2 filesystem in the Linux kernel on 32-bit systems. In ocfs2_dir_foreach_blk_el(), the directory position mask derived from sb->s_blocksize (a 32-bit unsigned long) is zero-extended to 64 bits when ANDed with the loff_t-typed ctx->pos, silently clearing the hi...

CVE-2026-89488

CVE-2026-89488 is a slab-use-after-free in the Linux kernel's Open vSwitch (OVS) component, occurring during network namespace teardown . Packet processing reads CT (connection tracking) limit state under RCU, while teardown frees that state under ovs_mutex without removing the pointer from reade...

CVE-2026-89487

CVE-2026-89487 affects the openvswitch subsystem in the Linux kernel. The bug resides in queue_userspace_packet(), whose error path calls skb_tx_error() on a packet that is still being forwarded through remaining flow actions. This call strips SKBFL_SHARED_FRAG from the live skb via skb_zcopy_cle...

CVE-2026-89486

CVE-2026-89486 is a use-after-free vulnerability in the Linux kernel's IPMI subsystem , introduced by commit 9e91f8a6c868 which removed a synchronize_rcu() grace period before freeing command receiver (cmd_rcvr) objects in _ipmi_destroy_user(). Because the cmd_rcvrs list is still traversed under ...

CVE-2026-89485

CVE-2026-89485 is a use-after-free vulnerability in the Linux kernel's lockd (NLM) subsystem. In nlm_traverse_files(), the current file is pinned across a mutex_unlock window, but the saved next pointer is not. A concurrent nlm_release_file() can free that next file, causing the iterator to deref...

CVE-2026-89483

CVE-2026-89483 is an information disclosure flaw in the Linux kernel NVMe subsystem . When nvme_setup_discard() falls back to the per-controller ctrl->discard_page (allocated via alloc_page(GFP_KERNEL) without zeroing) under memory pressure, up to 4080 bytes of uninitialized kernel memory (inc...

CVE-2026-89484

CVE-2026-89484 is a NULL pointer dereference in the Linux kernel's lockd (Network Lock Manager) subsystem. The bug occurs when nlmclnt_find_lockowner() fails to allocate a lockowner, yet nlmclnt_locks_init_private() still installs NLM file lock operations. When the VFS subsequently tears down the...

CVE-2026-89482

CVE-2026-89482 is a wild-memory-access vulnerability in the Linux kernel's nvme-tcp module. The root cause is an incorrect receive-side gate: for REQ_OP_WRITE_ZEROES commands, blk_rq_payload_bytes() returns a non-zero value despite the absence of physical segments, so the setup phase leaves req-&...