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 62 of 724
CVE-2023-54152UNKNOWN≥ 0, < 6.1.25-12025-12-24
CVE-2023-54152 CVE-2023-54152: In the Linux kernel, the following vulnerability has been resolved: can: j1939: prevent deadlock by moving j1939_sk_errqueue() This commit addresses a In the Linux kernel, the following vulnerability has been resolved: can: j1939: prevent deadlock by moving j1939_sk_errqueue() This commit addresses a deadlock situation that can occur in certain scenarios, such as when running data TP/ETP transfer and subscribing to the error queue while receiving a net down event.
osv
CVE-2023-54003UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.25-12025-12-24
CVE-2023-54003 CVE-2023-54003: In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix GID entry ref leak when create_ah fails If AH create request fails, In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix GID entry ref leak when create_ah fails If AH create request fails, release sgid_attr to avoid GID entry referrence leak reported while releasing GID table
osv
CVE-2023-54078UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-24
CVE-2023-54078 CVE-2023-54078: In the Linux kernel, the following vulnerability has been resolved: media: max9286: Free control handler The control handler is leaked in some probe-t In the Linux kernel, the following vulnerability has been resolved: media: max9286: Free control handler The control handler is leaked in some probe-time error paths, as well as in the remove path. Fix it.
osv
CVE-2023-54027UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-12-24
CVE-2023-54027 CVE-2023-54027: In the Linux kernel, the following vulnerability has been resolved: iio: core: Prevent invalid memory access when there is no parent Commit 813665564b In the Linux kernel, the following vulnerability has been resolved: iio: core: Prevent invalid memory access when there is no parent Commit 813665564b3d ("iio: core: Convert to use firmware node handle instead of OF node") switched the kind of nodes to use for label retrieval in device registration. Probably an unwan
osv
CVE-2022-50701UNKNOWN≥ 5.16.0, < 6.1.16≥ 6.2.0, < 6.2.32025-12-24
CVE-2022-50701 wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921s: fix slab-out-of-bounds access in sdio host SDIO may need addtional 511 bytes to align bus operation. If the tailroom of this skb is not big enough, we would access invalid memory region. For low level operation, increase skb size to keep valid memory access in SDIO
osv
CVE-2023-54080UNKNOWN≥ 6.5.0, < 6.5.32025-12-24
CVE-2023-54080 btrfs: zoned: skip splitting and logical rewriting on pre-alloc write btrfs: zoned: skip splitting and logical rewriting on pre-alloc write In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: skip splitting and logical rewriting on pre-alloc write When doing a relocation, there is a chance that at the time of btrfs_reloc_clone_csums(), there is no checksum for the corresponding region. In this case, btrfs_finish_ordered_zoned()'s sum points to an
osv
CVE-2025-68347UNKNOWN≥ 0, < 6.1.162-1≥ 0, < 6.12.63-1+1 more2025-12-24
CVE-2025-68347 CVE-2025-68347: In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events The DSP even In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events The DSP event handling code in hwdep_read() could write more bytes to the user buffer than requested, when a user provides a buffer smaller than the event header size (8 bytes). Fi
osv
CVE-2022-50732UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50732 CVE-2022-50732: In the Linux kernel, the following vulnerability has been resolved: staging: rtl8192u: Fix use after free in ieee80211_rx() We cannot dereference the In the Linux kernel, the following vulnerability has been resolved: staging: rtl8192u: Fix use after free in ieee80211_rx() We cannot dereference the "skb" pointer after calling ieee80211_monitor_rx(), because it is a use after free.
osv
CVE-2023-54064UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-12-24
CVE-2023-54064 CVE-2023-54064: In the Linux kernel, the following vulnerability has been resolved: ipmi:ssif: Fix a memory leak when scanning for an adapter The adapter scan ssif_in In the Linux kernel, the following vulnerability has been resolved: ipmi:ssif: Fix a memory leak when scanning for an adapter The adapter scan ssif_info_find() sets info->adapter_name if the adapter info came from SMBIOS, as it's not set in that case. However, this function can be called more than once, and it will l
osv
CVE-2023-54012UNKNOWN≥ 4.4.0, < 5.4.244≥ 5.5.0, < 5.10.181+3 more2025-12-24
CVE-2023-54012 net: fix stack overflow when LRO is disabled for virtual interfaces net: fix stack overflow when LRO is disabled for virtual interfaces In the Linux kernel, the following vulnerability has been resolved: net: fix stack overflow when LRO is disabled for virtual interfaces When the virtual interface's feature is updated, it synchronizes the updated feature for its own lower interface. This propagation logic should be worked as the iteration, not recursively. But it works recursiv
osv
CVE-2023-54088UNKNOWN≥ 0, < 6.4.13-12025-12-24
CVE-2023-54088 CVE-2023-54088: In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: hold queue_lock when removing blkg->q_node When blkg is removed from q In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: hold queue_lock when removing blkg->q_node When blkg is removed from q->blkg_list from blkg_free_workfn(), queue_lock has to be held, otherwise, all kinds of bugs(list corruption, hard lockup, ..) can be triggered from blkg_destroy_all().
osv
CVE-2025-68738UNKNOWN≥ 6.14.0, < 6.17.13≥ 6.18.0, < 6.18.22025-12-24
CVE-2025-68738 wifi: mt76: mt7996: fix null pointer deref in mt7996_conf_tx() wifi: mt76: mt7996: fix null pointer deref in mt7996_conf_tx() In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: fix null pointer deref in mt7996_conf_tx() If a link does not have an assigned channel yet, mt7996_vif_link returns NULL. We still need to store the updated queue settings in that case, and apply them later. Move the location of the queue params to within struct mt799
osv
CVE-2022-50744UNKNOWN≥ 0, < 6.1.4-12025-12-24
CVE-2022-50744 CVE-2022-50744: In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs During I/O an In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs During I/O and simultaneous cat of /sys/kernel/debug/lpfc/fnX/rx_monitor, a hard lockup similar to the call trace below may occur. The spin_lock_bh in lpfc_rx_monitor_report is not
osv
CVE-2025-68729UNKNOWN≥ 6.3.0, < 6.17.13≥ 6.18.0, < 6.18.22025-12-24
CVE-2025-68729 wifi: ath12k: Fix MSDU buffer types handling in RX error path wifi: ath12k: Fix MSDU buffer types handling in RX error path In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Fix MSDU buffer types handling in RX error path Currently, packets received on the REO exception ring from unassociated peers are of MSDU buffer type, while the driver expects link descriptor type packets. These packets are not parsed further due to a return check on packet t
osv
CVE-2023-53998UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-24
CVE-2023-53998 CVE-2023-53998: In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio - Fix race on data_avail and actual data The virtio rng device kicks In the Linux kernel, the following vulnerability has been resolved: hwrng: virtio - Fix race on data_avail and actual data The virtio rng device kicks off a new entropy request whenever the data available reaches zero. When a new request occurs at the end of a read operation, that is, when the result of that request
osv
CVE-2023-54159UNKNOWN≥ 5.2.0, < 5.4.243≥ 5.5.0, < 5.10.180+4 more2025-12-24
CVE-2023-54159 usb: mtu3: fix kernel panic at qmu transfer done irq handler usb: mtu3: fix kernel panic at qmu transfer done irq handler In the Linux kernel, the following vulnerability has been resolved: usb: mtu3: fix kernel panic at qmu transfer done irq handler When handle qmu transfer irq, it will unlock @mtu->lock before give back request, if another thread handle disconnect event at the same time, and try to disable ep, it may lock @mtu->lock and free qmu ring, then qmu irq hanlder may
osv
CVE-2022-50778UNKNOWN≥ 5.16.0, < 5.19.17≥ 5.20.0, < 6.0.32025-12-24
CVE-2022-50778 fortify: Fix __compiletime_strlen() under UBSAN_BOUNDS_LOCAL fortify: Fix __compiletime_strlen() under UBSAN_BOUNDS_LOCAL In the Linux kernel, the following vulnerability has been resolved: fortify: Fix __compiletime_strlen() under UBSAN_BOUNDS_LOCAL With CONFIG_FORTIFY=y and CONFIG_UBSAN_LOCAL_BOUNDS=y enabled, we observe a runtime panic while running Android's Compatibility Test Suite's (CTS) android.hardware.input.cts.tests. This is stemming from a strlen() call in hidinput_
osv
CVE-2022-50706UNKNOWN≥ 0, < 5.4.220≥ 5.5.0, < 5.10.150+3 more2025-12-24
CVE-2022-50706 net/ieee802154: don't warn zero-sized raw_sendmsg() net/ieee802154: don't warn zero-sized raw_sendmsg() In the Linux kernel, the following vulnerability has been resolved: net/ieee802154: don't warn zero-sized raw_sendmsg() syzbot is hitting skb_assert_len() warning at __dev_queue_xmit() [1], for PF_IEEE802154 socket's zero-sized raw_sendmsg() request is hitting __dev_queue_xmit() with skb->len == 0. Since PF_IEEE802154 socket's zero-sized raw_sendmsg() request was able to ret
osv
CVE-2022-50773UNKNOWN≥ 2.6.19, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-12-24
CVE-2022-50773 ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt In the Linux kernel, the following vulnerability has been resolved: ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt I got a null-ptr-defer error report when I do the following tests on the qemu platform: make defconfig and CONFIG_PARPORT=m, CONFIG_PARPORT_PC=m, CONFIG_SND_MTS64=m Then making test scripts: cat>test_mod1.sh snd_mts64_in
osv
CVE-2022-50768UNKNOWN≥ 6.0.0, < 6.0.16≥ 6.1.0, < 6.1.22025-12-24
CVE-2022-50768 scsi: smartpqi: Correct device removal for multi-actuator devices scsi: smartpqi: Correct device removal for multi-actuator devices In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Correct device removal for multi-actuator devices Correct device count for multi-actuator drives which can cause kernel panics.
osv