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 87 of 724
CVE-2025-40301UNKNOWN≥ 6.1.0, < 6.1.159≥ 6.2.0, < 6.6.117+2 more2025-12-08
CVE-2025-40301 Bluetooth: hci_event: validate skb length for unknown CC opcode
Bluetooth: hci_event: validate skb length for unknown CC opcode
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_event: validate skb length for unknown CC opcode
In hci_cmd_complete_evt(), if the command complete event has an unknown
opcode, we assume the first byte of the remaining skb->data contains the
return status. However, parameter data has previously been pulled in
hci_even
osv
CVE-2025-40295UNKNOWN≥ 6.15.0, < 6.17.82025-12-08
CVE-2025-40295 fscrypt: fix left shift underflow when inode->i_blkbits > PAGE_SHIFT
fscrypt: fix left shift underflow when inode->i_blkbits > PAGE_SHIFT
In the Linux kernel, the following vulnerability has been resolved:
fscrypt: fix left shift underflow when inode->i_blkbits > PAGE_SHIFT
When simulating an nvme device on qemu with both logical_block_size and
physical_block_size set to 8 KiB, an error trace appears during
partition table reading at boot time. The issue is caused by
inode->i_b
osv
CVE-2023-53750UNKNOWN≥ 0, < 6.4.4-12025-12-08
CVE-2023-53750 CVE-2023-53750: In the Linux kernel, the following vulnerability has been resolved: pinctrl: freescale: Fix a memory out of bounds when num_configs is 1 The config pa
In the Linux kernel, the following vulnerability has been resolved: pinctrl: freescale: Fix a memory out of bounds when num_configs is 1 The config passed in by pad wakeup is 1, when num_configs is 1, Configuration [1] should not be fetched, which will be detected by KASAN as a memory out of bounds condition. Modify
osv
CVE-2023-53766UNKNOWN≥ 2.6.12, < 4.14.324≥ 4.15.0, < 4.19.293+5 more2025-12-08
CVE-2023-53766 FS: JFS: Check for read-only mounted filesystem in txBegin
FS: JFS: Check for read-only mounted filesystem in txBegin
In the Linux kernel, the following vulnerability has been resolved:
FS: JFS: Check for read-only mounted filesystem in txBegin
This patch adds a check for read-only mounted filesystem
in txBegin before starting a transaction potentially saving
from NULL pointer deref.
osv
CVE-2025-40309UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-08
CVE-2025-40309 CVE-2025-40309: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix UAF on sco_conn_free BUG: KASAN: slab-use-after-free in sco_co
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix UAF on sco_conn_free BUG: KASAN: slab-use-after-free in sco_conn_free net/bluetooth/sco.c:87 [inline] BUG: KASAN: slab-use-after-free in kref_put include/linux/kref.h:65 [inline] BUG: KASAN: slab-use-after-free in sco_conn_put+0xd
osv
CVE-2022-50618UNKNOWN≥ 4.10.0, < 4.19.270≥ 4.20.0, < 5.4.229+4 more2025-12-08
CVE-2022-50618 mmc: meson-gx: fix return value check of mmc_add_host()
mmc: meson-gx: fix return value check of mmc_add_host()
In the Linux kernel, the following vulnerability has been resolved:
mmc: meson-gx: fix return value check of mmc_add_host()
mmc_add_host() may return error, if we ignore its return value,
it will lead two issues:
1. The memory that allocated in mmc_alloc_host() is leaked.
2. In the remove() path, mmc_remove_host() will be called to
delete device, but it's not added ye
osv
CVE-2025-40314UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-08
CVE-2025-40314 CVE-2025-40314: In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp
In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget In the __cdnsp_gadget_init() and cdnsp_gadget_exit() functions, the gadget structure (pdev->gadget) was freed before its endpoints. The endpoints are linked via t
osv
CVE-2023-53760UNKNOWN≥ 6.3.0, < 6.3.32025-12-08
CVE-2023-53760 scsi: ufs: core: mcq: Fix &hwq->cq_lock deadlock issue
scsi: ufs: core: mcq: Fix &hwq->cq_lock deadlock issue
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: core: mcq: Fix &hwq->cq_lock deadlock issue
When ufshcd_err_handler() is executed, CQ event interrupt can enter waiting
for the same lock. This can happen in ufshcd_handle_mcq_cq_events() and
also in ufs_mtk_mcq_intr(). The following warning message will be generated
when &hwq->cq_lock is use
osv
CVE-2022-50624UNKNOWN≥ 4.16.0, < 4.19.264≥ 4.20.0, < 5.4.223+3 more2025-12-08
CVE-2022-50624 net: netsec: fix error handling in netsec_register_mdio()
net: netsec: fix error handling in netsec_register_mdio()
In the Linux kernel, the following vulnerability has been resolved:
net: netsec: fix error handling in netsec_register_mdio()
If phy_device_register() fails, phy_device_free() need be called to
put refcount, so memory of phy device and device name can be freed
in callback function.
If get_phy_device() fails, mdiobus_unregister() need be called,
or it will cause w
osv
CVE-2023-53749UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.4.4-12025-12-08
CVE-2023-53749 CVE-2023-53749: In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer e
In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport th
osv
CVE-2023-53765UNKNOWN≥ 4.12.0, < 6.1.16≥ 6.2.0, < 6.2.32025-12-08
CVE-2023-53765 dm cache: free background tracker's queued work in btracker_destroy
dm cache: free background tracker's queued work in btracker_destroy
In the Linux kernel, the following vulnerability has been resolved:
dm cache: free background tracker's queued work in btracker_destroy
Otherwise the kernel can BUG with:
[ 2245.426978] =============================================================================
[ 2245.435155] BUG bt_work (Tainted: G B W ): Objects remaining in bt_work on __k
osv
CVE-2023-53757UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-12-08
CVE-2023-53757 CVE-2023-53757: In the Linux kernel, the following vulnerability has been resolved: irqchip/irq-mvebu-gicp: Fix refcount leak in mvebu_gicp_probe of_irq_find_parent()
In the Linux kernel, the following vulnerability has been resolved: irqchip/irq-mvebu-gicp: Fix refcount leak in mvebu_gicp_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak.
osv
CVE-2025-40313UNKNOWN≥ 5.15.0, < 5.15.197≥ 5.16.0, < 6.1.159+3 more2025-12-08
CVE-2025-40313 ntfs3: pretend $Extend records as regular files
ntfs3: pretend $Extend records as regular files
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: pretend $Extend records as regular files
Since commit af153bb63a33 ("vfs: catch invalid modes in may_open()")
requires any inode be one of S_IFDIR/S_IFLNK/S_IFREG/S_IFCHR/S_IFBLK/
S_IFIFO/S_IFSOCK type, use S_IFREG for $Extend records.
osv
CVE-2023-53751UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-08
CVE-2023-53751 CVE-2023-53751: In the Linux kernel, the following vulnerability has been resolved: cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname TCP_Server_In
In the Linux kernel, the following vulnerability has been resolved: cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname TCP_Server_Info::hostname may be updated once or many times during reconnect, so protect its access outside reconnect path as well and then prevent any potential use-after-free bugs
osv
CVE-2025-40284UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-06
CVE-2025-40284 CVE-2025-40284: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: cancel mesh send timer when hdev removed mesh_send_done timer is
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: cancel mesh send timer when hdev removed mesh_send_done timer is not canceled when hdev is removed, which causes crash if the timer triggers after hdev is gone. Cancel the timer when MGMT removes the hdev, like other MGMT timers. Shou
osv
CVE-2025-40275UNKNOWN≥ 4.18.0, < 5.4.302≥ 5.5.0, < 5.10.247+5 more2025-12-06
CVE-2025-40275 ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd
ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd
In snd_usb_create_streams(), for UAC version 3 devices, the Interface
Association Descriptor (IAD) is retrieved via usb_ifnum_to_if(). If this
call fails, a fallback routine attempts
osv
CVE-2025-40278UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-06
CVE-2025-40278 CVE-2025-40278: In the Linux kernel, the following vulnerability has been resolved: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak Fix a K
In the Linux kernel, the following vulnerability has been resolved: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak Fix a KMSAN kernel-infoleak detected by the syzbot . [net?] KMSAN: kernel-infoleak in __skb_datagram_iter In tcf_ife_dump(), the variable 'opt' was partially initialized using
osv
CVE-2025-40289UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-06
CVE-2025-40289 CVE-2025-40289: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM Otherwise accessing th
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM Otherwise accessing them can cause a crash.
osv
CVE-2025-40267UNKNOWN≥ 6.14.0, < 6.17.92025-12-06
CVE-2025-40267 io_uring/rw: ensure allocated iovec gets cleared for early failure
io_uring/rw: ensure allocated iovec gets cleared for early failure
In the Linux kernel, the following vulnerability has been resolved:
io_uring/rw: ensure allocated iovec gets cleared for early failure
A previous commit reused the recyling infrastructure for early cleanup,
but this is not enough for the case where our internal caches have
overflowed. If this happens, then the allocated iovec can get leaked if
th
osv
CVE-2025-40288UNKNOWN≥ 4.2.0, < 6.1.159≥ 6.2.0, < 6.6.117+2 more2025-12-06
CVE-2025-40288 drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices
drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices
Previously, APU platforms (and other scenarios with uninitialized VRAM managers)
triggered a NULL pointer dereference in `ttm_resource_manager_usage()`. The root
cause is not that the `struct ttm_resou
osv