Linux Kernel vulnerabilities
14,742 known vulnerabilities affecting linux/linux_kernel.
Total CVEs
14,742
CISA KEV
29
actively exploited
Public exploits
296
Exploited in wild
31
Severity breakdown
CRITICAL112HIGH3715MEDIUM8619LOW440UNKNOWN1856
Vulnerabilities
Page 113 of 738
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
CVE-2025-40056UNKNOWN≥ 0, < 6.1.158-1≥ 0, < 6.12.57-1+1 more2025-10-28
CVE-2025-40056 CVE-2025-40056: In the Linux kernel, the following vulnerability has been resolved: vhost: vringh: Fix copy_to_iter return value check The return value of copy_to_ite
In the Linux kernel, the following vulnerability has been resolved: vhost: vringh: Fix copy_to_iter return value check The return value of copy_to_iter can't be negative, check whether the copied length is equal to the requested length instead of checking for negative values.
osv
CVE-2025-40061UNKNOWN≥ 6.5.0, < 6.6.112≥ 6.7.0, < 6.12.53+1 more2025-10-28
CVE-2025-40061 RDMA/rxe: Fix race in do_task() when draining
RDMA/rxe: Fix race in do_task() when draining
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Fix race in do_task() when draining
When do_task() exhausts its iteration budget (!ret), it sets the state
to TASK_STATE_IDLE to reschedule, without a secondary check on the
current task->state. This can overwrite the TASK_STATE_DRAINING state
set by a concurrent call to rxe_cleanup_task() or rxe_disable_task()
osv
CVE-2025-40033UNKNOWN≥ 6.3.0, < 6.6.112≥ 6.7.0, < 6.12.53+1 more2025-10-28
CVE-2025-40033 remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable()
remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable()
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable()
pru_rproc_set_ctable() accessed rproc->priv before the IS_ERR_OR_NULL
check, which could lead to a null pointer dereference. Move the pru
assignment, ensuring we never
osv
CVE-2025-40029UNKNOWN≥ 5.9.0, < 5.10.246≥ 5.11.0, < 5.15.195+4 more2025-10-28
CVE-2025-40029 bus: fsl-mc: Check return value of platform_get_resource()
bus: fsl-mc: Check return value of platform_get_resource()
In the Linux kernel, the following vulnerability has been resolved:
bus: fsl-mc: Check return value of platform_get_resource()
platform_get_resource() returns NULL in case of failure, so check its
return value and propagate the error in order to prevent NULL pointer
dereference.
osv
CVE-2025-40035UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-28
CVE-2025-40035 CVE-2025-40035: In the Linux kernel, the following vulnerability has been resolved: Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak Struct
In the Linux kernel, the following vulnerability has been resolved: Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak Struct ff_effect_compat is embedded twice inside uinput_ff_upload_compat, contains internal padding. In particular, there is a hole after struct ff_replay to satisfy alignment
osv
CVE-2025-40081UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-28
CVE-2025-40081 CVE-2025-40081: In the Linux kernel, the following vulnerability has been resolved: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() Cast nr_pages to unsigned long t
In the Linux kernel, the following vulnerability has been resolved: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() Cast nr_pages to unsigned long to avoid overflow when handling large AUX buffer sizes (>= 2 GiB).
osv
CVE-2025-40030UNKNOWN≥ 4.19.0, < 5.4.301≥ 5.5.0, < 5.10.246+5 more2025-10-28
CVE-2025-40030 pinctrl: check the return value of pinmux_ops::get_function_name()
pinctrl: check the return value of pinmux_ops::get_function_name()
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: check the return value of pinmux_ops::get_function_name()
While the API contract in docs doesn't specify it explicitly, the
generic implementation of the get_function_name() callback from struct
pinmux_ops - pinmux_generic_get_function_name() - can fail and return
NULL.
osv
CVE-2025-40070UNKNOWN≥ 0, < 5.4.301≥ 5.5.0, < 5.10.246+5 more2025-10-28
CVE-2025-40070 pps: fix warning in pps_register_cdev when register device fail
pps: fix warning in pps_register_cdev when register device fail
In the Linux kernel, the following vulnerability has been resolved:
pps: fix warning in pps_register_cdev when register device fail
Similar to previous commit 2a934fdb01db ("media: v4l2-dev: fix error
handling in __video_register_device()"), the release hook should be set
before device_register(). Otherwise, when device_register() return error
and put_
osv
CVE-2025-40041UNKNOWN≥ 6.17.0, < 6.17.32025-10-28
CVE-2025-40041 LoongArch: BPF: Sign-extend struct ops return values properly
LoongArch: BPF: Sign-extend struct ops return values properly
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: BPF: Sign-extend struct ops return values properly
The ns_bpf_qdisc selftest triggers a kernel panic:
Oops[#1]:
CPU 0 Unable to handle kernel paging request at virtual address 0000000000741d58, era == 90000000851b5ac0, ra == 90000000851b5aa4
CPU: 0 UID: 0 PID: 449 Comm: test_pr
osv
CVE-2025-40046UNKNOWN≥ 6.15.0, < 6.17.32025-10-28
CVE-2025-40046 io_uring/zcrx: fix overshooting recv limit
io_uring/zcrx: fix overshooting recv limit
In the Linux kernel, the following vulnerability has been resolved:
io_uring/zcrx: fix overshooting recv limit
It's reported that sometimes a zcrx request can receive more than was
requested. It's caused by io_zcrx_recv_skb() adjusting desc->count for
all received buffers including frag lists, but then doing recursive
calls to process frag list skbs, which leads to desc->count double
accountin
osv
CVE-2025-40057UNKNOWN≥ 0, < 6.12.57-1≥ 0, < 6.17.6-12025-10-28
CVE-2025-40057 CVE-2025-40057: In the Linux kernel, the following vulnerability has been resolved: ptp: Add a upper bound on max_vclocks syzbot reported WARNING in max_vclocks_store
In the Linux kernel, the following vulnerability has been resolved: ptp: Add a upper bound on max_vclocks syzbot reported WARNING in max_vclocks_store. This occurs when the argument max is too large for kcalloc to handle. Extend the guard to guard against values that are too large for kcalloc
osv
CVE-2025-40027UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-28
CVE-2025-40027 CVE-2025-40027: In the Linux kernel, the following vulnerability has been resolved: net/9p: fix double req put in p9_fd_cancelled Syzkaller reports a KASAN issue as b
In the Linux kernel, the following vulnerability has been resolved: net/9p: fix double req put in p9_fd_cancelled Syzkaller reports a KASAN issue as below: general protection fault, probably for non-canonical address 0xfbd59c0000000021: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0xdea
osv
CVE-2025-40072UNKNOWN≥ 6.16.0, < 6.17.32025-10-28
CVE-2025-40072 fanotify: Validate the return value of mnt_ns_from_dentry() before dereferencing
fanotify: Validate the return value of mnt_ns_from_dentry() before dereferencing
In the Linux kernel, the following vulnerability has been resolved:
fanotify: Validate the return value of mnt_ns_from_dentry() before dereferencing
The function do_fanotify_mark() does not validate if
mnt_ns_from_dentry() returns NULL before dereferencing mntns->user_ns.
This causes a NULL pointer dereference in do_fa
osv
CVE-2025-40071UNKNOWN≥ 0, < 6.12.57-1≥ 0, < 6.17.6-12025-10-28
CVE-2025-40071 CVE-2025-40071: In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: Don't block input queue by waiting MSC Currently gsm_queue() processes
In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: Don't block input queue by waiting MSC Currently gsm_queue() processes incoming frames and when opening a DLC channel it calls gsm_dlci_open() which calls gsm_modem_update(). If basic mode is used it calls gsm_modem_upd_via_msc() and it c
osv
CVE-2025-40060UNKNOWN≥ 5.13.0, < 5.15.195≥ 5.16.0, < 6.1.156+3 more2025-10-28
CVE-2025-40060 coresight: trbe: Return NULL pointer for allocation failures
coresight: trbe: Return NULL pointer for allocation failures
In the Linux kernel, the following vulnerability has been resolved:
coresight: trbe: Return NULL pointer for allocation failures
When the TRBE driver fails to allocate a buffer, it currently returns
the error code "-ENOMEM". However, the caller etm_setup_aux() only
checks for a NULL pointer, so it misses the error. As a result, the
driver continues and event
osv
CVE-2025-40066UNKNOWN≥ 0, < 6.17.6-12025-10-28
CVE-2025-40066 CVE-2025-40066: In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: Check phy before init msta_link in mt7996_mac_sta_add_links()
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: Check phy before init msta_link in mt7996_mac_sta_add_links() In order to avoid a possible NULL pointer dereference in mt7996_mac_sta_init_link routine, move the phy pointer check before running mt7996_mac_sta_init_link() in mt7996
osv