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 114 of 738
CVE-2025-40026UNKNOWN≥ 3.0.0, < 5.4.301≥ 5.5.0, < 5.10.246+6 more2025-10-28
CVE-2025-40026 KVM: x86: Don't (re)check L1 intercepts when completing userspace I/O
KVM: x86: Don't (re)check L1 intercepts when completing userspace I/O
In the Linux kernel, the following vulnerability has been resolved:
KVM: x86: Don't (re)check L1 intercepts when completing userspace I/O
When completing emulation of instruction that generated a userspace exit
for I/O, don't recheck L1 intercepts as KVM has already finished that
phase of instruction execution, i.e. has already committed to
osv
CVE-2025-40079UNKNOWN≥ 6.6.0, < 6.12.53≥ 6.13.0, < 6.17.32025-10-28
CVE-2025-40079 riscv, bpf: Sign extend struct ops return values properly
riscv, bpf: Sign extend struct ops return values properly
In the Linux kernel, the following vulnerability has been resolved:
riscv, bpf: Sign extend struct ops return values properly
The ns_bpf_qdisc selftest triggers a kernel panic:
Unable to handle kernel paging request at virtual address ffffffffa38dbf58
Current test_progs pgtable: 4K pagesize, 57-bit VAs, pgdp=0x00000001109cc000
[ffffffffa38dbf58] pgd=000000011fffd
osv
CVE-2025-40044UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-28
CVE-2025-40044 CVE-2025-40044: In the Linux kernel, the following vulnerability has been resolved: fs: udf: fix OOB read in lengthAllocDescs handling When parsing Allocation Extent
In the Linux kernel, the following vulnerability has been resolved: fs: udf: fix OOB read in lengthAllocDescs handling When parsing Allocation Extent Descriptor, lengthAllocDescs comes from on-disk data and must be validated against the block size. Crafted or corrupted images may set lengthAllocDescs so that the total
osv
CVE-2025-40022UNKNOWN≥ 6.1.154, < 6.1.155≥ 6.6.108, < 6.6.109+2 more2025-10-24
CVE-2025-40022 crypto: af_alg - Fix incorrect boolean values in af_alg_ctx
crypto: af_alg - Fix incorrect boolean values in af_alg_ctx
In the Linux kernel, the following vulnerability has been resolved:
crypto: af_alg - Fix incorrect boolean values in af_alg_ctx
Commit 1b34cbbf4f01 ("crypto: af_alg - Disallow concurrent writes in
af_alg_sendmsg") changed some fields from bool to 1-bit bitfields of
type u32.
However, some assignments to these fields, specifically 'more' and
'merge', assign va
osv
CVE-2025-40021UNKNOWN≥ 5.4.0, < 5.10.245≥ 5.11.0, < 5.15.194+4 more2025-10-24
CVE-2025-40021 tracing: dynevent: Add a missing lockdown check on dynevent
tracing: dynevent: Add a missing lockdown check on dynevent
In the Linux kernel, the following vulnerability has been resolved:
tracing: dynevent: Add a missing lockdown check on dynevent
Since dynamic_events interface on tracefs is compatible with
kprobe_events and uprobe_events, it should also check the lockdown
status and reject if it is set.
osv
CVE-2025-40024UNKNOWN≥ 6.4.0, < 6.6.109≥ 6.7.0, < 6.12.50+1 more2025-10-24
CVE-2025-40024 vhost: Take a reference on the task in struct vhost_task.
vhost: Take a reference on the task in struct vhost_task.
In the Linux kernel, the following vulnerability has been resolved:
vhost: Take a reference on the task in struct vhost_task.
vhost_task_create() creates a task and keeps a reference to its
task_struct. That task may exit early via a signal and its task_struct
will be released.
A pending vhost_task_wake() will then attempt to wake the task and
access a task_struct
osv
CVE-2025-40020UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-24
CVE-2025-40020 CVE-2025-40020: In the Linux kernel, the following vulnerability has been resolved: can: peak_usb: fix shift-out-of-bounds issue Explicitly uses a 64-bit constant whe
In the Linux kernel, the following vulnerability has been resolved: can: peak_usb: fix shift-out-of-bounds issue Explicitly uses a 64-bit constant when the number of bits used for its shifting is 32 (which is the case for PC CAN FD interfaces supported by this driver). [mkl: update subject, apply manually]
osv
CVE-2025-40019UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-24
CVE-2025-40019 CVE-2025-40019: In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Check ssize for decryption and in-place encryption Move the ssize
In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Check ssize for decryption and in-place encryption Move the ssize check to the start in essiv_aead_crypt so that it's also checked for decryption and in-place encryption.
osv
CVE-2025-40023UNKNOWN≥ 0, < 6.16.10-12025-10-24
CVE-2025-40023 CVE-2025-40023: In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Don't expose sysfs attributes not applicable for VFs VFs can't read BMG
In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Don't expose sysfs attributes not applicable for VFs VFs can't read BMG_PCIE_CAP(0x138340) register nor access PCODE (already guarded by the info.skip_pcode flag) so we shouldn't expose attributes that require any of them to avoid errors l
osv
CVE-2023-53733UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-10-24
CVE-2023-53733 CVE-2023-53733: In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode When u32_replace
In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms.
osv
CVE-2022-50561UNKNOWN≥ 0, < 6.1.4-12025-10-22
CVE-2022-50561 CVE-2022-50561: In the Linux kernel, the following vulnerability has been resolved: iio: fix memory leak in iio_device_register_eventset() When iio_device_register_sy
In the Linux kernel, the following vulnerability has been resolved: iio: fix memory leak in iio_device_register_eventset() When iio_device_register_sysfs_group() returns failed, iio_device_register_eventset() needs to free attrs array. Otherwise, kmemleak would scan & report memory leak as below: unreferenced object
osv
CVE-2022-50559UNKNOWN≥ 0, < 6.0.3-12025-10-22
CVE-2022-50559 CVE-2022-50559: In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: fix memleak on platform_device_add() fails No error handling is per
In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: fix memleak on platform_device_add() fails No error handling is performed when platform_device_add() fails. Add error processing before return, and modified the return value.
osv
CVE-2022-50563UNKNOWN≥ 3.2.0, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-10-22
CVE-2022-50563 dm thin: Fix UAF in run_timer_softirq()
dm thin: Fix UAF in run_timer_softirq()
In the Linux kernel, the following vulnerability has been resolved:
dm thin: Fix UAF in run_timer_softirq()
When dm_resume() and dm_destroy() are concurrent, it will
lead to UAF, as follows:
BUG: KASAN: use-after-free in __run_timers+0x173/0x710
Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0
Call Trace:
dump_stack_lvl+0x73/0x9f
print_report.cold+0x132/0xaa2
_raw_spin_lock_irqsave+0x
osv
CVE-2023-53718UNKNOWN≥ 3.5.0, < 5.10.192≥ 5.11.0, < 5.15.128+2 more2025-10-22
CVE-2023-53718 ring-buffer: Do not swap cpu_buffer during resize process
ring-buffer: Do not swap cpu_buffer during resize process
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Do not swap cpu_buffer during resize process
When ring_buffer_swap_cpu was called during resize process,
the cpu buffer was swapped in the middle, resulting in incorrect state.
Continuing to run in the wrong state will result in oops.
This issue can be easily reproduced using the fol
osv
CVE-2022-50566UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-10-22
CVE-2022-50566 CVE-2022-50566: In the Linux kernel, the following vulnerability has been resolved: mtd: Fix device name leak when register device failed in add_mtd_device() There is
In the Linux kernel, the following vulnerability has been resolved: mtd: Fix device name leak when register device failed in add_mtd_device() There is a kmemleak when register device failed: unreferenced object 0xffff888101aab550 (size 8): comm "insmod", pid 3922, jiffies 4295277753 (age 925.408s) hex dump (first 8 b
osv
CVE-2022-50558UNKNOWN≥ 6.0.0, < 6.0.16≥ 6.1.0, < 6.1.22025-10-22
CVE-2022-50558 regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode
regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode
In the Linux kernel, the following vulnerability has been resolved:
regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode
Commit faa87ce9196d ("regmap-irq: Introduce config registers for irq
types") added the num_config_regs, then commit 9edd4f5aee84 ("regmap-irq:
Deprecate type registers and virtu
osv
CVE-2023-53716UNKNOWN≥ 4.14.315, < 4.14.316≥ 4.19.283, < 4.19.284+5 more2025-10-22
CVE-2023-53716 net: fix skb leak in __skb_tstamp_tx()
net: fix skb leak in __skb_tstamp_tx()
In the Linux kernel, the following vulnerability has been resolved:
net: fix skb leak in __skb_tstamp_tx()
Commit 50749f2dd685 ("tcp/udp: Fix memleaks of sk and zerocopy skbs with
TX timestamp.") added a call to skb_orphan_frags_rx() to fix leaks with
zerocopy skbs. But it ended up adding a leak of its own. When
skb_orphan_frags_rx() fails, the function just returns, leaking the skb
it just cloned. Fr
osv
CVE-2022-50580UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-10-22
CVE-2022-50580 CVE-2022-50580: In the Linux kernel, the following vulnerability has been resolved: blk-throttle: prevent overflow while calculating wait time There is a problem foun
In the Linux kernel, the following vulnerability has been resolved: blk-throttle: prevent overflow while calculating wait time There is a problem found by code review in tg_with_in_bps_limit() that 'bps_limit * jiffy_elapsed_rnd' might overflow. Fix the problem by calling mul_u64_u64_div_u64() instead.
osv
CVE-2022-50578UNKNOWN≥ 4.10.0, < 4.14.303≥ 4.15.0, < 4.19.270+5 more2025-10-22
CVE-2022-50578 class: fix possible memory leak in __class_register()
class: fix possible memory leak in __class_register()
In the Linux kernel, the following vulnerability has been resolved:
class: fix possible memory leak in __class_register()
If class_add_groups() returns error, the 'cp->subsys' need be
unregister, and the 'cp' need be freed.
We can not call kset_unregister() here, because the 'cls' will
be freed in callback function class_release() and it's also
freed in caller's error pa
osv
CVE-2023-53695UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-10-22
CVE-2023-53695 CVE-2023-53695: In the Linux kernel, the following vulnerability has been resolved: udf: Detect system inodes linked into directory hierarchy When UDF filesystem is c
In the Linux kernel, the following vulnerability has been resolved: udf: Detect system inodes linked into directory hierarchy When UDF filesystem is corrupted, hidden system inodes can be linked into directory hierarchy which is an avenue for further serious corruption of the filesystem and kernel confusion as notice
osv