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 80 of 724
CVE-2022-50649UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-12-09
CVE-2022-50649 CVE-2022-50649: In the Linux kernel, the following vulnerability has been resolved: power: supply: adp5061: fix out-of-bounds read in adp5061_get_chg_type() ADP5061_C In the Linux kernel, the following vulnerability has been resolved: power: supply: adp5061: fix out-of-bounds read in adp5061_get_chg_type() ADP5061_CHG_STATUS_1_CHG_STATUS is masked with 0x07, which means a length of 8, but adp5061_chg_type array size is 4, may end up reading 4 elements beyond the end of the adp5061
osv
CVE-2025-40330UNKNOWN≥ 0, < 6.17.8-12025-12-09
CVE-2025-40330 CVE-2025-40330: In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Shutdown FW DMA in bnxt_shutdown() The netif_close() call in bnxt_shutdow In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Shutdown FW DMA in bnxt_shutdown() The netif_close() call in bnxt_shutdown() only stops packet DMA. There may be FW DMA for trace logging (recently added) that will continue. If we kexec to a new kernel, the DMA will corrupt memory in the ne
osv
CVE-2022-50655UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-09
CVE-2022-50655 CVE-2022-50655: In the Linux kernel, the following vulnerability has been resolved: ppp: associate skb with a device at tx Syzkaller triggered flow dissector warning In the Linux kernel, the following vulnerability has been resolved: ppp: associate skb with a device at tx Syzkaller triggered flow dissector warning with the following: r0 = openat$ppp(0xffffffffffffff9c, &(0x7f0000000000), 0xc0802, 0x0) ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &(0x7f00000000c0)) ioctl$PPPIOCSACTIVE(r0, 0
osv
CVE-2022-50659UNKNOWN≥ 2.6.18, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-12-09
CVE-2022-50659 hwrng: geode - Fix PCI device refcount leak hwrng: geode - Fix PCI device refcount leak In the Linux kernel, the following vulnerability has been resolved: hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop w
osv
CVE-2023-53777UNKNOWN≥ 6.0.0, < 6.1.39≥ 6.2.0, < 6.3.13+1 more2025-12-09
CVE-2023-53777 erofs: kill hooked chains to avoid loops on deduplicated compressed images erofs: kill hooked chains to avoid loops on deduplicated compressed images In the Linux kernel, the following vulnerability has been resolved: erofs: kill hooked chains to avoid loops on deduplicated compressed images After heavily stressing EROFS with several images which include a hand-crafted image of repeated patterns for more than 46 days, I found two chains could be linked with each other almost si
osv
CVE-2022-50642UNKNOWN≥ 0, < 6.1.4-12025-12-09
CVE-2022-50642 CVE-2022-50642: In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_typec: zero out stale pointers `cros_typec_get_switch_han In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_typec: zero out stale pointers `cros_typec_get_switch_handles` allocates four pointers when obtaining type-c switch handles. These pointers are all freed if failing to obtain any of them; therefore, pointers in `port` become
osv
CVE-2023-53827UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.25-12025-12-09
CVE-2023-53827 CVE-2023-53827: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} Similar to comm In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} Similar to commit d0be8347c623 ("Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put"), just use l2cap_chan_hold_unless_zero to prevent referencing a channel that is about t
osv
CVE-2023-53839UNKNOWN≥ 2.6.14, < 4.14.323≥ 4.15.0, < 4.19.292+5 more2025-12-09
CVE-2023-53839 dccp: fix data-race around dp->dccps_mss_cache dccp: fix data-race around dp->dccps_mss_cache In the Linux kernel, the following vulnerability has been resolved: dccp: fix data-race around dp->dccps_mss_cache dccp_sendmsg() reads dp->dccps_mss_cache before locking the socket. Same thing in do_dccp_getsockopt(). Add READ_ONCE()/WRITE_ONCE() annotations, and change dccp_sendmsg() to check again dccps_mss_cache after socket is locked.
osv
CVE-2023-53858UNKNOWN≥ 3.3.0, < 4.14.322≥ 4.15.0, < 4.19.291+5 more2025-12-09
CVE-2023-53858 tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() in case of error If clk_get_rate() fails, the clk that has just been allocated needs to be freed.
osv
CVE-2023-53790UNKNOWN≥ 0, < 6.1.20-12025-12-09
CVE-2023-53790 CVE-2023-53790: In the Linux kernel, the following vulnerability has been resolved: bpf: Zeroing allocated object from slab in bpf memory allocator Currently the free In the Linux kernel, the following vulnerability has been resolved: bpf: Zeroing allocated object from slab in bpf memory allocator Currently the freed element in bpf memory allocator may be immediately reused, for htab map the reuse will reinitialize special fields in map value (e.g., bpf_spin_lock), but lookup proc
osv
CVE-2022-50648UNKNOWN≥ 0, < 6.0.3-12025-12-09
CVE-2022-50648 CVE-2022-50648: In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller Naveen r In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller Naveen reported recursive locking of direct_mutex with sample ftrace-direct-modify.ko: [ 74.762406] WARNING: possible recursive locking detected [ 74.762887] 6.0.0-rc6+ #33 Not
osv
CVE-2022-50640UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.7-12025-12-09
CVE-2022-50640 CVE-2022-50640: In the Linux kernel, the following vulnerability has been resolved: mmc: core: Fix kernel panic when remove non-standard SDIO card SDIO tuple is only In the Linux kernel, the following vulnerability has been resolved: mmc: core: Fix kernel panic when remove non-standard SDIO card SDIO tuple is only allocated for standard SDIO card, especially it causes memory corruption issues when the non-standard SDIO card has removed, which is because the card device's reference
osv
CVE-2022-50673UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-09
CVE-2022-50673 CVE-2022-50673: In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_orphan_cleanup I caught a issue as follows: ===== In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_orphan_cleanup I caught a issue as follows: ================================================================== BUG: KASAN: use-after-free in __list_add_valid+0x28/0x1a0 Read of size 8 at addr ffff88814b13f378 by task
osv
CVE-2022-50662UNKNOWN≥ 5.8.0, < 5.10.163≥ 5.11.0, < 5.15.86+2 more2025-12-09
CVE-2022-50662 RDMA/hns: fix memory leak in hns_roce_alloc_mr() RDMA/hns: fix memory leak in hns_roce_alloc_mr() In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: fix memory leak in hns_roce_alloc_mr() When hns_roce_mr_enable() failed in hns_roce_alloc_mr(), mr_key is not released. Compiled test only.
osv
CVE-2023-53865UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-09
CVE-2023-53865 CVE-2023-53865: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix warning when putting transaction with qgroups enabled after abort If we In the Linux kernel, the following vulnerability has been resolved: btrfs: fix warning when putting transaction with qgroups enabled after abort If we have a transaction abort with qgroups enabled we get a warning triggered when doing the final put on the transaction, like this: [552.6789] ------------[ cut here ]---
osv
CVE-2022-50665UNKNOWN≥ 0, < 6.0.3-12025-12-09
CVE-2022-50665 CVE-2022-50665: In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected It has In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected It has a fail log which is ath11k_dbg in ath11k_dp_rx_process_mon_status(), as below, it will not print when debug_mask is not set ATH11K_DBG_DATA. ath11k_dbg(ab, ATH11K_DBG_DA
osv
CVE-2022-50633UNKNOWN≥ 5.10.0, < 5.10.163≥ 5.11.0, < 5.15.87+2 more2025-12-09
CVE-2022-50633 usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init of_icc_get() alloc resources for path handle, we should release it when not need anymore. Like the release in dwc3_qcom_interconnect_exit() function. Add icc_put() in error handling to fix this.
osv
CVE-2023-53821UNKNOWN≥ 3.19.0, < 4.14.324≥ 4.15.0, < 4.19.293+5 more2025-12-09
CVE-2023-53821 ip6_vti: fix slab-use-after-free in decode_session6 ip6_vti: fix slab-use-after-free in decode_session6 In the Linux kernel, the following vulnerability has been resolved: ip6_vti: fix slab-use-after-free in decode_session6 When ipv6_vti device is set to the qdisc of the sfb type, the cb field of the sent skb may be modified during enqueuing. Then, slab-use-after-free may occur when ipv6_vti device sends IPv6 packets. The stack information is as follows: BUG: KASAN: slab-use-a
osv
CVE-2023-53796UNKNOWN≥ 4.3.0, < 4.14.308≥ 4.15.0, < 4.19.276+5 more2025-12-09
CVE-2023-53796 f2fs: fix information leak in f2fs_move_inline_dirents() f2fs: fix information leak in f2fs_move_inline_dirents() In the Linux kernel, the following vulnerability has been resolved: f2fs: fix information leak in f2fs_move_inline_dirents() When converting an inline directory to a regular one, f2fs is leaking uninitialized memory to disk because it doesn't initialize the entire directory block. Fix this by zero-initializing the block. This bug was introduced by commit 4ec17d688d
osv
CVE-2023-53842UNKNOWN≥ 5.14.0, < 5.15.123≥ 5.16.0, < 6.1.42+1 more2025-12-09
CVE-2023-53842 ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove The MBHC resources must be released on component probe failure and removal so can not be tied to the lifetime of the component device. This is specifically needed to allow probe deferrals of the sound card which oth
osv