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 61 of 724
CVE-2022-50779UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50779 CVE-2022-50779: In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string() When insert and r
In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string() When insert and remove the orangefs module, then debug_help_string will be leaked: unreferenced object 0xffff8881652ba000 (size 4096): comm "insmod", pid 1701, jiffies 4294893639 (age 1
osv
CVE-2022-50728UNKNOWN≥ 2.6.32, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-12-24
CVE-2022-50728 s390/lcs: Fix return type of lcs_start_xmit()
s390/lcs: Fix return type of lcs_start_xmit()
In the Linux kernel, the following vulnerability has been resolved:
s390/lcs: Fix return type of lcs_start_xmit()
With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
indirect call targets are validated against the expected function
pointer prototype to make sure the call target is valid to help mitigate
ROP attacks. If they are not identical, there is a failure at run ti
osv
CVE-2023-54103UNKNOWN≥ 0, < 5.10.205-1≥ 0, < 6.1.55-1+1 more2025-12-24
CVE-2023-54103 CVE-2023-54103: In the Linux kernel, the following vulnerability has been resolved: media: mtk-jpeg: Fix use after free bug due to uncanceled work In mtk_jpeg_probe,
In the Linux kernel, the following vulnerability has been resolved: media: mtk-jpeg: Fix use after free bug due to uncanceled work In mtk_jpeg_probe, &jpeg->job_timeout_work is bound with mtk_jpeg_job_timeout_work. Then mtk_jpeg_dec_device_run and mtk_jpeg_enc_device_run may be called to start the work. If we remove t
osv
CVE-2022-50735UNKNOWN≥ 0, < 6.1.4-12025-12-24
CVE-2022-50735 CVE-2022-50735: In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: do not run mt76u_status_worker if the device is not running Fix the fo
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: do not run mt76u_status_worker if the device is not running Fix the following NULL pointer dereference avoiding to run mt76u_status_worker thread if the device is not running yet. KASAN: null-ptr-deref in range [0x0000000000000000-0x00000
osv
CVE-2023-54106UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-12-24
CVE-2023-54106 CVE-2023-54106: In the Linux kernel, the following vulnerability has been resolved: net/mlx5: fix potential memory leak in mlx5e_init_rep_rx The memory pointed to by
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: fix potential memory leak in mlx5e_init_rep_rx The memory pointed to by the priv->rx_res pointer is not freed in the error path of mlx5e_init_rep_rx, which can lead to a memory leak. Fix by freeing the memory in the error path, thereby makin
osv
CVE-2023-53996UNKNOWN≥ 5.16.0, < 6.1.53≥ 6.2.0, < 6.4.16+1 more2025-12-24
CVE-2023-53996 x86/sev: Make enc_dec_hypercall() accept a size instead of npages
x86/sev: Make enc_dec_hypercall() accept a size instead of npages
In the Linux kernel, the following vulnerability has been resolved:
x86/sev: Make enc_dec_hypercall() accept a size instead of npages
enc_dec_hypercall() accepted a page count instead of a size, which
forced its callers to round up. As a result, non-page aligned
vaddrs caused pages to be spuriously marked as decrypted via the
encryption status hype
osv
CVE-2022-50707UNKNOWN≥ 5.19.0, < 6.0.19≥ 6.1.0, < 6.1.52025-12-24
CVE-2022-50707 virtio-crypto: fix memory leak in virtio_crypto_alg_skcipher_close_session()
virtio-crypto: fix memory leak in virtio_crypto_alg_skcipher_close_session()
In the Linux kernel, the following vulnerability has been resolved:
virtio-crypto: fix memory leak in virtio_crypto_alg_skcipher_close_session()
'vc_ctrl_req' is alloced in virtio_crypto_alg_skcipher_close_session(),
and should be freed in the invalid ctrl_status->status error handling
case. Otherwise there is a memory leak.
osv
CVE-2022-50713UNKNOWN≥ 5.17.0, < 6.0.16≥ 6.1.0, < 6.1.22025-12-24
CVE-2022-50713 clk: visconti: Fix memory leak in visconti_register_pll()
clk: visconti: Fix memory leak in visconti_register_pll()
In the Linux kernel, the following vulnerability has been resolved:
clk: visconti: Fix memory leak in visconti_register_pll()
@pll->rate_table has allocated memory by kmemdup(), if clk_hw_register()
fails, it should be freed, otherwise it will cause memory leak issue,
this patch fixes it.
osv
CVE-2022-50740UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50740 CVE-2022-50740: In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs() S
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs() Syzkaller reports a long-known leak of urbs in ath9k_hif_usb_dealloc_tx_urbs(). The cause of the leak is that usb_get_urb() is called but usb_free_urb() (or usb_put_urb(
osv
CVE-2025-68742UNKNOWN≥ 0, < 6.1.162-1≥ 0, < 6.12.63-1+1 more2025-12-24
CVE-2025-68742 CVE-2025-68742: In the Linux kernel, the following vulnerability has been resolved: bpf: Fix invalid prog->stats access when update_effective_progs fails Syzkaller tr
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix invalid prog->stats access when update_effective_progs fails Syzkaller triggers an invalid memory access issue following fault injection in update_effective_progs. The issue can be described as follows: __cgroup_bpf_detach update_effective_p
osv
CVE-2023-54016UNKNOWN≥ 6.3.0, < 6.5.52025-12-24
CVE-2023-54016 wifi: ath12k: Fix memory leak in rx_desc and tx_desc
wifi: ath12k: Fix memory leak in rx_desc and tx_desc
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath12k: Fix memory leak in rx_desc and tx_desc
Currently when ath12k_dp_cc_desc_init() is called we allocate
memory to rx_descs and tx_descs. In ath12k_dp_cc_cleanup(), during
descriptor cleanup rx_descs and tx_descs memory is not freed.
This is cause of memory leak. These allocated memory should be
osv
CVE-2023-54114UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-24
CVE-2023-54114 CVE-2023-54114: In the Linux kernel, the following vulnerability has been resolved: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() As the cal
In the Linux kernel, the following vulnerability has been resolved: net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() As the call trace shows, skb_panic was caused by wrong skb->mac_header in nsh_gso_segment(): invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 3 PID: 2737 Comm: syz Not tainte
osv
CVE-2025-68744UNKNOWN≥ 6.4.0, < 6.6.120≥ 6.7.0, < 6.12.63+2 more2025-12-24
CVE-2025-68744 bpf: Free special fields when update [lru_,]percpu_hash maps
bpf: Free special fields when update [lru_,]percpu_hash maps
In the Linux kernel, the following vulnerability has been resolved:
bpf: Free special fields when update [lru_,]percpu_hash maps
As [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing
calls to 'bpf_obj_free_fields()' in 'pcpu_copy_value()' could cause the
memory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the
map gets freed.
Fix t
osv
CVE-2023-53990UNKNOWN≥ 0, < 5.15.111≥ 5.16.0, < 6.1.28+2 more2025-12-24
CVE-2023-53990 SMB3: Add missing locks to protect deferred close file list
SMB3: Add missing locks to protect deferred close file list
In the Linux kernel, the following vulnerability has been resolved:
SMB3: Add missing locks to protect deferred close file list
cifs_del_deferred_close function has a critical section which modifies
the deferred close file list. We must acquire deferred_lock before
calling cifs_del_deferred_close function.
osv
CVE-2023-54044UNKNOWN≥ 3.15.0, < 4.14.315≥ 4.15.0, < 4.19.283+6 more2025-12-24
CVE-2023-54044 spmi: Add a check for remove callback when removing a SPMI driver
spmi: Add a check for remove callback when removing a SPMI driver
In the Linux kernel, the following vulnerability has been resolved:
spmi: Add a check for remove callback when removing a SPMI driver
When removing a SPMI driver, there can be a crash due to NULL pointer
dereference if it does not have a remove callback defined. This is
one such call trace observed when removing the QCOM SPMI PMIC driver:
dump_bac
osv
CVE-2022-50737UNKNOWN≥ 0, < 6.1.4-12025-12-24
CVE-2022-50737 CVE-2022-50737: In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Validate index root when initialize NTFS security This enhances the sani
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Validate index root when initialize NTFS security This enhances the sanity check for $SDH and $SII while initializing NTFS security, guarantees these index root are legit. [ 162.459513] BUG: KASAN: use-after-free in hdr_find_e.isra.0+0x10c/
osv
CVE-2023-54026UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-12-24
CVE-2023-54026 CVE-2023-54026: In the Linux kernel, the following vulnerability has been resolved: opp: Fix use-after-free in lazy_opp_tables after probe deferral When dev_pm_opp_of
In the Linux kernel, the following vulnerability has been resolved: opp: Fix use-after-free in lazy_opp_tables after probe deferral When dev_pm_opp_of_find_icc_paths() in _allocate_opp_table() returns -EPROBE_DEFER, the opp_table is freed again, to wait until all the interconnect paths are available. However, if the
osv
CVE-2023-53867UNKNOWN≥ 2.6.34, < 6.1.28≥ 6.2.0, < 6.2.15+1 more2025-12-24
CVE-2023-53867 ceph: fix potential use-after-free bug when trimming caps
ceph: fix potential use-after-free bug when trimming caps
In the Linux kernel, the following vulnerability has been resolved:
ceph: fix potential use-after-free bug when trimming caps
When trimming the caps and just after the 'session->s_cap_lock' is
released in ceph_iterate_session_caps() the cap maybe removed by
another thread, and when using the stale cap memory in the callbacks
it will trigger use-after-free crash.
osv
CVE-2022-50763UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-12-24
CVE-2022-50763 CVE-2022-50763: In the Linux kernel, the following vulnerability has been resolved: crypto: marvell/octeontx - prevent integer overflows The "code_length" value comes
In the Linux kernel, the following vulnerability has been resolved: crypto: marvell/octeontx - prevent integer overflows The "code_length" value comes from the firmware file. If your firmware is untrusted realistically there is probably very little you can do to protect yourself. Still we try to limit the damage as m
osv
CVE-2023-54086UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-24
CVE-2023-54086 CVE-2023-54086: In the Linux kernel, the following vulnerability has been resolved: bpf: Add preempt_count_{sub,add} into btf id deny list The recursion check in __bp
In the Linux kernel, the following vulnerability has been resolved: bpf: Add preempt_count_{sub,add} into btf id deny list The recursion check in __bpf_prog_enter* and __bpf_prog_exit* leave preempt_count_{sub,add} unprotected. When attaching trampoline to them we get panic as follows, [ 867.843050] BUG: TASK stack g
osv