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 79 of 724
CVE-2023-53833UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-09
CVE-2023-53833 CVE-2023-53833: In the Linux kernel, the following vulnerability has been resolved: drm/i915: Fix NULL ptr deref by checking new_crtc_state intel_atomic_get_new_crtc_
In the Linux kernel, the following vulnerability has been resolved: drm/i915: Fix NULL ptr deref by checking new_crtc_state intel_atomic_get_new_crtc_state can return NULL, unless crtc state wasn't obtained previously with intel_atomic_get_crtc_state, so we must check it for NULLness here, just as in many other place
osv
CVE-2023-53815UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-09
CVE-2023-53815 CVE-2023-53815: In the Linux kernel, the following vulnerability has been resolved: posix-timers: Prevent RT livelock in itimer_delete() itimer_delete() has a retry l
In the Linux kernel, the following vulnerability has been resolved: posix-timers: Prevent RT livelock in itimer_delete() itimer_delete() has a retry loop when the timer is concurrently expired. On non-RT kernels this just spin-waits until the timer callback has completed, except for posix CPU timers which have HAVE_P
osv
CVE-2022-50656UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-09
CVE-2022-50656 CVE-2022-50656: In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Clear nfc_target before being used Fix a slab-out-of-bounds read that
In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Clear nfc_target before being used Fix a slab-out-of-bounds read that occurs in nla_put() called from nfc_genl_send_target() when target->sensb_res_len, which is duplicated from an nfc_target in pn533, is too large as the nfc_target is not
osv
CVE-2023-53814UNKNOWN≥ 0, < 6.1.20-12025-12-09
CVE-2023-53814 CVE-2023-53814: In the Linux kernel, the following vulnerability has been resolved: PCI: Fix dropping valid root bus resources with
In the Linux kernel, the following vulnerability has been resolved: PCI: Fix dropping valid root bus resources with .end = zero On r8a7791/koelsch: kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak) # cat /sys/kernel/debug/kmemleak unreferenced object 0xc3a34e00 (size 64): comm "swapper/0", pid 1, jiffies 4294937460 (age 199.080s)
osv
CVE-2022-50678UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-12-09
CVE-2022-50678 CVE-2022-50678: In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix invalid address access when enabling SCAN log level The variab
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix invalid address access when enabling SCAN log level The variable i is changed when setting random MAC address and causes invalid address access when printing the value of pi->reqs[i]->reqid. We replace reqs index with ri to fix th
osv
CVE-2023-53809UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-12-09
CVE-2023-53809 CVE-2023-53809: In the Linux kernel, the following vulnerability has been resolved: l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register() When a file desc
In the Linux kernel, the following vulnerability has been resolved: l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register() When a file descriptor of pppol2tp socket is passed as file descriptor of UDP socket, a recursive deadlock occurs in l2tp_tunnel_register(). This situation is reproduced by the followi
osv
CVE-2023-53789UNKNOWN≥ 0, < 6.1.20-12025-12-09
CVE-2023-53789 CVE-2023-53789: In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Improve page fault error reporting If IOMMU domain for device group is
In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Improve page fault error reporting If IOMMU domain for device group is not setup properly then we may hit IOMMU page fault. Current page fault handler assumes that domain is always setup and it will hit NULL pointer derefence (see below sam
osv
CVE-2023-53817UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-12-09
CVE-2023-53817 CVE-2023-53817: In the Linux kernel, the following vulnerability has been resolved: crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() During NVMeTCP Authenti
In the Linux kernel, the following vulnerability has been resolved: crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() During NVMeTCP Authentication a controller can trigger a kernel oops by specifying the 8192 bit Diffie Hellman group and passing a correctly sized, but zeroed Diffie Hellamn value. mpi_cmp_ui
osv
CVE-2025-40341UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-09
CVE-2025-40341 CVE-2025-40341: In the Linux kernel, the following vulnerability has been resolved: futex: Don't leak robust_list pointer on exec race sys_get_robust_list() and compa
In the Linux kernel, the following vulnerability has been resolved: futex: Don't leak robust_list pointer on exec race sys_get_robust_list() and compat_get_robust_list() use ptrace_may_access() to check if the calling task is allowed to access another task's robust_list pointer. This check is racy against a concurren
osv
CVE-2025-40343UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-09
CVE-2025-40343 CVE-2025-40343: In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid scheduling association deletion twice When forcefully shutting dow
In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid scheduling association deletion twice When forcefully shutting down a port via the configfs interface, nvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and then nvmet_disable_port(). Both functions will eventually sche
osv
CVE-2023-53805UNKNOWN≥ 0, < 5.10.190≥ 5.11.0, < 5.15.124+2 more2025-12-09
CVE-2023-53805 tty: n_gsm: fix UAF in gsm_cleanup_mux
tty: n_gsm: fix UAF in gsm_cleanup_mux
In the Linux kernel, the following vulnerability has been resolved:
tty: n_gsm: fix UAF in gsm_cleanup_mux
In gsm_cleanup_mux() the 'gsm->dlci' pointer was not cleaned properly,
leaving it a dangling pointer after gsm_dlci_release.
This leads to use-after-free where 'gsm->dlci[0]' are freed and accessed
by the subsequent gsm_cleanup_mux().
Such is the case in the following call trace:
__dump_stack
osv
CVE-2023-53856UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.3-12025-12-09
CVE-2023-53856 CVE-2023-53856: In the Linux kernel, the following vulnerability has been resolved: of: overlay: Call of_changeset_init() early When of_overlay_fdt_apply() fails, the
In the Linux kernel, the following vulnerability has been resolved: of: overlay: Call of_changeset_init() early When of_overlay_fdt_apply() fails, the changeset may be partially applied, and the caller is still expected to call of_overlay_remove() to clean up this partial state. However, of_overlay_apply() calls of_r
osv
CVE-2023-53812UNKNOWN≥ 5.18.0, < 6.1.28≥ 6.2.0, < 6.2.15+1 more2025-12-09
CVE-2023-53812 media: mediatek: vcodec: fix decoder disable pm crash
media: mediatek: vcodec: fix decoder disable pm crash
In the Linux kernel, the following vulnerability has been resolved:
media: mediatek: vcodec: fix decoder disable pm crash
Can't call pm_runtime_disable when the architecture support sub device for
'dev->pm.dev' is NUll, or will get below crash log.
[ 10.771551] pc : _raw_spin_lock_irq+0x4c/0xa0
[ 10.771556] lr : __pm_runtime_disable+0x30/0x130
[ 10.771558] sp : ffffffc01
osv
CVE-2025-40329UNKNOWN≥ 6.2.0, < 6.6.117≥ 6.7.0, < 6.12.58+1 more2025-12-09
CVE-2025-40329 drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb
drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb
In the Linux kernel, the following vulnerability has been resolved:
drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb
The Mesa issue referenced below pointed out a possible deadlock:
[ 1231.611031] Possible interrupt unsafe locking scenario:
[ 1231.611033] CPU0 CPU1
[ 1231.611034] ---- ----
[ 1231.611035] lock(&xa->xa_lock#17);
[ 1231.611038] local_irq_disa
osv
CVE-2023-53806UNKNOWN≥ 4.15.0, < 6.1.30≥ 6.2.0, < 6.3.42025-12-09
CVE-2023-53806 drm/amd/display: populate subvp cmd info only for the top pipe
drm/amd/display: populate subvp cmd info only for the top pipe
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: populate subvp cmd info only for the top pipe
[Why]
System restart observed while changing the display resolution
to 8k with extended mode. Sytem restart was caused by a page fault.
[How]
When the driver populates subvp info it did it for both the pipes using
vblank whi
osv
CVE-2023-53831UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-12-09
CVE-2023-53831 CVE-2023-53831: In the Linux kernel, the following vulnerability has been resolved: net: read sk->sk_family once in sk_mc_loop() syzbot is playing with IPV6_ADDRFORM
In the Linux kernel, the following vulnerability has been resolved: net: read sk->sk_family once in sk_mc_loop() syzbot is playing with IPV6_ADDRFORM quite a lot these days, and managed to hit the WARN_ON_ONCE(1) in sk_mc_loop() We have many more similar issues to fix. WARNING: CPU: 1 PID: 1593 at net/core/sock.c:782
osv
CVE-2025-40328UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.8-12025-12-09
CVE-2025-40328 CVE-2025-40328: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_close_cached_fid() find_or_create_cached_di
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in smb2_close_cached_fid() find_or_create_cached_dir() could grab a new reference after kref_put() had seen the refcount drop to zero but before cfid_list_lock is acquired in smb2_close_cached_fid(), leading to use-afte
osv
CVE-2022-50636UNKNOWN≥ 3.13.0, < 4.14.303≥ 4.15.0, < 4.19.270+5 more2025-12-09
CVE-2022-50636 PCI: Fix pci_device_is_present() for VFs by checking PF
PCI: Fix pci_device_is_present() for VFs by checking PF
In the Linux kernel, the following vulnerability has been resolved:
PCI: Fix pci_device_is_present() for VFs by checking PF
pci_device_is_present() previously didn't work for VFs because it reads the
Vendor and Device ID, which are 0xffff for VFs, which looks like they
aren't present. Check the PF instead.
Wei Gong reported that if virtio I/O is in progress when the
osv
CVE-2022-50646UNKNOWN≥ 4.16.0, < 4.19.270≥ 4.20.0, < 5.4.229+4 more2025-12-09
CVE-2022-50646 scsi: hpsa: Fix possible memory leak in hpsa_init_one()
scsi: hpsa: Fix possible memory leak in hpsa_init_one()
In the Linux kernel, the following vulnerability has been resolved:
scsi: hpsa: Fix possible memory leak in hpsa_init_one()
The hpda_alloc_ctlr_info() allocates h and its field reply_map. However, in
hpsa_init_one(), if alloc_percpu() failed, the hpsa_init_one() jumps to
clean1 directly, which frees h and leaks the h->reply_map.
Fix by calling hpda_free_ctlr_info() t
osv
CVE-2023-53848UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.3-12025-12-09
CVE-2023-53848 CVE-2023-53848: In the Linux kernel, the following vulnerability has been resolved: md/raid5-cache: fix a deadlock in r5l_exit_log() Commit b13015af94cf ("md/raid5-ca
In the Linux kernel, the following vulnerability has been resolved: md/raid5-cache: fix a deadlock in r5l_exit_log() Commit b13015af94cf ("md/raid5-cache: Clear conf->log after finishing work") introduce a new problem: // caller hold reconfig_mutex r5l_exit_log flush_work(&log->disable_writeback_work) r5c_disable_wri
osv