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 60 of 724
CVE-2023-54113UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.3-12025-12-24
CVE-2023-54113 CVE-2023-54113: In the Linux kernel, the following vulnerability has been resolved: rcu: dump vmalloc memory info safely Currently, for double invoke call_rcu(), will In the Linux kernel, the following vulnerability has been resolved: rcu: dump vmalloc memory info safely Currently, for double invoke call_rcu(), will dump rcu_head objects memory info, if the objects is not allocated from the slab allocator, the vmalloc_dump_obj() will be invoke and the vmap_area_lock spinlock need
osv
CVE-2023-54076UNKNOWN≥ 6.4.0, < 6.4.72025-12-24
CVE-2023-54076 smb: client: fix missed ses refcounting smb: client: fix missed ses refcounting In the Linux kernel, the following vulnerability has been resolved: smb: client: fix missed ses refcounting Use new cifs_smb_ses_inc_refcount() helper to get an active reference of @ses and @ses->dfs_root_ses (if set). This will prevent @ses->dfs_root_ses of being put in the next call to cifs_put_smb_ses() and thus potentially causing an use-after-free bug.
osv
CVE-2022-50772UNKNOWN≥ 5.2.0, < 6.0.72025-12-24
CVE-2022-50772 netdevsim: fix memory leak in nsim_bus_dev_new() netdevsim: fix memory leak in nsim_bus_dev_new() In the Linux kernel, the following vulnerability has been resolved: netdevsim: fix memory leak in nsim_bus_dev_new() If device_register() failed in nsim_bus_dev_new(), the value of reference in nsim_bus_dev->dev is 1. obj->name in nsim_bus_dev->dev will not be released. unreferenced object 0xffff88810352c480 (size 16): comm "echo", pid 5691, jiffies 4294945921 (age 133.270s) hex d
osv
CVE-2023-54037UNKNOWN≥ 6.3.0, < 6.4.72025-12-24
CVE-2023-54037 ice: prevent NULL pointer deref during reload ice: prevent NULL pointer deref during reload In the Linux kernel, the following vulnerability has been resolved: ice: prevent NULL pointer deref during reload Calling ethtool during reload can lead to call trace, because VSI isn't configured for some time, but netdev is alive. To fix it add rtnl lock for VSI deconfig and config. Set ::num_q_vectors to 0 after freeing and add a check for ::tx/rx_rings in ring related ethtool ops.
osv
CVE-2022-50775UNKNOWN≥ 5.17.0, < 6.1.16≥ 6.2.0, < 6.2.32025-12-24
CVE-2022-50775 RDMA/hns: Fix refcount leak in hns_roce_mmap RDMA/hns: Fix refcount leak in hns_roce_mmap In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix refcount leak in hns_roce_mmap rdma_user_mmap_entry_get_pgoff() takes the reference. Add missing rdma_user_mmap_entry_put() to release the reference. Acked-by Haoyue Xu
osv
CVE-2023-54137UNKNOWN≥ 5.8.0, < 5.10.195≥ 5.11.0, < 5.15.132+3 more2025-12-24
CVE-2023-54137 vfio/type1: fix cap_migration information leak vfio/type1: fix cap_migration information leak In the Linux kernel, the following vulnerability has been resolved: vfio/type1: fix cap_migration information leak Fix an information leak where an uninitialized hole in struct vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace. The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as shown in this pahole(1) output: struct vfio_iommu_type1
osv
CVE-2023-54041UNKNOWN≥ 0, < 6.1.25-12025-12-24
CVE-2023-54041 CVE-2023-54041: In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided bu In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak when removing provided buffers When removing provided buffers, io_buffer structs are not being disposed of, leading to a memory leak. They can't be freed individually, because they are allocated in page-sized groups. They ne
osv
CVE-2023-54038UNKNOWN≥ 6.4.0, < 6.4.72025-12-24
CVE-2023-54038 Bluetooth: hci_conn: return ERR_PTR instead of NULL when there is no link Bluetooth: hci_conn: return ERR_PTR instead of NULL when there is no link In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: return ERR_PTR instead of NULL when there is no link hci_connect_sco currently returns NULL when there is no link (i.e. when hci_conn_link() returns NULL). sco_connect() expects an ERR_PTR in case of any error (see line 266 in sco.c). Thus, hco
osv
CVE-2023-54070UNKNOWN≥ 0, < 6.5.6-12025-12-24
CVE-2023-54070 CVE-2023-54070: In the Linux kernel, the following vulnerability has been resolved: igb: clean up in all error paths when enabling SR-IOV After commit 50f303496d92 (" In the Linux kernel, the following vulnerability has been resolved: igb: clean up in all error paths when enabling SR-IOV After commit 50f303496d92 ("igb: Enable SR-IOV after reinit"), removing the igb module could hang or crash (depending on the machine) when the module has been loaded with the max_vfs parameter set
osv
CVE-2025-68356UNKNOWN≥ 6.6.0, < 6.12.63≥ 6.13.0, < 6.17.13+1 more2025-12-24
CVE-2025-68356 gfs2: Prevent recursive memory reclaim gfs2: Prevent recursive memory reclaim In the Linux kernel, the following vulnerability has been resolved: gfs2: Prevent recursive memory reclaim Function new_inode() returns a new inode with inode->i_mapping->gfp_mask set to GFP_HIGHUSER_MOVABLE. This value includes the __GFP_FS flag, so allocations in that address space can recurse into filesystem memory reclaim. We don't want that to happen because it can consume a significant amount of
osv
CVE-2022-50751UNKNOWN≥ 2.6.16, < 5.4.229≥ 5.5.0, < 5.10.163+3 more2025-12-24
CVE-2022-50751 configfs: fix possible memory leak in configfs_create_dir() configfs: fix possible memory leak in configfs_create_dir() In the Linux kernel, the following vulnerability has been resolved: configfs: fix possible memory leak in configfs_create_dir() kmemleak reported memory leaks in configfs_create_dir(): unreferenced object 0xffff888009f6af00 (size 192): comm "modprobe", pid 3777, jiffies 4295537735 (age 233.784s) backtrace: kmem_cache_alloc (mm/slub.c:3250 mm/slub.c:3256 mm/sl
osv
CVE-2023-53992UNKNOWN≥ 3.19.0, < 6.1.55≥ 6.2.0, < 6.5.52025-12-24
CVE-2023-53992 wifi: cfg80211: ocb: don't leave if not joined wifi: cfg80211: ocb: don't leave if not joined In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: ocb: don't leave if not joined If there's no OCB state, don't ask the driver/mac80211 to leave, since that's just confusing. Since set/clear the chandef state, that's a simple check.
osv
CVE-2023-54090UNKNOWN≥ 5.16.0, < 6.1.29≥ 6.2.0, < 6.2.16+1 more2025-12-24
CVE-2023-54090 ixgbe: Fix panic during XDP_TX with > 64 CPUs ixgbe: Fix panic during XDP_TX with > 64 CPUs In the Linux kernel, the following vulnerability has been resolved: ixgbe: Fix panic during XDP_TX with > 64 CPUs Commit 4fe815850bdc ("ixgbe: let the xdpdrv work with more than 64 cpus") adds support to allow XDP programs to run on systems with more than 64 CPUs by locking the XDP TX rings and indexing them using cpu % 64 (IXGBE_MAX_XDP_QS). Upon trying this out patch on a system with
osv
CVE-2023-54102UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-24
CVE-2023-54102 CVE-2023-54102: In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow A static code an In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow A static code analysis tool flagged the possibility of buffer overflow when using copy_from_user() for a debugfs entry. Currently, it is possible that copy_from_user() copies more byte
osv
CVE-2022-50725UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50725 CVE-2022-50725: In the Linux kernel, the following vulnerability has been resolved: media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init() KASAN reports a use-af In the Linux kernel, the following vulnerability has been resolved: media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init() KASAN reports a use-after-free: BUG: KASAN: use-after-free in dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core] Call Trace: ... dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core] vidtv_bridge_probe+0x7bf/0xa
osv
CVE-2023-54042UNKNOWN≥ 5.14.0, < 5.15.121≥ 5.16.0, < 6.1.39+2 more2025-12-24
CVE-2023-54042 powerpc/64s: Fix VAS mm use after free powerpc/64s: Fix VAS mm use after free In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Fix VAS mm use after free The refcount on mm is dropped before the coprocessor is detached.
osv
CVE-2025-68354UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2025-12-24
CVE-2025-68354 CVE-2025-68354: In the Linux kernel, the following vulnerability has been resolved: regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex reg In the Linux kernel, the following vulnerability has been resolved: regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex regulator_supply_alias_list was accessed without any locking in regulator_supply_alias(), regulator_register_supply_alias(), and regulator_unregister_supply_alias(). Concu
osv
CVE-2023-54149UNKNOWN≥ 6.3.0, < 6.3.13≥ 6.4.0, < 6.4.42025-12-24
CVE-2023-54149 net: dsa: avoid suspicious RCU usage for synced VLAN-aware MAC addresses net: dsa: avoid suspicious RCU usage for synced VLAN-aware MAC addresses In the Linux kernel, the following vulnerability has been resolved: net: dsa: avoid suspicious RCU usage for synced VLAN-aware MAC addresses When using the felix driver (the only one which supports UC filtering and MC filtering) as a DSA master for a random other DSA switch, one can see the following stack trace when the downstream sw
osv
CVE-2022-50718UNKNOWN≥ 5.8.0, < 5.10.163≥ 5.11.0, < 5.15.86+2 more2025-12-24
CVE-2022-50718 drm/amdgpu: fix pci device refcount leak drm/amdgpu: fix pci device refcount leak In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix pci device refcount leak As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So before returning from amdgpu_device_resume|suspend_display_audio(), pci_dev_put() is called to
osv
CVE-2023-54018UNKNOWN≥ 4.3.0, < 4.14.308≥ 4.15.0, < 4.19.276+5 more2025-12-24
CVE-2023-54018 drm/msm/hdmi: Add missing check for alloc_ordered_workqueue drm/msm/hdmi: Add missing check for alloc_ordered_workqueue In the Linux kernel, the following vulnerability has been resolved: drm/msm/hdmi: Add missing check for alloc_ordered_workqueue Add check for the return value of alloc_ordered_workqueue as it may return NULL pointer and cause NULL pointer dereference in `hdmi_hdcp.c` and `hdmi_hpd.c`. Patchwork: https://patchwork.freedesktop.org/patch/517211/
osv