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 40 of 724
CVE-2023-54252UNKNOWN≥ 5.15.106, < 5.15.107≥ 6.1.23, < 6.1.24+1 more2025-12-30
CVE-2023-54252 platform/x86: think-lmi: Fix memory leaks when parsing ThinkStation WMI strings
platform/x86: think-lmi: Fix memory leaks when parsing ThinkStation WMI strings
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: think-lmi: Fix memory leaks when parsing ThinkStation WMI strings
My previous commit introduced a memory leak where the item allocated
from tlmi_setting was not freed.
This commit also renames it to avoid confusion with the similarly name
v
osv
CVE-2023-54210UNKNOWN≥ 6.0.0, < 6.1.42≥ 6.2.0, < 6.4.72025-12-30
CVE-2023-54210 Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
KASAN reports that there's a use-after-free in
hci_remove_adv_monitor(). Trawling through the disassembly, you can
see that the complaint is from the access in bt_dev_dbg() under t
osv
CVE-2023-54306UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-12-30
CVE-2023-54306 CVE-2023-54306: In the Linux kernel, the following vulnerability has been resolved: net: tls: avoid hanging tasks on the tx_lock syzbot sent a hung task report and Er
In the Linux kernel, the following vulnerability has been resolved: net: tls: avoid hanging tasks on the tx_lock syzbot sent a hung task report and Eric explains that adversarial receiver may keep RWIN at 0 for a long time, so we are not guaranteed to make forward progress. Thread which took tx_lock and went to sleep
osv
CVE-2022-50874UNKNOWN≥ 0, < 6.1.20-12025-12-30
CVE-2022-50874 CVE-2022-50874: In the Linux kernel, the following vulnerability has been resolved: RDMA/erdma: Fix refcount leak in erdma_mmap rdma_user_mmap_entry_get() take refere
In the Linux kernel, the following vulnerability has been resolved: RDMA/erdma: Fix refcount leak in erdma_mmap rdma_user_mmap_entry_get() take reference, we should release it when not need anymore, add the missing rdma_user_mmap_entry_put() in the error path to fix it.
osv
CVE-2023-54199UNKNOWN≥ 5.9.0, < 5.10.173≥ 5.11.0, < 5.15.99+2 more2025-12-30
CVE-2023-54199 drm/msm/adreno: Fix null ptr access in adreno_gpu_cleanup()
drm/msm/adreno: Fix null ptr access in adreno_gpu_cleanup()
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/adreno: Fix null ptr access in adreno_gpu_cleanup()
Fix the below kernel panic due to null pointer access:
[ 18.504431] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000048
[ 18.513464] Mem abort info:
[ 18.516346] ESR = 0x0000000096000005
[ 18.520204] E
osv
CVE-2023-54260UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-12-30
CVE-2023-54260 CVE-2023-54260: In the Linux kernel, the following vulnerability has been resolved: cifs: Fix lost destroy smbd connection when MR allocate failed If the MR allocate
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix lost destroy smbd connection when MR allocate failed If the MR allocate failed, the smb direct connection info is NULL, then smbd_destroy() will directly return, then the connection info will be leaked. Let's set the smb direct connection in
osv
CVE-2022-50830UNKNOWN≥ 0, < 6.1.20-12025-12-30
CVE-2022-50830 CVE-2022-50830: In the Linux kernel, the following vulnerability has been resolved: auxdisplay: hd44780: Fix potential memory leak in hd44780_remove() hd44780_probe()
In the Linux kernel, the following vulnerability has been resolved: auxdisplay: hd44780: Fix potential memory leak in hd44780_remove() hd44780_probe() allocates a memory chunk for hd with kzalloc() and makes "lcd->drvdata->hd44780" point to it. When we call hd44780_remove(), we should release all relevant memory and
osv
CVE-2023-54222UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-30
CVE-2023-54222 CVE-2023-54222: In the Linux kernel, the following vulnerability has been resolved: hte: tegra-194: Fix off by one in tegra_hte_map_to_line_id() The "map_sz" is the n
In the Linux kernel, the following vulnerability has been resolved: hte: tegra-194: Fix off by one in tegra_hte_map_to_line_id() The "map_sz" is the number of elements in the "m" array so the > comparison needs to be changed to >= to prevent an out of bounds read.
osv
CVE-2023-54185UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-12-30
CVE-2023-54185 CVE-2023-54185: In the Linux kernel, the following vulnerability has been resolved: btrfs: remove BUG_ON()'s in add_new_free_space() At add_new_free_space() we have t
In the Linux kernel, the following vulnerability has been resolved: btrfs: remove BUG_ON()'s in add_new_free_space() At add_new_free_space() we have these BUG_ON()'s that are there to deal with any failure to add free space to the in memory free space cache. Such failures are mostly -ENOMEM that should be very rare.
osv
CVE-2023-54220UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.52-1+1 more2025-12-30
CVE-2023-54220 CVE-2023-54220: In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Fix oops for port->pm on uart_change_pm() Unloading a hardware speci
In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Fix oops for port->pm on uart_change_pm() Unloading a hardware specific 8250 driver can produce error "Unable to handle kernel paging request at virtual address" about ten seconds after unloading the driver. This happens on uart_hangup(
osv
CVE-2023-54317UNKNOWN≥ 0, < 4.14.308≥ 4.15.0, < 4.19.276+5 more2025-12-30
CVE-2023-54317 dm flakey: don't corrupt the zero page
dm flakey: don't corrupt the zero page
In the Linux kernel, the following vulnerability has been resolved:
dm flakey: don't corrupt the zero page
When we need to zero some range on a block device, the function
__blkdev_issue_zero_pages submits a write bio with the bio vector pointing
to the zero page. If we use dm-flakey with corrupt bio writes option, it
will corrupt the content of the zero page which results in crashes of
various userspa
osv
CVE-2023-54311UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-30
CVE-2023-54311 CVE-2023-54311: In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock when converting an inline directory in nojournal mode In no jou
In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock when converting an inline directory in nojournal mode In no journal mode, ext4_finish_convert_inline_dir() can self-deadlock by calling ext4_handle_dirty_dirblock() when it already has taken the directory lock. There is a similar s
osv
CVE-2023-54221UNKNOWN≥ 5.18.0, < 6.1.39≥ 6.2.0, < 6.3.13+1 more2025-12-30
CVE-2023-54221 clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe
clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe
In the Linux kernel, the following vulnerability has been resolved:
clk: imx93: fix memory leak and missing unwind goto in imx93_clocks_probe
In function probe(), it returns directly without unregistered hws
when error occurs.
Fix this by adding 'goto unregister_hws;' on line 295 and
line 310.
Use devm_kzalloc() instead of kzalloc
osv
CVE-2023-54269UNKNOWN≥ 0, < 5.15.113≥ 5.16.0, < 6.1.30+1 more2025-12-30
CVE-2023-54269 SUNRPC: double free xprt_ctxt while still in use
SUNRPC: double free xprt_ctxt while still in use
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: double free xprt_ctxt while still in use
When an RPC request is deferred, the rq_xprt_ctxt pointer is moved out
of the svc_rqst into the svc_deferred_req.
When the deferred request is revisited, the pointer is copied into
the new svc_rqst - and also remains in the svc_deferred_req.
In the (rare?) case that
osv
CVE-2023-54248UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-30
CVE-2023-54248 CVE-2023-54248: In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Add check for kmemdup Since the kmemdup may return NULL pointer, it shou
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Add check for kmemdup Since the kmemdup may return NULL pointer, it should be better to add check for the return value in order to avoid NULL pointer dereference.
osv
CVE-2022-50817UNKNOWN≥ 3.17.0, < 5.10.152≥ 5.11.0, < 5.15.76+1 more2025-12-30
CVE-2022-50817 net: hsr: avoid possible NULL deref in skb_clone()
net: hsr: avoid possible NULL deref in skb_clone()
In the Linux kernel, the following vulnerability has been resolved:
net: hsr: avoid possible NULL deref in skb_clone()
syzbot got a crash [1] in skb_clone(), caused by a bug
in hsr_get_untagged_frame().
When/if create_stripped_skb_hsr() returns NULL, we must
not attempt to call skb_clone().
While we are at it, replace a WARN_ONCE() by netdev_warn_once().
[1]
general protecti
osv
CVE-2022-50862UNKNOWN≥ 5.16.0, < 6.0.72025-12-30
CVE-2022-50862 bpf: prevent decl_tag from being referenced in func_proto
bpf: prevent decl_tag from being referenced in func_proto
In the Linux kernel, the following vulnerability has been resolved:
bpf: prevent decl_tag from being referenced in func_proto
Syzkaller was able to hit the following issue:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3609 at kernel/bpf/btf.c:1946
btf_type_id_size+0x2d5/0x9d0 kernel/bpf/btf.c:1946
Modules linked in:
CPU: 0 PID: 3609 Comm: syz-executo
osv
CVE-2023-54234UNKNOWN≥ 0, < 6.1.20-12025-12-30
CVE-2023-54234 CVE-2023-54234: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization Commit c1af985d27da ("
In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization Commit c1af985d27da ("scsi: mpi3mr: Add Event acknowledgment logic") introduced an array mrioc->evtack_cmds but initialization of the array elements was missed. They are just zero cleared. T
osv
CVE-2023-54213UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-30
CVE-2023-54213 CVE-2023-54213: In the Linux kernel, the following vulnerability has been resolved: USB: sisusbvga: Add endpoint checks The syzbot fuzzer was able to provoke a WARNIN
In the Linux kernel, the following vulnerability has been resolved: USB: sisusbvga: Add endpoint checks The syzbot fuzzer was able to provoke a WARNING from the sisusbvga driver: ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 1 PID: 26 at drivers/usb/core/urb.c:504 usb_su
osv
CVE-2022-50834UNKNOWN≥ 3.13.0, < 4.14.303≥ 4.15.0, < 4.19.270+5 more2025-12-30
CVE-2022-50834 nfc: Fix potential resource leaks
nfc: Fix potential resource leaks
In the Linux kernel, the following vulnerability has been resolved:
nfc: Fix potential resource leaks
nfc_get_device() take reference for the device, add missing
nfc_put_device() to release it when not need anymore.
Also fix the style warnning by use error EOPNOTSUPP instead of
ENOTSUPP.
osv