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 70 of 724
CVE-2025-68304UNKNOWN≥ 6.6.0, < 6.17.112025-12-16
CVE-2025-68304 Bluetooth: hci_core: lookup hci_conn on RX path on protocol side
Bluetooth: hci_core: lookup hci_conn on RX path on protocol side
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_core: lookup hci_conn on RX path on protocol side
The hdev lock/lookup/unlock/use pattern in the packet RX path doesn't
ensure hci_conn* is not concurrently modified/deleted. This locking
appears to be leftover from before conn_hash started using RCU
commit bf4c6325249
osv
CVE-2025-68240UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-16
CVE-2025-68240 CVE-2025-68240: In the Linux kernel, the following vulnerability has been resolved: nilfs2: avoid having an active sc_timer before freeing sci Because kthread_stop di
In the Linux kernel, the following vulnerability has been resolved: nilfs2: avoid having an active sc_timer before freeing sci Because kthread_stop did not stop sc_task properly and returned -EINTR, the sc_timer was not properly closed, ultimately causing the problem [1] reported by syzbot when freeing sci due to the
osv
CVE-2025-68191UNKNOWN≥ 5.9.0, < 5.10.247≥ 5.11.0, < 5.15.197+4 more2025-12-16
CVE-2025-68191 udp_tunnel: use netdev_warn() instead of netdev_WARN()
udp_tunnel: use netdev_warn() instead of netdev_WARN()
In the Linux kernel, the following vulnerability has been resolved:
udp_tunnel: use netdev_warn() instead of netdev_WARN()
netdev_WARN() uses WARN/WARN_ON to print a backtrace along with
file and line information. In this case, udp_tunnel_nic_register()
returning an error is just a failed operation, not a kernel bug.
udp_tunnel_nic_register() can fail due to a memory a
osv
CVE-2025-68172UNKNOWN≥ 6.3.0, < 6.6.117≥ 6.7.0, < 6.12.58+1 more2025-12-16
CVE-2025-68172 crypto: aspeed - fix double free caused by devm
crypto: aspeed - fix double free caused by devm
In the Linux kernel, the following vulnerability has been resolved:
crypto: aspeed - fix double free caused by devm
The clock obtained via devm_clk_get_enabled() is automatically managed
by devres and will be disabled and freed on driver detach. Manually
calling clk_disable_unprepare() in error path and remove function
causes double free.
Remove the manual clock cleanup in both aspe
osv
CVE-2025-68290UNKNOWN≥ 5.6.0, < 5.10.247≥ 5.11.0, < 5.15.197+4 more2025-12-16
CVE-2025-68290 most: usb: fix double free on late probe failure
most: usb: fix double free on late probe failure
In the Linux kernel, the following vulnerability has been resolved:
most: usb: fix double free on late probe failure
The MOST subsystem has a non-standard registration function which frees
the interface on registration failures and on deregistration.
This unsurprisingly leads to bugs in the MOST drivers, and a couple of
recent changes turned a reference underflow and use-after-fre
osv
CVE-2025-68170UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.8-12025-12-16
CVE-2025-68170 CVE-2025-68170: In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Do not kfree() devres managed rdev Since the allocation of the drivers
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Do not kfree() devres managed rdev Since the allocation of the drivers main structure was changed to devm_drm_dev_alloc() rdev is managed by devres and we shouldn't be calling kfree() on it. This fixes things exploding if the driver probe
osv
CVE-2025-68186UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.8-12025-12-16
CVE-2025-68186 CVE-2025-68186: In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up Th
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up The function ring_buffer_map_get_reader() is a bit more strict than the other get reader functions, and except for certain situations the rb_get_reader_page() should not
osv
CVE-2025-68257UNKNOWN≥ 5.8.0, < 5.10.248≥ 5.11.0, < 5.15.198+5 more2025-12-16
CVE-2025-68257 comedi: check device's attached status in compat ioctls
comedi: check device's attached status in compat ioctls
In the Linux kernel, the following vulnerability has been resolved:
comedi: check device's attached status in compat ioctls
Syzbot identified an issue [1] that crashes kernel, seemingly due to
unexistent callback dev->get_valid_routes(). By all means, this should
not occur as said callback must always be set to
get_zero_valid_routes() in __comedi_device_postconfig().
osv
CVE-2025-68295UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68295 CVE-2025-68295: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix memory leak in cifs_construct_tcon() When having a multiuser moun
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix memory leak in cifs_construct_tcon() When having a multiuser mount with domain= specified and using cifscreds, cifs_set_cifscreds() will end up setting @ctx->domainname, so it needs to be freed before leaving cifs_construct_tcon(). T
osv
CVE-2025-68233UNKNOWN≥ 6.0.0, < 6.1.159≥ 6.2.0, < 6.6.118+2 more2025-12-16
CVE-2025-68233 drm/tegra: Add call to put_pid()
drm/tegra: Add call to put_pid()
In the Linux kernel, the following vulnerability has been resolved:
drm/tegra: Add call to put_pid()
Add a call to put_pid() corresponding to get_task_pid().
host1x_memory_context_alloc() does not take ownership of the PID so we
need to free it here to avoid leaking.
[[email protected]: reword commit message]
osv
CVE-2025-68225UNKNOWN≥ 0, < 6.17.10-12025-12-16
CVE-2025-68225 CVE-2025-68225: In the Linux kernel, the following vulnerability has been resolved: lib/test_kho: check if KHO is enabled We must check whether KHO is enabled prior t
In the Linux kernel, the following vulnerability has been resolved: lib/test_kho: check if KHO is enabled We must check whether KHO is enabled prior to issuing KHO commands, otherwise KHO internal data structures are not initialized.
osv
CVE-2025-68215UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.10-12025-12-16
CVE-2025-68215 CVE-2025-68215: In the Linux kernel, the following vulnerability has been resolved: ice: fix PTP cleanup on driver removal in error path Improve the cleanup on releas
In the Linux kernel, the following vulnerability has been resolved: ice: fix PTP cleanup on driver removal in error path Improve the cleanup on releasing PTP resources in error path. The error case might happen either at the driver probe and PTP feature initialization or on PTP restart (errors in reset handling, NVM
osv
CVE-2025-68281UNKNOWN≥ 6.17.0, < 6.17.122025-12-16
CVE-2025-68281 ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list
ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list
"struct sdca_control" declares "values" field as integer array.
But the memory allocated to it is of char array. This causes
crash for sdca_parse_function API. This patch addresses the
issue by allocating correct data size.
osv
CVE-2025-40362UNKNOWN≥ 6.10.0, < 6.12.58≥ 6.13.0, < 6.17.82025-12-16
CVE-2025-40362 ceph: fix multifs mds auth caps issue
ceph: fix multifs mds auth caps issue
In the Linux kernel, the following vulnerability has been resolved:
ceph: fix multifs mds auth caps issue
The mds auth caps check should also validate the
fsname along with the associated caps. Not doing
so would result in applying the mds auth caps of
one fs on to the other fs in a multifs ceph cluster.
The bug causes multiple issues w.r.t user
authentication, following is one such example.
Steps to R
osv
CVE-2025-68206UNKNOWN≥ 4.12.0, < 6.1.167≥ 6.2.0, < 6.6.130+2 more2025-12-16
CVE-2025-68206 netfilter: nft_ct: add seqadj extension for natted connections
netfilter: nft_ct: add seqadj extension for natted connections
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_ct: add seqadj extension for natted connections
Sequence adjustment may be required for FTP traffic with PASV/EPSV modes.
due to need to re-write packet payload (IP, port) on the ftp control
connection. This can require changes to the TCP length and expected
seq / ack_seq.
osv
CVE-2025-40360UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-16
CVE-2025-40360 CVE-2025-40360: In the Linux kernel, the following vulnerability has been resolved: drm/sysfb: Do not dereference NULL pointer in plane reset The plane state in __drm
In the Linux kernel, the following vulnerability has been resolved: drm/sysfb: Do not dereference NULL pointer in plane reset The plane state in __drm_gem_reset_shadow_plane() can be NULL. Do not deref that pointer, but forward NULL to the other plane-reset helpers. Clears plane->state to NULL. v2: - fix typo in comm
osv
CVE-2025-40353UNKNOWN≥ 6.11.0, < 6.12.56≥ 6.13.0, < 6.17.62025-12-16
CVE-2025-40353 arm64: mte: Do not warn if the page is already tagged in copy_highpage()
arm64: mte: Do not warn if the page is already tagged in copy_highpage()
In the Linux kernel, the following vulnerability has been resolved:
arm64: mte: Do not warn if the page is already tagged in copy_highpage()
The arm64 copy_highpage() assumes that the destination page is newly
allocated and not MTE-tagged (PG_mte_tagged unset) and warns
accordingly. However, following commit 060913999d7a ("mm: migrate
osv
CVE-2025-68261UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2025-12-16
CVE-2025-68261 CVE-2025-68261: In the Linux kernel, the following vulnerability has been resolved: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() Fix a race be
In the Linux kernel, the following vulnerability has been resolved: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() Fix a race between inline data destruction and block mapping. The function ext4_destroy_inline_data_nolock() changes the inode data layout by clearing EXT4_INODE_INLINE_DATA and set
osv
CVE-2025-68197UNKNOWN≥ 6.13.0, < 6.17.82025-12-16
CVE-2025-68197 bnxt_en: Fix null pointer dereference in bnxt_bs_trace_check_wrap()
bnxt_en: Fix null pointer dereference in bnxt_bs_trace_check_wrap()
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Fix null pointer dereference in bnxt_bs_trace_check_wrap()
With older FW, we may get the ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER
for FW trace data type that has not been initialized. This will result
in a crash in bnxt_bs_trace_type_wrap(). Add a guard to check for
osv
CVE-2025-68289UNKNOWN≥ 0, < 5.10.247≥ 5.11.0, < 5.15.197+4 more2025-12-16
CVE-2025-68289 usb: gadget: f_eem: Fix memory leak in eem_unwrap
usb: gadget: f_eem: Fix memory leak in eem_unwrap
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: f_eem: Fix memory leak in eem_unwrap
The existing code did not handle the failure case of usb_ep_queue in the
command path, potentially leading to memory leaks.
Improve error handling to free all allocated resources on usb_ep_queue
failure. This patch continues to use goto logic for error handling,
osv