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 73 of 724
CVE-2025-68253UNKNOWN≥ 0, < 6.17.6-12025-12-16
CVE-2025-68253 CVE-2025-68253: In the Linux kernel, the following vulnerability has been resolved: mm: don't spin in add_stack_record when gfp flags don't allow syzbot was able to f In the Linux kernel, the following vulnerability has been resolved: mm: don't spin in add_stack_record when gfp flags don't allow syzbot was able to find the following path: add_stack_record_to_list mm/page_owner.c:182 [inline] inc_stack_record_count mm/page_owner.c:214 [inline] __set_page_owner+0x2c3/0x4a0 mm/page_o
osv
CVE-2025-68209UNKNOWN≥ 6.0.0, < 6.17.92025-12-16
CVE-2025-68209 mlx5: Fix default values in create CQ mlx5: Fix default values in create CQ In the Linux kernel, the following vulnerability has been resolved: mlx5: Fix default values in create CQ Currently, CQs without a completion function are assigned the mlx5_add_cq_to_tasklet function by default. This is problematic since only user CQs created through the mlx5_ib driver are intended to use this function. Additionally, all CQs that will use doorbells instead of polling for completions mu
osv
CVE-2025-68303UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-16
CVE-2025-68303 CVE-2025-68303: In the Linux kernel, the following vulnerability has been resolved: platform/x86: intel: punit_ipc: fix memory corruption This passes the address of t In the Linux kernel, the following vulnerability has been resolved: platform/x86: intel: punit_ipc: fix memory corruption This passes the address of the pointer "&punit_ipcdev" when the intent was to pass the pointer itself "punit_ipcdev" (without the ampersand). This means that the: complete(&ipcdev->cmd_complete);
osv
CVE-2025-68293UNKNOWN≥ 6.9.0, < 6.12.61≥ 6.13.0, < 6.17.112025-12-16
CVE-2025-68293 mm/huge_memory: fix NULL pointer deference when splitting folio mm/huge_memory: fix NULL pointer deference when splitting folio In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: fix NULL pointer deference when splitting folio Commit c010d47f107f ("mm: thp: split huge page to any lower order pages") introduced an early check on the folio's order via mapping->flags before proceeding with the split work. This check introduced a bug: for shmem fol
osv
CVE-2025-40347UNKNOWN≥ 5.12.0, < 6.6.115≥ 6.7.0, < 6.12.56+1 more2025-12-16
CVE-2025-40347 net: enetc: fix the deadlock of enetc_mdio_lock net: enetc: fix the deadlock of enetc_mdio_lock In the Linux kernel, the following vulnerability has been resolved: net: enetc: fix the deadlock of enetc_mdio_lock After applying the workaround for err050089, the LS1028A platform experiences RCU stalls on RT kernel. This issue is caused by the recursive acquisition of the read lock enetc_mdio_lock. Here list some of the call stacks identified under the enetc_poll path that may lea
osv
CVE-2025-68294UNKNOWN≥ 0, < 6.17.11-12025-12-16
CVE-2025-68294 CVE-2025-68294: In the Linux kernel, the following vulnerability has been resolved: io_uring/net: ensure vectored buffer node import is tied to notification When supp In the Linux kernel, the following vulnerability has been resolved: io_uring/net: ensure vectored buffer node import is tied to notification When support for vectored registered buffers was added, the import itself is using 'req' rather than the notification io_kiocb, sr->notif. For non-vectored imports, sr->notif is
osv
CVE-2025-68210UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-16
CVE-2025-68210 CVE-2025-68210: In the Linux kernel, the following vulnerability has been resolved: erofs: avoid infinite loop due to incomplete zstd-compressed data Currently, the d In the Linux kernel, the following vulnerability has been resolved: erofs: avoid infinite loop due to incomplete zstd-compressed data Currently, the decompression logic incorrectly spins if compressed data is truncated in crafted (deliberately corrupted) images.
osv
CVE-2025-68216UNKNOWN≥ 0, < 6.17.10-12025-12-16
CVE-2025-68216 CVE-2025-68216: In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Disable trampoline for kernel module function trace The current Lo In the Linux kernel, the following vulnerability has been resolved: LoongArch: BPF: Disable trampoline for kernel module function trace The current LoongArch BPF trampoline implementation is incompatible with tracing functions in kernel modules. This causes several severe and user-visible problems: * The `bpf_selftes
osv
CVE-2025-68301UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68301 CVE-2025-68301: In the Linux kernel, the following vulnerability has been resolved: net: atlantic: fix fragment overflow handling in RX path The atlantic driver can r In the Linux kernel, the following vulnerability has been resolved: net: atlantic: fix fragment overflow handling in RX path The atlantic driver can receive packets with more than MAX_SKB_FRAGS (17) fragments when handling large multi-descriptor packets. This causes an out-of-bounds write in skb_add_rx_frag_netmem()
osv
CVE-2025-68314UNKNOWN≥ 0, < 6.17.8-12025-12-16
CVE-2025-68314 CVE-2025-68314: In the Linux kernel, the following vulnerability has been resolved: drm/msm: make sure last_fence is always updated Update last_fence in the vm-bind p In the Linux kernel, the following vulnerability has been resolved: drm/msm: make sure last_fence is always updated Update last_fence in the vm-bind path instead of kernel managed path. last_fence is used to wait for work to finish in vm_bind contexts but not used for kernel managed contexts. This fixes a bug where l
osv
CVE-2025-68213UNKNOWN≥ 0, < 6.12.60≥ 6.13.0, < 6.17.102025-12-16
CVE-2025-68213 idpf: fix possible vport_config NULL pointer deref in remove idpf: fix possible vport_config NULL pointer deref in remove In the Linux kernel, the following vulnerability has been resolved: idpf: fix possible vport_config NULL pointer deref in remove Attempting to remove the driver will cause a crash in cases where the vport failed to initialize. Following trace is from an instance where the driver failed during an attempt to create a VF: [ 1661.543624] idpf 0000:84:00.7: Devic
osv
CVE-2025-68319UNKNOWN≥ 6.9.0, < 6.17.82025-12-16
CVE-2025-68319 netconsole: Acquire su_mutex before navigating configs hierarchy netconsole: Acquire su_mutex before navigating configs hierarchy In the Linux kernel, the following vulnerability has been resolved: netconsole: Acquire su_mutex before navigating configs hierarchy There is a race between operations that iterate over the userdata cg_children list and concurrent add/remove of userdata items through configfs. The update_userdata() function iterates over the nt->userdata_group.cg_chi
osv
CVE-2025-68251UNKNOWN≥ 6.8.0, < 6.17.62025-12-16
CVE-2025-68251 erofs: avoid infinite loops due to corrupted subpage compact indexes erofs: avoid infinite loops due to corrupted subpage compact indexes In the Linux kernel, the following vulnerability has been resolved: erofs: avoid infinite loops due to corrupted subpage compact indexes Robert reported an infinite loop observed by two crafted images. The root cause is that `clusterofs` can be larger than `lclustersize` for !NONHEAD `lclusters` in corrupted subpage compact indexes, e.g.: b
osv
CVE-2025-68183UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.8-12025-12-16
CVE-2025-68183 CVE-2025-68183: In the Linux kernel, the following vulnerability has been resolved: ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr Currently In the Linux kernel, the following vulnerability has been resolved: ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr Currently when both IMA and EVM are in fix mode, the IMA signature will be reset to IMA hash if a program first stores IMA signature in security.ima and then writes/removes some o
osv
CVE-2025-68299UNKNOWN≥ 0, < 6.17.11-12025-12-16
CVE-2025-68299 CVE-2025-68299: In the Linux kernel, the following vulnerability has been resolved: afs: Fix delayed allocation of a cell's anonymous key The allocation of a cell's a In the Linux kernel, the following vulnerability has been resolved: afs: Fix delayed allocation of a cell's anonymous key The allocation of a cell's anonymous key is done in a background thread along with other cell setup such as doing a DNS upcall. In the reported bug, this is triggered by afs_parse_source() parsing
osv
CVE-2025-68298UNKNOWN≥ 0, < 6.12.61≥ 6.13.0, < 6.17.112025-12-16
CVE-2025-68298 Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref In btusb_mtk_setup(), we set `btmtk_data->isopkt_intf` to: usb_ifnum_to_if(data->udev, MTK_ISO_IFNUM) That function can return NULL in some cases. Even when it returns NULL, though, we still go on
osv
CVE-2025-68231UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-16
CVE-2025-68231 CVE-2025-68231: In the Linux kernel, the following vulnerability has been resolved: mm/mempool: fix poisoning order>0 pages with HIGHMEM The kernel test has reported: In the Linux kernel, the following vulnerability has been resolved: mm/mempool: fix poisoning order>0 pages with HIGHMEM The kernel test has reported: BUG: unable to handle page fault for address: fffba000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page *pde = 03171067 *pte = 00
osv
CVE-2025-68234UNKNOWN≥ 6.17.0, < 6.17.102025-12-16
CVE-2025-68234 io_uring/cmd_net: fix wrong argument types for skb_queue_splice() io_uring/cmd_net: fix wrong argument types for skb_queue_splice() In the Linux kernel, the following vulnerability has been resolved: io_uring/cmd_net: fix wrong argument types for skb_queue_splice() If timestamp retriving needs to be retried and the local list of SKB's already has entries, then it's spliced back into the socket queue. However, the arguments for the splice helper are transposed, causing exactly t
osv
CVE-2025-68308UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68308 CVE-2025-68308: In the Linux kernel, the following vulnerability has been resolved: can: kvaser_usb: leaf: Fix potential infinite loop in command parsers The `kvaser_ In the Linux kernel, the following vulnerability has been resolved: can: kvaser_usb: leaf: Fix potential infinite loop in command parsers The `kvaser_usb_leaf_wait_cmd()` and `kvaser_usb_leaf_read_bulk_callback` functions contain logic to zero-length commands. These commands are used to align data to the USB endpoint
osv
CVE-2025-68212UNKNOWN≥ 0, < 6.17.10-12025-12-16
CVE-2025-68212 CVE-2025-68212: In the Linux kernel, the following vulnerability has been resolved: fs: Fix uninitialized 'offp' in statmount_string() In statmount_string(), most fla In the Linux kernel, the following vulnerability has been resolved: fs: Fix uninitialized 'offp' in statmount_string() In statmount_string(), most flags assign an output offset pointer (offp) which is later updated with the string offset. However, the STATMOUNT_MNT_UIDMAP and STATMOUNT_MNT_GIDMAP cases directly set t
osv