Linux Kernel vulnerabilities

14,478 known vulnerabilities affecting linux/linux_kernel.

Total CVEs
14,478
CISA KEV
29
actively exploited
Public exploits
296
Exploited in wild
31
Severity breakdown
CRITICAL112HIGH3696MEDIUM8484LOW419UNKNOWN1767

Vulnerabilities

Page 36 of 724
CVE-2025-68818UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2026-01-13
CVE-2025-68818 CVE-2025-68818: In the Linux kernel, the following vulnerability has been resolved: scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" Th In the Linux kernel, the following vulnerability has been resolved: scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" This reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9. The commit being reverted added code to __qla2x00_abort_all_cmds() to call sp->done() without holding a spin
osv
CVE-2025-68804UNKNOWN≥ 5.3.0, < 5.10.248≥ 5.11.0, < 5.15.198+4 more2026-01-13
CVE-2025-68804 platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver After unbinding the driver, another kthread `cros_ec_console_log_work` is still accessing the device, resulting an UAF and crash. The driver doesn't unregister the EC device in .remove() which should shutdown sub-devices syn
osv
CVE-2025-68821UNKNOWN≥ 0, < 5.15.198≥ 5.16.0, < 6.1.160+3 more2026-01-13
CVE-2025-68821 fuse: fix readahead reclaim deadlock fuse: fix readahead reclaim deadlock In the Linux kernel, the following vulnerability has been resolved: fuse: fix readahead reclaim deadlock Commit e26ee4efbc79 ("fuse: allocate ff->release_args only if release is needed") skips allocating ff->release_args if the server does not implement open. However in doing so, fuse_prepare_release() now skips grabbing the reference on the inode, which makes it possible for an inode to be evicted from t
osv
CVE-2025-68822UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.3-12026-01-13
CVE-2025-68822 CVE-2025-68822: In the Linux kernel, the following vulnerability has been resolved: Input: alps - fix use-after-free bugs caused by dev3_register_work The dev3_regist In the Linux kernel, the following vulnerability has been resolved: Input: alps - fix use-after-free bugs caused by dev3_register_work The dev3_register_work delayed work item is initialized within alps_reconnect() and scheduled upon receipt of the first bare PS/2 packet from an external PS/2 device connected to the
osv
CVE-2025-68797UNKNOWN≥ 2.6.12, < 5.10.248≥ 5.11.0, < 5.15.198+4 more2026-01-13
CVE-2025-68797 char: applicom: fix NULL pointer dereference in ac_ioctl char: applicom: fix NULL pointer dereference in ac_ioctl In the Linux kernel, the following vulnerability has been resolved: char: applicom: fix NULL pointer dereference in ac_ioctl Discovered by Atuin - Automated Vulnerability Discovery Engine. In ac_ioctl, the validation of IndexCard and the check for a valid RamIO pointer are skipped when cmd is 6. However, the function unconditionally executes readb(apbs[IndexCard].R
osv
CVE-2025-68777UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2026-01-13
CVE-2025-68777 CVE-2025-68777: In the Linux kernel, the following vulnerability has been resolved: Input: ti_am335x_tsc - fix off-by-one error in wire_order validation The current v In the Linux kernel, the following vulnerability has been resolved: Input: ti_am335x_tsc - fix off-by-one error in wire_order validation The current validation 'wire_order[i] > ARRAY_SIZE(config_pins)' allows wire_order[i] to equal ARRAY_SIZE(config_pins), which causes out-of-bounds access when used as index in 'conf
osv
CVE-2025-68770UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.3-12026-01-13
CVE-2025-68770 CVE-2025-68770: In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix XDP_TX path For XDP_TX action in bnxt_rx_xdp(), clearing of the event In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix XDP_TX path For XDP_TX action in bnxt_rx_xdp(), clearing of the event flags is not correct. __bnxt_poll_work() -> bnxt_rx_pkt() -> bnxt_rx_xdp() may be looping within NAPI and some event flags may be set in earlier iterations. In particu
osv
CVE-2025-68781UNKNOWN≥ 0, < 6.1.162-1≥ 0, < 6.12.69-1+1 more2026-01-13
CVE-2025-68781 CVE-2025-68781: In the Linux kernel, the following vulnerability has been resolved: usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal The de In the Linux kernel, the following vulnerability has been resolved: usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal The delayed work item otg_event is initialized in fsl_otg_conf() and scheduled under two conditions: 1. When a host controller binds to the OTG controller. 2. When the USB ID
osv
CVE-2025-68812UNKNOWN≥ 0, < 6.18.3-12026-01-13
CVE-2025-68812 CVE-2025-68812: In the Linux kernel, the following vulnerability has been resolved: media: iris: Add sanity check for stop streaming Add sanity check in iris_vb2_stop In the Linux kernel, the following vulnerability has been resolved: media: iris: Add sanity check for stop streaming Add sanity check in iris_vb2_stop_streaming. If inst->state is already IRIS_INST_ERROR, we should skip the stream_off operation because it would still send packets to the firmware. In iris_kill_session
osv
CVE-2025-68784UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.3-12026-01-13
CVE-2025-68784 CVE-2025-68784: In the Linux kernel, the following vulnerability has been resolved: xfs: fix a UAF problem in xattr repair The xchk_setup_xattr_buf function can alloc In the Linux kernel, the following vulnerability has been resolved: xfs: fix a UAF problem in xattr repair The xchk_setup_xattr_buf function can allocate a new value buffer, which means that any reference to ab->value before the call could become a dangling pointer. Fix this by moving an assignment to after the buffe
osv
CVE-2025-68810UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.3-12026-01-13
CVE-2025-68810 CVE-2025-68810: In the Linux kernel, the following vulnerability has been resolved: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot Reject attempts In the Linux kernel, the following vulnerability has been resolved: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot Reject attempts to disable KVM_MEM_GUEST_MEMFD on a memslot that was initially created with a guest_memfd binding, as KVM doesn't support toggling KVM_MEM_GUEST_MEMFD on existing memslo
osv
CVE-2025-68792UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.3-12026-01-13
CVE-2025-68792 CVE-2025-68792: In the Linux kernel, the following vulnerability has been resolved: tpm2-sessions: Fix out of range indexing in name_size 'name_size' does not have an In the Linux kernel, the following vulnerability has been resolved: tpm2-sessions: Fix out of range indexing in name_size 'name_size' does not have any range checks, and it just directly indexes with TPM_ALG_ID, which could lead into memory corruption at worst. Address the issue by only processing known values and re
osv
CVE-2025-71065UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.3-12026-01-13
CVE-2025-71065 CVE-2025-71065: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid potential deadlock As Jiaming Zhang and syzbot reported, there In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid potential deadlock As Jiaming Zhang and syzbot reported, there is potential deadlock in f2fs as below: Chain exists of: &sbi->cp_rwsem --> fs_reclaim --> sb_internal#2 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(sb_i
osv
CVE-2025-68801UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2026-01-13
CVE-2025-68801 CVE-2025-68801: In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_router: Fix neighbour use-after-free We sometimes observe use-afte In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_router: Fix neighbour use-after-free We sometimes observe use-after-free when dereferencing a neighbour [1]. The problem seems to be that the driver stores a pointer to the neighbour, but without holding a reference on it. A reference
osv
CVE-2025-68820UNKNOWN≥ 0, < 5.10.248≥ 5.11.0, < 5.15.198+4 more2026-01-13
CVE-2025-68820 ext4: xattr: fix null pointer deref in ext4_raw_inode() ext4: xattr: fix null pointer deref in ext4_raw_inode() In the Linux kernel, the following vulnerability has been resolved: ext4: xattr: fix null pointer deref in ext4_raw_inode() If ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED), iloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all() lacks error checking, this will lead to a null pointer dereference in ext4_raw_inode(), called right after ext
osv
CVE-2025-68775UNKNOWN≥ 6.4.0, < 6.6.120≥ 6.7.0, < 6.12.64+1 more2026-01-13
CVE-2025-68775 net/handshake: duplicate handshake cancellations leak socket net/handshake: duplicate handshake cancellations leak socket In the Linux kernel, the following vulnerability has been resolved: net/handshake: duplicate handshake cancellations leak socket When a handshake request is cancelled it is removed from the handshake_net->hn_requests list, but it is still present in the handshake_rhashtbl until it is destroyed. If a second cancellation request arrives for the same handshake
osv
CVE-2025-68779UNKNOWN≥ 6.18.0, < 6.18.32026-01-13
CVE-2025-68779 net/mlx5e: Avoid unregistering PSP twice net/mlx5e: Avoid unregistering PSP twice In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid unregistering PSP twice PSP is unregistered twice in: _mlx5e_remove -> mlx5e_psp_unregister mlx5e_nic_cleanup -> mlx5e_psp_unregister This leads to a refcount underflow in some conditions: ------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 2 PID: 1694 at lib/refcount.c:28 re
osv
CVE-2025-68807UNKNOWN≥ 6.16.0, < 6.18.32026-01-13
CVE-2025-68807 block: fix race between wbt_enable_default and IO submission block: fix race between wbt_enable_default and IO submission In the Linux kernel, the following vulnerability has been resolved: block: fix race between wbt_enable_default and IO submission When wbt_enable_default() is moved out of queue freezing in elevator_change(), it can cause the wbt inflight counter to become negative (-1), leading to hung tasks in the writeback path. Tasks get stuck in wbt_wait() because the co
osv
CVE-2025-68786UNKNOWN≥ 0, < 6.1.162-1≥ 0, < 6.12.69-1+1 more2026-01-13
CVE-2025-68786 CVE-2025-68786: In the Linux kernel, the following vulnerability has been resolved: ksmbd: skip lock-range check on equal size to avoid size==0 underflow When size eq In the Linux kernel, the following vulnerability has been resolved: ksmbd: skip lock-range check on equal size to avoid size==0 underflow When size equals the current i_size (including 0), the code used to call check_lock_range(filp, i_size, size - 1, WRITE), which computes `size - 1` and can underflow for size==0. S
osv
CVE-2025-68791UNKNOWN≥ 0, < 6.18.3-12026-01-13
CVE-2025-68791 CVE-2025-68791: In the Linux kernel, the following vulnerability has been resolved: fuse: missing copy_finish in fuse-over-io-uring argument copies Fix a possible ref In the Linux kernel, the following vulnerability has been resolved: fuse: missing copy_finish in fuse-over-io-uring argument copies Fix a possible reference count leak of payload pages during fuse argument copies. [Joanne: simplified error cleanup]
osv