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 99 of 724
CVE-2025-40055UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-28
CVE-2025-40055 CVE-2025-40055: In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix double free in user_cluster_connect() user_cluster_disconnect() frees " In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix double free in user_cluster_connect() user_cluster_disconnect() frees "conn->cc_private" which is "lc" but then the error handling frees "lc" a second time. Set "lc" to NULL on this path to avoid a double free.
osv
CVE-2025-40062UNKNOWN≥ 0, < 6.1.156≥ 6.2.0, < 6.6.112+2 more2025-10-28
CVE-2025-40062 crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs When the initialization of qm->debug.acc_diff_reg fails, the probe process does not exit. However, after qm->debug.qm_diff_regs is freed, it is not set to NULL. This can lead to a double free when the remove process attempts to free it agai
osv
CVE-2025-40054UNKNOWN≥ 5.5.0, < 6.17.32025-10-28
CVE-2025-40054 f2fs: fix UAF issue in f2fs_merge_page_bio() f2fs: fix UAF issue in f2fs_merge_page_bio() In the Linux kernel, the following vulnerability has been resolved: f2fs: fix UAF issue in f2fs_merge_page_bio() As JY reported in bugzilla [1], Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 pc : [0xffffffe51d249484] f2fs_is_cp_guaranteed+0x70/0x98 lr : [0xffffffe51d24adbc] f2fs_merge_page_bio+0x520/0x6d4 CPU: 3 UID: 0 PID: 6790 Comm: kworker/u16:3 T
osv
CVE-2025-40043UNKNOWN≥ 0, < 6.1.158-1≥ 0, < 6.12.57-1+1 more2025-10-28
CVE-2025-40043 CVE-2025-40043: In the Linux kernel, the following vulnerability has been resolved: net: nfc: nci: Add parameter validation for packet data Syzbot reported an uniniti In the Linux kernel, the following vulnerability has been resolved: net: nfc: nci: Add parameter validation for packet data Syzbot reported an uninitialized value bug in nci_init_req, which was introduced by commit 5aca7966d2a7 ("Merge tag 'perf-tools-fixes-for-v6.17-2025-09-16' of git://git.kernel.org/pub/scm/linux/
osv
CVE-2025-40065UNKNOWN≥ 0, < 6.17.6-12025-10-28
CVE-2025-40065 CVE-2025-40065: In the Linux kernel, the following vulnerability has been resolved: RISC-V: KVM: Write hgatp register with valid mode bits According to the RISC-V Pri In the Linux kernel, the following vulnerability has been resolved: RISC-V: KVM: Write hgatp register with valid mode bits According to the RISC-V Privileged Architecture Spec, when MODE=Bare is selected,software must write zero to the remaining fields of hgatp. We have detected the valid mode supported by the HW bef
osv
CVE-2025-40051UNKNOWN≥ 0, < 6.1.158-1≥ 0, < 6.12.57-1+1 more2025-10-28
CVE-2025-40051 CVE-2025-40051: In the Linux kernel, the following vulnerability has been resolved: vhost: vringh: Modify the return value check The return value of copy_from_iter an In the Linux kernel, the following vulnerability has been resolved: vhost: vringh: Modify the return value check The return value of copy_from_iter and copy_to_iter can't be negative, check whether the copied lengths are equal.
osv
CVE-2025-40031UNKNOWN≥ 0, < 6.12.57-1≥ 0, < 6.17.6-12025-10-28
CVE-2025-40031 CVE-2025-40031: In the Linux kernel, the following vulnerability has been resolved: tee: fix register_shm_helper() In register_shm_helper(), fix incorrect error handl In the Linux kernel, the following vulnerability has been resolved: tee: fix register_shm_helper() In register_shm_helper(), fix incorrect error handling for a call to iov_iter_extract_pages(). A case is missing for when iov_iter_extract_pages() only got some pages and return a number larger than 0, but not the reque
osv
CVE-2025-40077UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.6-12025-10-28
CVE-2025-40077 CVE-2025-40077: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid overflow while left shift operation Should cast type of folio-> In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid overflow while left shift operation Should cast type of folio->index from pgoff_t to loff_t to avoid overflow while left shift operation.
osv
CVE-2025-40047UNKNOWN≥ 6.7.0, < 6.12.53≥ 6.13.0, < 6.17.32025-10-28
CVE-2025-40047 io_uring/waitid: always prune wait queue entry in io_waitid_wait() io_uring/waitid: always prune wait queue entry in io_waitid_wait() In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: always prune wait queue entry in io_waitid_wait() For a successful return, always remove our entry from the wait queue entry list. Previously this was skipped if a cancelation was in progress, but this can race with another invocation of the wait queue entry call
osv
CVE-2025-40032UNKNOWN≥ 5.7.0, < 6.1.157≥ 6.2.0, < 6.6.113+2 more2025-10-28
CVE-2025-40032 PCI: endpoint: pci-epf-test: Add NULL check for DMA channels before release PCI: endpoint: pci-epf-test: Add NULL check for DMA channels before release In the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: pci-epf-test: Add NULL check for DMA channels before release The fields dma_chan_tx and dma_chan_rx of the struct pci_epf_test can be NULL even after EPF initialization. Then it is prudent to check that they have non-NULL values before releasing t
osv
CVE-2025-40025UNKNOWN≥ 0, < 6.17.6-12025-10-28
CVE-2025-40025 CVE-2025-40025: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node footer for non inode dnode As syzbot reported In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node footer for non inode dnode As syzbot reported below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/file.c:1243! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 5354 Comm: syz.0.0 No
osv
CVE-2025-40037UNKNOWN≥ 6.8.0, < 6.12.53≥ 6.13.0, < 6.17.32025-10-28
CVE-2025-40037 fbdev: simplefb: Fix use after free in simplefb_detach_genpds() fbdev: simplefb: Fix use after free in simplefb_detach_genpds() In the Linux kernel, the following vulnerability has been resolved: fbdev: simplefb: Fix use after free in simplefb_detach_genpds() The pm_domain cleanup can not be devres managed as it uses struct simplefb_par which is allocated within struct fb_info by framebuffer_alloc(). This allocation is explicitly freed by unregister_framebuffer() in simplefb_re
osv
CVE-2025-40052UNKNOWN≥ 6.3.0, < 6.6.112≥ 6.7.0, < 6.12.53+1 more2025-10-28
CVE-2025-40052 smb: client: fix crypto buffers in non-linear memory smb: client: fix crypto buffers in non-linear memory In the Linux kernel, the following vulnerability has been resolved: smb: client: fix crypto buffers in non-linear memory The crypto API, through the scatterlist API, expects input buffers to be in linear memory. We handle this with the cifs_sg_set_buf() helper that converts vmalloc'd memory to their corresponding pages. However, when we allocate our aead_request buffer (@c
osv
CVE-2025-40053UNKNOWN≥ 2.6.12, < 5.10.246≥ 5.11.0, < 5.15.195+4 more2025-10-28
CVE-2025-40053 net: dlink: handle copy_thresh allocation failure net: dlink: handle copy_thresh allocation failure In the Linux kernel, the following vulnerability has been resolved: net: dlink: handle copy_thresh allocation failure The driver did not handle failure of `netdev_alloc_skb_ip_align()`. If the allocation failed, dereferencing `skb->protocol` could lead to a NULL pointer dereference. This patch tries to allocate `skb`. If the allocation fails, it falls back to the normal path. T
osv
CVE-2025-40074UNKNOWN≥ 4.13.0, < 6.17.32025-10-28
CVE-2025-40074 ipv4: start using dst_dev_rcu() ipv4: start using dst_dev_rcu() In the Linux kernel, the following vulnerability has been resolved: ipv4: start using dst_dev_rcu() Change icmpv4_xrlim_allow(), ip_defrag() to prevent possible UAF. Change ipmr_prepare_xmit(), ipmr_queue_fwd_xmit(), ip_mr_output(), ipv4_neigh_lookup() to use lockdep enabled dst_dev_rcu().
osv
CVE-2025-40063UNKNOWN≥ 0, < 6.17.6-12025-10-28
CVE-2025-40063 CVE-2025-40063: In the Linux kernel, the following vulnerability has been resolved: crypto: comp - Use same definition of context alloc and free ops In commit 42d9f6c In the Linux kernel, the following vulnerability has been resolved: crypto: comp - Use same definition of context alloc and free ops In commit 42d9f6c77479 ("crypto: acomp - Move scomp stream allocation code into acomp"), the crypto_acomp_streams struct was made to rely on having the alloc_ctx and free_ctx operations
osv
CVE-2025-40058UNKNOWN≥ 6.7.0, < 6.12.53≥ 6.13.0, < 6.17.32025-10-28
CVE-2025-40058 iommu/vt-d: Disallow dirty tracking if incoherent page walk iommu/vt-d: Disallow dirty tracking if incoherent page walk In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Disallow dirty tracking if incoherent page walk Dirty page tracking relies on the IOMMU atomically updating the dirty bit in the paging-structure entry. For this operation to succeed, the paging- structure memory must be coherent between the IOMMU and the CPU. In another word, if t
osv
CVE-2025-40076UNKNOWN≥ 6.17.0, < 6.17.32025-10-28
CVE-2025-40076 PCI: rcar-host: Pass proper IRQ domain to generic_handle_domain_irq() PCI: rcar-host: Pass proper IRQ domain to generic_handle_domain_irq() In the Linux kernel, the following vulnerability has been resolved: PCI: rcar-host: Pass proper IRQ domain to generic_handle_domain_irq() Starting with commit dd26c1a23fd5 ("PCI: rcar-host: Switch to msi_create_parent_irq_domain()"), the MSI parent IRQ domain is NULL because the object of type struct irq_domain_info passed to: msi_create_p
osv
CVE-2025-40048UNKNOWN≥ 4.10.0, < 5.4.301≥ 5.5.0, < 5.10.246+5 more2025-10-28
CVE-2025-40048 uio_hv_generic: Let userspace take care of interrupt mask uio_hv_generic: Let userspace take care of interrupt mask In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Let userspace take care of interrupt mask Remove the logic to set interrupt mask by default in uio_hv_generic driver as the interrupt mask value is supposed to be controlled completely by the user space. If the mask bit gets changed by the driver, concurrently with user mode operat
osv
CVE-2025-40059UNKNOWN≥ 6.8.0, < 6.12.53≥ 6.13.0, < 6.17.32025-10-28
CVE-2025-40059 coresight: Fix incorrect handling for return value of devm_kzalloc coresight: Fix incorrect handling for return value of devm_kzalloc In the Linux kernel, the following vulnerability has been resolved: coresight: Fix incorrect handling for return value of devm_kzalloc The return value of devm_kzalloc could be an null pointer, use "!desc.pdata" to fix incorrect handling return value of devm_kzalloc.
osv