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 82 of 724
CVE-2023-53791UNKNOWN≥ 0, < 6.5.6-12025-12-09
CVE-2023-53791 CVE-2023-53791: In the Linux kernel, the following vulnerability has been resolved: md: fix warning for holder mismatch from export_rdev() Commit a1d767191096 ("md: u
In the Linux kernel, the following vulnerability has been resolved: md: fix warning for holder mismatch from export_rdev() Commit a1d767191096 ("md: use mddev->external to select holder in export_rdev()") fix the problem that 'claim_rdev' is used for blkdev_get_by_dev() while 'rdev' is used for blkdev_put(). However,
osv
CVE-2023-53781UNKNOWN≥ 0, < 6.3.7-12025-12-09
CVE-2023-53781 CVE-2023-53781: In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in tcp_write_timer_handler()
In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in tcp_write_timer_handler(). With Eric's ref tracker, syzbot finally found a repro for use-after-free in tcp_write_timer_handler() by kernel TCP sockets. [0] If SMC creates a kernel socket in __smc_create(), the kernel socket is supposed to be freed in sm
osv
CVE-2022-50632UNKNOWN≥ 0, < 6.1.4-12025-12-09
CVE-2022-50632 CVE-2022-50632: In the Linux kernel, the following vulnerability has been resolved: drivers: perf: marvell_cn10k: Fix hotplug callback leak in tad_pmu_init() tad_pmu_
In the Linux kernel, the following vulnerability has been resolved: drivers: perf: marvell_cn10k: Fix hotplug callback leak in tad_pmu_init() tad_pmu_init() won't remove the callback added by cpuhp_setup_state_multi() when platform_driver_register() failed. Remove the callback by cpuhp_remove_multi_state() in fail pa
osv
CVE-2023-53784UNKNOWN≥ 6.4.0, < 6.4.52025-12-09
CVE-2023-53784 drm: bridge: dw_hdmi: fix connector access for scdc
drm: bridge: dw_hdmi: fix connector access for scdc
In the Linux kernel, the following vulnerability has been resolved:
drm: bridge: dw_hdmi: fix connector access for scdc
Commit 5d844091f237 ("drm/scdc-helper: Pimp SCDC debugs") changed the scdc
interface to pick up an i2c adapter from a connector instead. However, in
the case of dw-hdmi, the wrong connector was being used to pass i2c adapter
information, since dw-hdmi's embe
osv
CVE-2023-53819UNKNOWN≥ 4.2.0, < 4.19.313≥ 4.20.0, < 5.4.275+5 more2025-12-09
CVE-2023-53819 amdgpu: validate offset_in_bo of drm_amdgpu_gem_va
amdgpu: validate offset_in_bo of drm_amdgpu_gem_va
In the Linux kernel, the following vulnerability has been resolved:
amdgpu: validate offset_in_bo of drm_amdgpu_gem_va
This is motivated by OOB access in amdgpu_vm_update_range when
offset_in_bo+map_size overflows.
v2: keep the validations in amdgpu_vm_bo_map
v3: add the validations to amdgpu_vm_bo_map/amdgpu_vm_bo_replace_map
rather than to amdgpu_gem_va_ioctl
osv
CVE-2023-53778UNKNOWN≥ 6.4.0, < 6.4.122025-12-09
CVE-2023-53778 accel/qaic: Clean up integer overflow checking in map_user_pages()
accel/qaic: Clean up integer overflow checking in map_user_pages()
In the Linux kernel, the following vulnerability has been resolved:
accel/qaic: Clean up integer overflow checking in map_user_pages()
The encode_dma() function has some validation on in_trans->size but it
would be more clear to move those checks to find_and_map_user_pages().
The encode_dma() had two checks:
if (in_trans->addr + in_trans->size
osv
CVE-2022-50666UNKNOWN≥ 5.3.0, < 5.15.75≥ 5.16.0, < 5.19.17+1 more2025-12-09
CVE-2022-50666 RDMA/siw: Fix QP destroy to wait for all references dropped.
RDMA/siw: Fix QP destroy to wait for all references dropped.
In the Linux kernel, the following vulnerability has been resolved:
RDMA/siw: Fix QP destroy to wait for all references dropped.
Delay QP destroy completion until all siw references to QP are
dropped. The calling RDMA core will free QP structure after
successful return from siw_qp_destroy() call, so siw must not
hold any remaining reference to the QP upon re
osv
CVE-2022-50677UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-09
CVE-2022-50677 CVE-2022-50677: In the Linux kernel, the following vulnerability has been resolved: ipmi: fix use after free in _ipmi_destroy_user() The intf_free() function frees th
In the Linux kernel, the following vulnerability has been resolved: ipmi: fix use after free in _ipmi_destroy_user() The intf_free() function frees the "intf" pointer so we cannot dereference it again on the next line.
osv
CVE-2023-53822UNKNOWN≥ 5.6.0, < 6.1.30≥ 6.2.0, < 6.3.42025-12-09
CVE-2023-53822 wifi: ath11k: Ignore frags from uninitialized peer in dp.
wifi: ath11k: Ignore frags from uninitialized peer in dp.
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: Ignore frags from uninitialized peer in dp.
When max virtual ap interfaces are configured in all the bands with
ACS and hostapd restart is done every 60s, a crash is observed at
random times.
In this certain scenario, a fragmented packet is received for
self peer, for which rx_tid an
osv
CVE-2025-40342UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-09
CVE-2025-40342 CVE-2025-40342: In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing port_state and rport state nvme_fc_unregister_remote r
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing port_state and rport state nvme_fc_unregister_remote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because nvme_fc_create_asso
osv
CVE-2023-53840UNKNOWN≥ 4.12.0, < 5.15.99≥ 5.16.0, < 6.1.16+1 more2025-12-09
CVE-2023-53840 usb: early: xhci-dbc: Fix a potential out-of-bound memory access
usb: early: xhci-dbc: Fix a potential out-of-bound memory access
In the Linux kernel, the following vulnerability has been resolved:
usb: early: xhci-dbc: Fix a potential out-of-bound memory access
If xdbc_bulk_write() fails, the values in 'buf' can be anything. So the
string is not guaranteed to be NULL terminated when xdbc_trace() is called.
Reserve an extra byte, which will be zeroed automatically because 'buf
osv
CVE-2025-40335UNKNOWN≥ 6.16.0, < 6.17.82025-12-09
CVE-2025-40335 drm/amdgpu: validate userq input args
drm/amdgpu: validate userq input args
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: validate userq input args
This will help on validating the userq input args, and
rejecting for the invalid userq request at the IOCTLs
first place.
osv
CVE-2025-40333UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.8-12025-12-09
CVE-2025-40333 CVE-2025-40333: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix infinite loop in __insert_extent_tree() When we get wrong extent info da
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix infinite loop in __insert_extent_tree() When we get wrong extent info data, and look up extent_node in rb tree, it will cause infinite loop (CONFIG_F2FS_CHECK_FS=n). Avoiding this by return NULL and print some kernel messages in that case.
osv
CVE-2023-53801UNKNOWN≥ 5.13.0, < 5.15.113≥ 5.16.0, < 6.1.81+1 more2025-12-09
CVE-2023-53801 iommu/sprd: Release dma buffer to avoid memory leak
iommu/sprd: Release dma buffer to avoid memory leak
In the Linux kernel, the following vulnerability has been resolved:
iommu/sprd: Release dma buffer to avoid memory leak
When attaching to a domain, the driver would alloc a DMA buffer which
is used to store address mapping table, and it need to be released
when the IOMMU domain is freed.
osv
CVE-2025-40344UNKNOWN≥ 6.12.0, < 6.12.58≥ 6.13.0, < 6.17.82025-12-09
CVE-2025-40344 ASoC: Intel: avs: Disable periods-elapsed work when closing PCM
ASoC: Intel: avs: Disable periods-elapsed work when closing PCM
In the Linux kernel, the following vulnerability has been resolved:
ASoC: Intel: avs: Disable periods-elapsed work when closing PCM
avs_dai_fe_shutdown() handles the shutdown procedure for HOST HDAudio
stream while period-elapsed work services its IRQs. As the former
frees the DAI's private context, these two operations shall be
synchronized to avoid s
osv
CVE-2023-53818UNKNOWN≥ 4.0.0, < 4.14.308≥ 4.15.0, < 4.19.276+5 more2025-12-09
CVE-2023-53818 ARM: zynq: Fix refcount leak in zynq_early_slcr_init
ARM: zynq: Fix refcount leak in zynq_early_slcr_init
In the Linux kernel, the following vulnerability has been resolved:
ARM: zynq: Fix refcount leak in zynq_early_slcr_init
of_find_compatible_node() returns a node pointer with refcount incremented,
we should use of_node_put() on error path.
Add missing of_node_put() to avoid refcount leak.
osv
CVE-2023-53825UNKNOWN≥ 4.6.0, < 4.14.326≥ 4.15.0, < 4.19.295+5 more2025-12-09
CVE-2023-53825 kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().
kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().
In the Linux kernel, the following vulnerability has been resolved:
kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().
syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720
("kcm: Fix memory leak in error path of kcm_sendmsg()") suppressed it by
updating kcm_tx_msg(head)->last_skb if partial data is copied so that the
following sendmsg() will
osv
CVE-2023-53832UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-09
CVE-2023-53832 CVE-2023-53832: In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref in raid10_sync_request init_resync() inits mempool a
In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref in raid10_sync_request init_resync() inits mempool and sets conf->have_replacemnt at the beginning of sync, close_sync() frees the mempool when sync is completed. After [1] recovery might be skipped and init_resync() is
osv
CVE-2023-53861UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-12-09
CVE-2023-53861 CVE-2023-53861: In the Linux kernel, the following vulnerability has been resolved: ext4: correct grp validation in ext4_mb_good_group Group corruption check will acc
In the Linux kernel, the following vulnerability has been resolved: ext4: correct grp validation in ext4_mb_good_group Group corruption check will access memory of grp and will trigger kernel crash if grp is NULL. So do NULL check before corruption check.
osv
CVE-2023-53828UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.3-12025-12-09
CVE-2023-53828 CVE-2023-53828: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor() KSAN re
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor() KSAN reports use-after-free in hci_add_adv_monitor(). While adding an adv monitor, hci_add_adv_monitor() calls -> msft_add_monitor_pattern() calls -> msft_add_monitor_sync() c
osv