Linux Kernel vulnerabilities
14,746 known vulnerabilities affecting linux/linux_kernel.
Total CVEs
14,746
CISA KEV
29
actively exploited
Public exploits
297
Exploited in wild
31
Severity breakdown
CRITICAL122HIGH3791MEDIUM8704LOW426UNKNOWN1703
Vulnerabilities
Page 149 of 738
CVE-2023-53397MEDIUMCVSS 5.5≥ 4.1, < 4.14.322≥ 4.15, < 5.4.251+5 more2025-09-18
CVE-2023-53397 [MEDIUM] CWE-193 CVE-2023-53397: In the Linux kernel, the following vulnerability has been resolved:
modpost: fix off by one in is_e
In the Linux kernel, the following vulnerability has been resolved:
modpost: fix off by one in is_executable_section()
The > comparison should be >= to prevent an out of bounds array
access.
nvdosv
CVE-2022-50385MEDIUMCVSS 5.5≥ 4.1, < 5.10.163≥ 5.11, < 5.15.86+2 more2025-09-18
CVE-2022-50385 [MEDIUM] CVE-2022-50385: In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix an Oops in nfs_d_autom
In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix an Oops in nfs_d_automount()
When mounting from a NFSv4 referral, path->dentry can end up being a
negative dentry, so derive the struct nfs_server from the dentry
itself instead.
nvdosv
CVE-2023-53405MEDIUMCVSS 5.5fixed in 5.15.100≥ 5.16, < 6.1.18+1 more2025-09-18
CVE-2023-53405 [MEDIUM] CWE-401 CVE-2023-53405: In the Linux kernel, the following vulnerability has been resolved:
USB: gadget: gr_udc: fix memory
In the Linux kernel, the following vulnerability has been resolved:
USB: gadget: gr_udc: fix memory leak with using debugfs_lookup()
When calling debugfs_lookup() the result must have dput() called on it,
otherwise the memory will leak over time. To make things simpler, just
call debugfs_lookup_and_remove() instead which handles all of the logic
a
nvdosv
CVE-2022-50396MEDIUMCVSS 5.5≥ 4.9, < 4.14.308≥ 4.15, < 4.19.276+6 more2025-09-18
CVE-2022-50396 [MEDIUM] CWE-401 CVE-2022-50396: In the Linux kernel, the following vulnerability has been resolved:
net: sched: fix memory leak in
In the Linux kernel, the following vulnerability has been resolved:
net: sched: fix memory leak in tcindex_set_parms
Syzkaller reports a memory leak as follows:
BUG: memory leak
unreferenced object 0xffff88810c287f00 (size 256):
comm "syz-executor105", pid 3600, jiffies 4294943292 (age 12.990s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00
nvdosv
CVE-2022-50387MEDIUMCVSS 5.5≥ 5.8, < 5.10.153≥ 5.11, < 5.15.77+2 more2025-09-18
CVE-2022-50387 [MEDIUM] CWE-401 CVE-2022-50387: In the Linux kernel, the following vulnerability has been resolved:
net: hinic: fix the issue of CM
In the Linux kernel, the following vulnerability has been resolved:
net: hinic: fix the issue of CMDQ memory leaks
When hinic_set_cmdq_depth() fails in hinic_init_cmdqs(), the cmdq memory is
not released correctly. Fix it.
nvdosv
CVE-2023-53409MEDIUMCVSS 5.5fixed in 5.15.100≥ 5.16, < 6.1.18+1 more2025-09-18
CVE-2023-53409 [MEDIUM] CWE-401 CVE-2023-53409: In the Linux kernel, the following vulnerability has been resolved:
drivers: base: component: fix m
In the Linux kernel, the following vulnerability has been resolved:
drivers: base: component: fix memory leak with using debugfs_lookup()
When calling debugfs_lookup() the result must have dput() called on it,
otherwise the memory will leak over time. To make things simpler, just
call debugfs_lookup_and_remove() instead which handles all of the lo
nvdosv
CVE-2023-53410MEDIUMCVSS 5.5fixed in 6.1.18≥ 6.2, < 6.2.52025-09-18
CVE-2023-53410 [MEDIUM] CWE-401 CVE-2023-53410: In the Linux kernel, the following vulnerability has been resolved:
USB: ULPI: fix memory leak with
In the Linux kernel, the following vulnerability has been resolved:
USB: ULPI: fix memory leak with using debugfs_lookup()
When calling debugfs_lookup() the result must have dput() called on it,
otherwise the memory will leak over time. To make things simpler, just
call debugfs_lookup_and_remove() instead which handles all of the logic
at once.
nvdosv
CVE-2022-50380MEDIUMCVSS 5.5≥ 4.19, < 4.19.264≥ 4.20, < 5.4.221+3 more2025-09-18
CVE-2022-50380 [MEDIUM] CWE-476 CVE-2022-50380: In the Linux kernel, the following vulnerability has been resolved:
mm: /proc/pid/smaps_rollup: fix
In the Linux kernel, the following vulnerability has been resolved:
mm: /proc/pid/smaps_rollup: fix no vma's null-deref
Commit 258f669e7e88 ("mm: /proc/pid/smaps_rollup: convert to single value
seq_file") introduced a null-deref if there are no vma's in the task in
show_smaps_rollup.
nvdosv
CVE-2023-53402MEDIUMCVSS 5.5fixed in 5.15.100≥ 5.16, < 6.1.18+1 more2025-09-18
CVE-2023-53402 [MEDIUM] CWE-401 CVE-2023-53402: In the Linux kernel, the following vulnerability has been resolved:
kernel/printk/index.c: fix memo
In the Linux kernel, the following vulnerability has been resolved:
kernel/printk/index.c: fix memory leak with using debugfs_lookup()
When calling debugfs_lookup() the result must have dput() called on it,
otherwise the memory will leak over time. To make things simpler, just
call debugfs_lookup_and_remove() instead which handles all of the logic
nvdosv
CVE-2022-50409MEDIUMCVSS 5.5fixed in 4.14.296≥ 4.15, < 4.19.262+5 more2025-09-18
CVE-2022-50409 [MEDIUM] CWE-476 CVE-2022-50409: In the Linux kernel, the following vulnerability has been resolved:
net: If sock is dead don't acce
In the Linux kernel, the following vulnerability has been resolved:
net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory
Fixes the below NULL pointer dereference:
[...]
[ 14.471200] Call Trace:
[ 14.471562]
[ 14.471882] lock_acquire+0x245/0x2e0
[ 14.472416] ? remove_wait_queue+0x12/0x50
[ 14.473014] ? _raw_spin_lock_irqsave+0x1
nvdosv
CVE-2023-53379MEDIUMCVSS 5.5≥ 4.4.284, < 4.5≥ 4.9.283, < 4.10+8 more2025-09-18
CVE-2023-53379 [MEDIUM] CWE-401 CVE-2023-53379: In the Linux kernel, the following vulnerability has been resolved:
usb: phy: phy-tahvo: fix memory
In the Linux kernel, the following vulnerability has been resolved:
usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe()
Smatch reports:
drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe()
warn: missing unwind goto?
After geting irq, if ret < 0, it will return without error handling to
free memory.
Just add error handling to fix this problem.
nvdosv
CVE-2022-50376MEDIUMCVSS 5.5≥ 4.6, < 5.4.229≥ 5.5, < 5.10.163+3 more2025-09-18
CVE-2022-50376 [MEDIUM] CWE-401 CVE-2022-50376: In the Linux kernel, the following vulnerability has been resolved:
orangefs: Fix kmemleak in orang
In the Linux kernel, the following vulnerability has been resolved:
orangefs: Fix kmemleak in orangefs_{kernel,client}_debug_init()
When insert and remove the orangefs module, there are memory leaked
as below:
unreferenced object 0xffff88816b0cc000 (size 2048):
comm "insmod", pid 783, jiffies 4294813439 (age 65.512s)
hex dump (first 32 bytes):
6e
nvdosv
CVE-2022-50388MEDIUMCVSS 5.5≥ 5.4, < 5.10.163≥ 5.11, < 5.15.87+3 more2025-09-18
CVE-2022-50388 [MEDIUM] CWE-476 CVE-2022-50388: In the Linux kernel, the following vulnerability has been resolved:
nvme: fix multipath crash cause
In the Linux kernel, the following vulnerability has been resolved:
nvme: fix multipath crash caused by flush request when blktrace is enabled
The flush request initialized by blk_kick_flush has NULL bio,
and it may be dealt with nvme_end_req during io completion.
When blktrace is enabled, nvme_trace_bio_complete with multipath
activated trying to
nvdosv
CVE-2022-50400MEDIUMCVSS 5.5fixed in 5.10.150≥ 5.11, < 5.15.75+2 more2025-09-18
CVE-2022-50400 [MEDIUM] CWE-401 CVE-2022-50400: In the Linux kernel, the following vulnerability has been resolved:
staging: greybus: audio_helper:
In the Linux kernel, the following vulnerability has been resolved:
staging: greybus: audio_helper: remove unused and wrong debugfs usage
In the greybus audio_helper code, the debugfs file for the dapm has the
potential to be removed and memory will be leaked. There is also the
very real potential for this code to remove ALL debugfs entries from t
nvdosv
CVE-2023-53447MEDIUMCVSS 4.7≥ 3.8, < 6.4.52025-09-18
CVE-2023-53447 [MEDIUM] CWE-362 CVE-2023-53447: In the Linux kernel, the following vulnerability has been resolved:
f2fs: don't reset unchangable m
In the Linux kernel, the following vulnerability has been resolved:
f2fs: don't reset unchangable mount option in f2fs_remount()
syzbot reports a bug as below:
general protection fault, probably for non-canonical address 0xdffffc0000000009: 0000 [#1] PREEMPT SMP KASAN
RIP: 0010:__lock_acquire+0x69/0x2000 kernel/locking/lockdep.c:4942
Call Trace:
nvdosv
CVE-2022-50416MEDIUMCVSS 5.5≥ 5.13, < 5.15.86≥ 5.16, < 6.0.16+1 more2025-09-18
CVE-2022-50416 [MEDIUM] CWE-401 CVE-2022-50416: In the Linux kernel, the following vulnerability has been resolved:
irqchip/wpcm450: Fix memory lea
In the Linux kernel, the following vulnerability has been resolved:
irqchip/wpcm450: Fix memory leak in wpcm450_aic_of_init()
If of_iomap() failed, 'aic' should be freed before return. Otherwise
there is a memory leak.
nvdosv
CVE-2022-50404MEDIUMCVSS 5.5≥ 5.15.64, < 5.15.86≥ 5.19.6, < 6.0+3 more2025-09-18
CVE-2022-50404 [MEDIUM] CWE-401 CVE-2022-50404: In the Linux kernel, the following vulnerability has been resolved:
fbdev: fbcon: release buffer wh
In the Linux kernel, the following vulnerability has been resolved:
fbdev: fbcon: release buffer when fbcon_do_set_font() failed
syzbot is reporting memory leak at fbcon_do_set_font() [1], for
commit a5a923038d70 ("fbdev: fbcon: Properly revert changes when
vc_resize() failed") missed that the buffer might be newly allocated
by fbcon_set_font().
nvdosv
CVE-2023-53391MEDIUMCVSS 5.5≥ 2.6.30, < 5.10.188≥ 5.11, < 5.15.121+2 more2025-09-18
CVE-2023-53391 [MEDIUM] CVE-2023-53391: In the Linux kernel, the following vulnerability has been resolved:
shmem: use ramfs_kill_sb() for
In the Linux kernel, the following vulnerability has been resolved:
shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs
As the ramfs-based tmpfs uses ramfs_init_fs_context() for the
init_fs_context method, which allocates fc->s_fs_info, use ramfs_kill_sb()
to free it and avoid a memory leak.
nvdosv
CVE-2022-50405MEDIUMCVSS 5.5≥ 3.18, < 4.9.337≥ 4.10, < 4.14.303+6 more2025-09-18
CVE-2022-50405 [MEDIUM] CWE-476 CVE-2022-50405: In the Linux kernel, the following vulnerability has been resolved:
net/tunnel: wait until all sk_u
In the Linux kernel, the following vulnerability has been resolved:
net/tunnel: wait until all sk_user_data reader finish before releasing the sock
There is a race condition in vxlan that when deleting a vxlan device
during receiving packets, there is a possibility that the sock is
released after getting vxlan_sock vs from sk_user_data. Then in
la
nvdosv
CVE-2023-53424MEDIUMCVSS 5.5≥ 5.15, < 6.3.13≥ 6.4, < 6.4.42025-09-18
CVE-2023-53424 [MEDIUM] CWE-401 CVE-2023-53424: In the Linux kernel, the following vulnerability has been resolved:
clk: mediatek: fix of_iomap mem
In the Linux kernel, the following vulnerability has been resolved:
clk: mediatek: fix of_iomap memory leak
Smatch reports:
drivers/clk/mediatek/clk-mtk.c:583 mtk_clk_simple_probe() warn:
'base' from of_iomap() not released on lines: 496.
This problem was also found in linux-next. In mtk_clk_simple_probe(),
base is not released when handling erro
nvdosv