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 76 of 724
CVE-2022-50671UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-12-09
CVE-2022-50671 CVE-2022-50671: In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix "kernel NULL pointer dereference" error When rxe_queue_init in the f In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix "kernel NULL pointer dereference" error When rxe_queue_init in the function rxe_qp_init_req fails, both qp->req.task.func and qp->req.task.arg are not initialized. Because of creation of qp fails, the function rxe_create_qp will call rx
osv
CVE-2023-53845UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-09
CVE-2023-53845 CVE-2023-53845: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix infinite loop in nilfs_mdt_get_block() If the disk image that nilfs2 m In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix infinite loop in nilfs_mdt_get_block() If the disk image that nilfs2 mounts is corrupted and a virtual block address obtained by block lookup for a metadata file is invalid, nilfs_bmap_lookup_at_level() may return the same internal return
osv
CVE-2023-53829UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.6-12025-12-09
CVE-2023-53829 CVE-2023-53829: In the Linux kernel, the following vulnerability has been resolved: f2fs: flush inode if atomic file is aborted Let's flush the inode being aborted at In the Linux kernel, the following vulnerability has been resolved: f2fs: flush inode if atomic file is aborted Let's flush the inode being aborted atomic operation to avoid stale dirty inode during eviction in this call stack: f2fs_mark_inode_dirty_sync+0x22/0x40 [f2fs] f2fs_abort_atomic_write+0xc4/0xf0 [f2fs] f2fs_
osv
CVE-2022-50647UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-12-09
CVE-2022-50647 CVE-2022-50647: In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as `insb', `outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested location, which in turn
osv
CVE-2023-53849UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-09
CVE-2023-53849 CVE-2023-53849: In the Linux kernel, the following vulnerability has been resolved: drm/msm: fix workqueue leak on bind errors Make sure to destroy the workqueue also In the Linux kernel, the following vulnerability has been resolved: drm/msm: fix workqueue leak on bind errors Make sure to destroy the workqueue also in case of early errors during bind (e.g. a subcomponent failing to bind). Since commit c3b790ea07a1 ("drm: Manage drm_mode_config_init with drmm_") the mode config wi
osv
CVE-2023-53820UNKNOWN≥ 0, < 4.19.312≥ 4.20.0, < 5.4.274+4 more2025-12-09
CVE-2023-53820 loop: loop_set_status_from_info() check before assignment loop: loop_set_status_from_info() check before assignment In the Linux kernel, the following vulnerability has been resolved: loop: loop_set_status_from_info() check before assignment In loop_set_status_from_info(), lo->lo_offset and lo->lo_sizelimit should be checked before reassignment, because if an overflow error occurs, the original correct value will be changed to the wrong value, and it will not be changed back.
osv
CVE-2023-53797UNKNOWN≥ 0, < 5.4.251≥ 5.5.0, < 5.10.188+4 more2025-12-09
CVE-2023-53797 HID: wacom: Use ktime_t rather than int when dealing with timestamps HID: wacom: Use ktime_t rather than int when dealing with timestamps In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Use ktime_t rather than int when dealing with timestamps Code which interacts with timestamps needs to use the ktime_t type returned by functions like ktime_get. The int type does not offer enough space to store these values, and attempting to use it is a recipe f
osv
CVE-2022-50639UNKNOWN≥ 0, < 6.0.5-12025-12-09
CVE-2022-50639 CVE-2022-50639: In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fa In the Linux kernel, the following vulnerability has been resolved: io-wq: Fix memory leak in worker creation If the CPU mask allocation for a node fails, then the memory allocated for the 'io_wqe' struct of the current node doesn't get freed on the error handling path, since it has not yet been added to the 'wqes' a
osv
CVE-2022-50641UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-12-09
CVE-2022-50641 CVE-2022-50641: In the Linux kernel, the following vulnerability has been resolved: HSI: omap_ssi: Fix refcount leak in ssi_probe When returning or breaking early fro In the Linux kernel, the following vulnerability has been resolved: HSI: omap_ssi: Fix refcount leak in ssi_probe When returning or breaking early from a for_each_available_child_of_node() loop, we need to explicitly call of_node_put() on the child node to possibly release the node.
osv
CVE-2023-53841UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-09
CVE-2023-53841 CVE-2023-53841: In the Linux kernel, the following vulnerability has been resolved: devlink: report devlink_port_type_warn source device devlink_port_type_warn is sch In the Linux kernel, the following vulnerability has been resolved: devlink: report devlink_port_type_warn source device devlink_port_type_warn is scheduled for port devlink and warning when the port type is not set. But from this warning it is not easy found out which device (driver) has no devlink port set. [ 3709.
osv
CVE-2022-50679UNKNOWN≥ 5.8.0, < 5.10.152≥ 5.11.0, < 5.15.76+1 more2025-12-09
CVE-2022-50679 i40e: Fix DMA mappings leak i40e: Fix DMA mappings leak In the Linux kernel, the following vulnerability has been resolved: i40e: Fix DMA mappings leak During reallocation of RX buffers, new DMA mappings are created for those buffers. steps for reproduction: while : do for ((i=0; i<=8160; i=i+32)) do ethtool -G enp130s0f0 rx $i tx $i sleep 0.5 ethtool -g enp130s0f0 done done This resulted in crash: i40e 0000:01:00.1: Unable to allocate memory for the Rx descriptor ring, size=
osv
CVE-2023-53799UNKNOWN≥ 2.6.19, < 5.10.195≥ 5.11.0, < 5.15.132+3 more2025-12-09
CVE-2023-53799 crypto: api - Use work queue in crypto_destroy_instance crypto: api - Use work queue in crypto_destroy_instance In the Linux kernel, the following vulnerability has been resolved: crypto: api - Use work queue in crypto_destroy_instance The function crypto_drop_spawn expects to be called in process context. However, when an instance is unregistered while it still has active users, the last user may cause the instance to be freed in atomic context. Fix this by delaying the freei
osv
CVE-2025-40336UNKNOWN≥ 6.15.0, < 6.17.82025-12-09
CVE-2025-40336 drm/gpusvm: fix hmm_pfn_to_map_order() usage drm/gpusvm: fix hmm_pfn_to_map_order() usage In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: fix hmm_pfn_to_map_order() usage Handle the case where the hmm range partially covers a huge page (like 2M), otherwise we can potentially end up doing something nasty like mapping memory which is outside the range, and maybe not even mapped by the mm. Fix is based on the xe userptr code, which in a future patch
osv
CVE-2023-53779UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-09
CVE-2023-53779 CVE-2023-53779: In the Linux kernel, the following vulnerability has been resolved: mfd: dln2: Fix memory leak in dln2_probe() When dln2_setup_rx_urbs() in dln2_probe In the Linux kernel, the following vulnerability has been resolved: mfd: dln2: Fix memory leak in dln2_probe() When dln2_setup_rx_urbs() in dln2_probe() fails, error out_free forgets to call usb_put_dev() to decrease the refcount of dln2->usb_dev. Fix this by adding usb_put_dev() in the error handling code of dln2_pr
osv
CVE-2023-53855UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-12-09
CVE-2023-53855 CVE-2023-53855: In the Linux kernel, the following vulnerability has been resolved: net: dsa: ocelot: call dsa_tag_8021q_unregister() under rtnl_lock() on driver remo In the Linux kernel, the following vulnerability has been resolved: net: dsa: ocelot: call dsa_tag_8021q_unregister() under rtnl_lock() on driver remove When the tagging protocol in current use is "ocelot-8021q" and we unbind the driver, we see this splat: $ echo '0000:00:00.2' > /sys/bus/pci/drivers/fsl_enetc/unbind
osv
CVE-2023-53862UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-12-09
CVE-2023-53862 CVE-2023-53862: In the Linux kernel, the following vulnerability has been resolved: hfs: fix missing hfs_bnode_get() in __hfs_bnode_create Syzbot found a kernel BUG i In the Linux kernel, the following vulnerability has been resolved: hfs: fix missing hfs_bnode_get() in __hfs_bnode_create Syzbot found a kernel BUG in hfs_bnode_put(): kernel BUG at fs/hfs/bnode.c:466! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 3634 Comm: kworker/u4:5 Not tainted 6.1.0-rc7-syzkaller-001
osv
CVE-2023-53787UNKNOWN≥ 0, < 6.4.11-12025-12-09
CVE-2023-53787 CVE-2023-53787: In the Linux kernel, the following vulnerability has been resolved: regulator: da9063: fix null pointer deref with partial DT config When some of the In the Linux kernel, the following vulnerability has been resolved: regulator: da9063: fix null pointer deref with partial DT config When some of the da9063 regulators do not have corresponding DT nodes a null pointer dereference occurs on boot because such regulators have no init_data causing the pointers calculated
osv
CVE-2023-53795UNKNOWN≥ 6.2.0, < 6.4.82025-12-09
CVE-2023-53795 iommufd: IOMMUFD_DESTROY should not increase the refcount iommufd: IOMMUFD_DESTROY should not increase the refcount In the Linux kernel, the following vulnerability has been resolved: iommufd: IOMMUFD_DESTROY should not increase the refcount syzkaller found a race where IOMMUFD_DESTROY increments the refcount: obj = iommufd_get_object(ucmd->ictx, cmd->id, IOMMUFD_OBJ_ANY); if (IS_ERR(obj)) return PTR_ERR(obj); iommufd_ref_to_users(obj); /* See iommufd_ref_to_users() */ if (!io
osv
CVE-2023-53794UNKNOWN≥ 4.7.0, < 6.1.47≥ 6.2.0, < 6.4.122025-12-09
CVE-2023-53794 cifs: fix session state check in reconnect to avoid use-after-free issue cifs: fix session state check in reconnect to avoid use-after-free issue In the Linux kernel, the following vulnerability has been resolved: cifs: fix session state check in reconnect to avoid use-after-free issue Don't collect exiting session in smb2_reconnect_server(), because it will be released soon. Note that the exiting session will stay in server->smb_ses_list until it complete the cifs_free_ipc()
osv
CVE-2023-53816UNKNOWN≥ 0, < 6.1.25-12025-12-09
CVE-2023-53816 CVE-2023-53816: In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix potential kgd_mem UAFs kgd_mem pointers returned by kfd_process_de In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix potential kgd_mem UAFs kgd_mem pointers returned by kfd_process_device_translate_handle are only guaranteed to be valid while p->mutex is held. As soon as the mutex is unlocked, another thread can free the BO.
osv