CVE-2026-89914

CVE-2026-89914 affects the Linux kernel's KVM arm64 component. When the decode_range_tlbi() helper was moved to support S1 TLBI (translation lookaside buffer invalidation), the required sign extension of the virtual address was omitted. This causes physical address (PA) bit overflow when the rang...

CVE-2026-89913

CVE-2026-89913 affects the Linux kernel in the KVM arm64 vgic-v3 subsystem. The function vgic_v3_save_pending_tables() iterates the LPI xarray via xa_for_each() and dereferences struct vgic_irq without holding a stable reference. The xarray iterator provides only temporary RCU coverage, which is ...

CVE-2026-89912

CVE-2026-89912 affects the Linux kernel in the KVM arm64 vgic-its subsystem. When a guest issues MAPC with V=0 , the ite->collection pointer is nulled while the ITE remains on the device's ITT list. The function vgic_its_save_ite() then dereferences this NULL pointer unconditionally when the V...

CVE-2026-89911

CVE-2026-89911 affects the KVM arm64 subsystem of the Linux kernel. The root cause is an integer overflow in the handling of TLB Invalidation by Range (TLBI) : because the TLBI range can be encoded with a large value based on an arbitrary virtual address, a guest can trigger an overflow if the hy...

CVE-2026-89909

CVE-2026-89909 is a resource leak in the Linux kernel 's LoongArch KVM module. When kvm_loongarch_init() calls kvm_loongarch_env_init() to allocate per-CPU kvm_context (vmcs), kvm_loongarch_ops, and register perf callbacks, a subsequent failure in kvm_init() causes these resources to be leaked be...

CVE-2026-89910

CVE-2026-89910 affects the Linux kernel on LoongArch architecture within the KVM subsystem. The vulnerable component is the stack variable vector[] in the function dmsintc_inject_irq() , which is sometimes used without being initialized, potentially leading to information disclosure (uninitialize...

CVE-2026-89908

In the Linux kernel LoongArch KVM subsystem, kvm_arch_prepare_memory_region() computes a memslot's arch.flags (KVM_MEM_HUGEPAGE_CAPABLE / KVM_MEM_HUGEPAGE_INCAPABLE) only for KVM_MR_CREATE and KVM_MR_MOVE, returning early for all other changes. Because the generic code allocates a zeroed memslot ...

CVE-2026-89906

CVE-2026-89906 affects the LoongArch BPF JIT in the Linux kernel. The jump offset calculation for tail calls used a stale prior-pass code stride to derive branch distances, which can produce wrong branch offsets and cause soft lockups when extra JIT passes are triggered. The fix recalculates the ...

CVE-2026-89907

CVE-2026-89907 affects the Linux kernel on the LoongArch architecture in the KVM EIOINTC MSI routing path. The function pch_msi_set_irq() passes user-supplied MSI data directly to eiointc_set_irq() without validating it against the 256-entry EIOINTC_IRQS limit. A value of 256 or greater causes ou...

CVE-2026-89905

CVE-2026-89905 affects the Linux kernel on the LoongArch architecture within the BPF subsystem. The root cause is a stack layout flaw : the optional arena register slot is placed above the tail call counter (TCC) context . When arena_vm_start is dynamically enabled, it shifts the relative offset ...

CVE-2026-89903

CVE-2026-89903 affects the Linux kernel on the LoongArch architecture, specifically the rethook trampoline (previously the kretprobe trampoline since v6.3 ). The trampoline incorrectly saves and restores $r21 (the per-CPU base register) across its entry/exit frame. If a task migrates CPUs between...

CVE-2026-89904

This Linux kernel vulnerability affects the LoongArch architecture, where the acpi_package_ids[] array overflows when processing the PPTT ACPI table . In a typical LoongArch virtual machine configuration with one core per socket, up to 256 sockets (packages) can be present, exceeding the array's ...

CVE-2026-89902

This Linux kernel vulnerability affects the LoongArch kprobe subsystem. Because LoongArch uses break 11 for kprobe breakpoints, an ordinary userspace breakpoint can reach kprobe_singlestep_handler() with no active probe. The handler calls preempt_enable_no_resched() before checking for a probe, c...

CVE-2026-89900

CVE-2026-89900 is a kernel memory leak in the Linux kernel's media/cec/core subsystem. A prior commit that fixed a race condition between unregister and urb/irq callbacks removed the implicit call to rc_free_device() from rc_unregister_device() but failed to remove the NULL assignment of adap-&gt...

CVE-2026-89901

CVE-2026-89901 is a NULL pointer dereference in the Linux kernel's airspy USB media driver. The root cause is a race between airspy_disconnect() (which clears s->udev) and airspy_stop_streaming() (which unconditionally calls airspy_ctrl_msg() and airspy_free_stream_bufs()). If a streaming user...

CVE-2026-89899

CVE-2026-89899 is a race condition in the Linux kernel's CEC (Consumer Electronics Control) media subsystem . In cec_transmit_msg_fh(), the adapter lock is dropped to wait for a blocking transmit; if that wait is interrupted by a signal, cancel_delayed_work_sync() can execute before the CEC kthre...

CVE-2026-89898

CVE-2026-89898 affects the Linux kernel 's CEC (Consumer Electronics Control) media driver for the Extron DA HD 4K Plus device. The root cause is a missing sanity check that allows an overflow of the msg.msg[] buffer when malformed incoming data is processed. The CVSS 3.1 score is 8.8 (HIGH) with...

CVE-2026-89897

CVE-2026-89897 affects the Linux kernel 's CEC (Consumer Electronics Control) media subsystem. The vulnerability resides in cec_receive_notify(), which reads the exclusive follower pointer without holding the adapter lock , creating a race condition. The fix serializes the no-follower check and m...

CVE-2026-89896

This Linux kernel memory leak affects the cedrus media driver (Allwinner SoC VPU). In cedrus_init_ctrls() , the V4L2 control handler is initialized before allocating memory for ctx->ctrls; if that allocation fails, the function returns -ENOMEM without freeing the handler resources, causing a l...

CVE-2026-89894

CVE-2026-89894 is a heap out-of-bounds write in the Linux kernel cx231xx media driver. The vulnerability arises because vidioc_s_fmt_vid_cap() and vidioc_s_std() can change the device-wide geometry (dev->width/dev->norm) while only checking whether the video queue is busy, not the VBI queue...