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 42 of 724
CVE-2023-54246UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-12-30
CVE-2023-54246 CVE-2023-54246: In the Linux kernel, the following vulnerability has been resolved: rcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle() Th
In the Linux kernel, the following vulnerability has been resolved: rcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle() The rcuscale.holdoff module parameter can be used to delay the start of rcu_scale_writer() kthread. However, the hung-task timeout will trigger when the timeout specified
osv
CVE-2022-50864UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-30
CVE-2022-50864 CVE-2022-50864: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix shift-out-of-bounds due to too large exponent of block size If field s
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix shift-out-of-bounds due to too large exponent of block size If field s_log_block_size of superblock data is corrupted and too large, init_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds warning followed by a kernel panic
osv
CVE-2023-54240UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-12-30
CVE-2023-54240 CVE-2023-54240: In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_eth_soc: fix possible NULL pointer dereference in mtk_hwlro_get
In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_eth_soc: fix possible NULL pointer dereference in mtk_hwlro_get_fdir_all() rule_locs is allocated in ethtool_get_rxnfc and the size is determined by rule_cnt from user space. So rule_cnt needs to be check before using rule_locs to
osv
CVE-2023-54280UNKNOWN≥ 0, < 6.3.7-12025-12-30
CVE-2023-54280 CVE-2023-54280: In the Linux kernel, the following vulnerability has been resolved: cifs: fix potential race when tree connecting ipc Protect access of TCP_Server_Inf
In the Linux kernel, the following vulnerability has been resolved: cifs: fix potential race when tree connecting ipc Protect access of TCP_Server_Info::hostname when building the ipc tree name as it might get freed in cifsd thread and thus causing an use-after-free bug in __tree_connect_dfs_target(). Also, while at
osv
CVE-2023-54286UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-30
CVE-2023-54286 CVE-2023-54286: In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: dvm: Fix memcpy: detected field-spanning write backtrace A received
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: dvm: Fix memcpy: detected field-spanning write backtrace A received TKIP key may be up to 32 bytes because it may contain MIC rx/tx keys too. These are not used by iwl and copying these over overflows the iwl_keyinfo.key field. Add a c
osv
CVE-2023-54318UNKNOWN≥ 5.8.0, < 5.10.195≥ 5.11.0, < 5.15.132+2 more2025-12-30
CVE-2023-54318 net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add
net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add
In the Linux kernel, the following vulnerability has been resolved:
net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add
While doing smcr_port_add, there maybe linkgroup add into or delete
from smc_lgr_list.list at the same time, which may result kernel crash.
So, use smc_lgr_lis
osv
CVE-2022-50871UNKNOWN≥ 5.6.0, < 6.0.16≥ 6.1.0, < 6.1.22025-12-30
CVE-2022-50871 wifi: ath11k: Fix qmi_msg_handler data structure initialization
wifi: ath11k: Fix qmi_msg_handler data structure initialization
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: Fix qmi_msg_handler data structure initialization
qmi_msg_handler is required to be null terminated by QMI module.
There might be a case where a handler for a msg id is not present in the
handlers array which can lead to infinite loop while searching the handler
and there
osv
CVE-2023-54268UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-30
CVE-2023-54268 CVE-2023-54268: In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't wake up kswapd from fill_pool() syzbot is reporting a lockdep
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't wake up kswapd from fill_pool() syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd,
osv
CVE-2023-54243UNKNOWN≥ 3.15.0, < 5.10.173≥ 5.11.0, < 5.15.100+2 more2025-12-30
CVE-2023-54243 netfilter: ebtables: fix table blob use-after-free
netfilter: ebtables: fix table blob use-after-free
In the Linux kernel, the following vulnerability has been resolved:
netfilter: ebtables: fix table blob use-after-free
We are not allowed to return an error at this point.
Looking at the code it looks like ret is always 0 at this
point, but its not.
t = find_table_lock(net, repl->name, &ret, &ebt_mutex);
... this can return a valid table, with ret != 0.
This bug causes updat
osv
CVE-2023-54180UNKNOWN≥ 3.8.0, < 6.0.19≥ 6.1.0, < 6.1.52025-12-30
CVE-2023-54180 btrfs: handle case when repair happens with dev-replace
btrfs: handle case when repair happens with dev-replace
In the Linux kernel, the following vulnerability has been resolved:
btrfs: handle case when repair happens with dev-replace
[BUG]
There is a bug report that a BUG_ON() in btrfs_repair_io_failure()
(originally repair_io_failure() in v6.0 kernel) got triggered when
replacing a unreliable disk:
BTRFS warning (device sda1): csum failed root 257 ino 2397453 off 39624704 c
osv
CVE-2023-54276UNKNOWN≥ 6.3.0, < 6.4.42025-12-30
CVE-2023-54276 nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net
nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net
In the Linux kernel, the following vulnerability has been resolved:
nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net
Commit f5f9d4a314da ("nfsd: move reply cache initialization into nfsd
startup") moved the initialization of the reply cache into nfsd startup,
but didn't account for the stats counters, whi
osv
CVE-2022-50827UNKNOWN≥ 0, < 6.0.6-12025-12-30
CVE-2022-50827 CVE-2022-50827: In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix memory leak in lpfc_create_port() Commit 5e633302ace1 ("scsi: lpfc
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix memory leak in lpfc_create_port() Commit 5e633302ace1 ("scsi: lpfc: vmid: Add support for VMID in mailbox command") introduced allocations for the VMID resources in lpfc_create_port() after the call to scsi_host_alloc(). Upon failure
osv
CVE-2023-54201UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.3-12025-12-30
CVE-2023-54201 CVE-2023-54201: In the Linux kernel, the following vulnerability has been resolved: RDMA/efa: Fix wrong resources deallocation order When trying to destroy QP or CQ,
In the Linux kernel, the following vulnerability has been resolved: RDMA/efa: Fix wrong resources deallocation order When trying to destroy QP or CQ, we first decrease the refcount and potentially free memory regions allocated for the object and then request the device to destroy the object. If the device fails, the o
osv
CVE-2023-54200UNKNOWN≥ 5.15.0, < 5.15.113≥ 5.16.0, < 6.1.30+1 more2025-12-30
CVE-2023-54200 netfilter: nf_tables: always release netdev hooks from notifier
netfilter: nf_tables: always release netdev hooks from notifier
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: always release netdev hooks from notifier
This reverts "netfilter: nf_tables: skip netdev events generated on netns removal".
The problem is that when a veth device is released, the veth release
callback will also queue the peer netns device for removal.
Its pos
osv
CVE-2023-54275UNKNOWN≥ 5.7.0, < 5.10.173≥ 5.11.0, < 5.15.99+2 more2025-12-30
CVE-2023-54275 wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup
wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: Fix memory leak in ath11k_peer_rx_frag_setup
crypto_alloc_shash() allocates resources, which should be released by
crypto_free_shash(). When ath11k_peer_find() fails, there has memory
leak. Add missing crypto_free_shash() to fix this.
osv
CVE-2023-54244UNKNOWN≥ 2.6.33, < 4.14.316≥ 4.15.0, < 4.19.284+5 more2025-12-30
CVE-2023-54244 ACPI: EC: Fix oops when removing custom query handlers
ACPI: EC: Fix oops when removing custom query handlers
In the Linux kernel, the following vulnerability has been resolved:
ACPI: EC: Fix oops when removing custom query handlers
When removing custom query handlers, the handler might still
be used inside the EC query workqueue, causing a kernel oops
if the module holding the callback function was already unloaded.
Fix this by flushing the EC query workqueue when removing
cu
osv
CVE-2023-54236UNKNOWN≥ 4.18.0, < 5.4.240≥ 5.5.0, < 5.10.177+3 more2025-12-30
CVE-2023-54236 net/net_failover: fix txq exceeding warning
net/net_failover: fix txq exceeding warning
In the Linux kernel, the following vulnerability has been resolved:
net/net_failover: fix txq exceeding warning
The failover txq is inited as 16 queues.
when a packet is transmitted from the failover device firstly,
the failover device will select the queue which is returned from
the primary device if the primary device is UP and running.
If the primary device txq is bigger than the default
osv
CVE-2022-50835UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-12-30
CVE-2022-50835 CVE-2022-50835: In the Linux kernel, the following vulnerability has been resolved: jbd2: add miss release buffer head in fc_do_one_pass() In fc_do_one_pass() miss re
In the Linux kernel, the following vulnerability has been resolved: jbd2: add miss release buffer head in fc_do_one_pass() In fc_do_one_pass() miss release buffer head after use which will lead to reference count leak.
osv
CVE-2022-50847UNKNOWN≥ 5.18.0, < 6.0.16≥ 6.1.0, < 6.1.22025-12-30
CVE-2022-50847 drm/bridge: it6505: Initialize AUX channel in it6505_i2c_probe
drm/bridge: it6505: Initialize AUX channel in it6505_i2c_probe
In the Linux kernel, the following vulnerability has been resolved:
drm/bridge: it6505: Initialize AUX channel in it6505_i2c_probe
During device boot, the HPD interrupt could be triggered before the DRM
subsystem registers it6505 as a DRM bridge. In such cases, the driver
tries to access AUX channel and causes NULL pointer dereference.
Initializing the A
osv
CVE-2022-50824UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-30
CVE-2022-50824 CVE-2022-50824: In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak In check_acpi_tpm
In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak In check_acpi_tpm2(), we get the TPM2 table just to make sure the table is there, not used after the init, so the acpi_put_table() should be added to release the ACPI memory.
osv