CyberSecBulletin

Linux vulnerabilities

We track 3,714 vulnerabilities in Linux products across 5 products. 3,710 are rated high or critical, and 32 have been exploited in real attacks. The most recent was published on October 15, 2026.

3,714vulnerabilities
245critical
3,465high
32exploited
7.8average CVSS score

Latest Linux vulnerabilities

  • 7.8 High severity

    Linux: NULL Pointer Dereference

    CVE-2024-36928Linux

    In the Linux kernel, the following vulnerability has been resolved: s390/qeth: Fix kernel panic after setting hsuid Symptom: When the hsuid attribute is set for the first time on an IQD Layer3 device while the corresponding network interface is already UP, the

  • 7.8 High severity

    Linux: Improper Validation of Array Index

    CVE-2024-36921Linux

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: guard against invalid STA ID on removal Guard against invalid station IDs in iwl_mvm_mld_rm_sta_id as that would result in out-of-bounds array accesses. This prevents issue

  • 7.1 High severity

    Linux: Out-of-bounds Read

    CVE-2024-36916Linux

    In the Linux kernel, the following vulnerability has been resolved: blk-iocost: avoid out of bounds shift UBSAN catches undefined behavior in blk-iocost, where sometimes iocg->delay is shifted right by a number that is too large, resulting in undefined behavio

  • 7.1 High severity

    Linux: Out-of-bounds Read

    CVE-2024-36915Linux

    In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies syzbot reported unsafe calls to copy_from_sockptr() [1] Use copy_safe_from_sockptr() instead. [1] BUG: KASAN: slab-out-of-bounds in copy_from

  • 9.3 Critical severity

    Linux: Exposure of Sensitive System Information Due to Uncleared Debug Information

    CVE-2024-36913Linux

    In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an

  • 9.6 Critical severity

    Linux: Exposure of Sensitive System Information Due to Uncleared Debug Information

    CVE-2024-36912Linux

    In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error

  • 8.4 High severity

    Linux: Exposure of Sensitive Information to an Unauthorized Actor

    CVE-2024-36910Linux

    In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Don't free decrypted memory In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned a

  • 7.8 High severity

    Linux: Out-of-bounds Write

    CVE-2024-36906Linux

    In the Linux kernel, the following vulnerability has been resolved: ARM: 9381/1: kasan: clear stale stack poison We found below OOB crash: [ 33.452494] ================================================================== [ 33.453513] BUG: KASAN: stack-out-of-bou

  • 7.8 High severity

    Linux: Use After Free

    CVE-2024-36904Linux

    In the Linux kernel, the following vulnerability has been resolved: tcp: Use refcount_inc_not_zero() in tcp_twsk_unique(). Anderson Nascimento reported a use-after-free splat in tcp_twsk_unique() with nice analysis. Since commit ec94c2696f0b ("tcp/dccp: avoid

  • 7.0 High severity

    Linux: Concurrent Execution using Shared Resource with Improper Synchronization

    CVE-2024-36899Linux

    In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Fix use after free in lineinfo_changed_notify The use-after-free issue occurs as follows: when the GPIO chip device file is being closed by invoking gpio_chrdev_release(), watch

  • 7.8 High severity

    Linux: Use of Uninitialized Resource

    CVE-2024-36898Linux

    In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: fix uninitialised kfifo If a line is requested with debounce, and that results in debouncing in software, and the line is subsequently reconfigured to enable edge detection then

  • 9.1 Critical severity

    Linux: NULL Pointer Dereference

    CVE-2024-36896Linux

    In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix access violation during port device removal Testing with KASAN and syzkaller revealed a bug in port.c:disable_store(): usb_hub_to_struct_hub() can return NULL if the hub that th

  • 7.8 High severity

    Linux: Out-of-bounds Write

    CVE-2024-36895Linux

    In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: use correct buffer size when parsing configfs lists This commit fixes uvc gadget support on 32-bit platforms. Commit 0df28607c5cb ("usb: gadget: uvc: Generalise helper functi

  • 7.8 High severity

    Linux: Concurrent Execution using Shared Resource with Improper Synchronization

    CVE-2024-36894Linux

    In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete FFS based applications can utilize the aio_cancel() callback to dequeue pending USB requests submitted to the UDC. The

  • 7.8 High severity

    Linux: Use After Free

    CVE-2024-36886LinuxEPSS 1.31%

    In the Linux kernel, the following vulnerability has been resolved: tipc: fix UAF in error path Sam Page (sam4k) working with Trend Micro Zero Day Initiative reported a UAF in the tipc_buf_append() error path: BUG: KASAN: slab-use-after-free in kfree_skb_list_

  • 7.1 High severity

    Linux: Out-of-bounds Read

    CVE-2024-36883Linux

    In the Linux kernel, the following vulnerability has been resolved: net: fix out-of-bounds access in ops_init net_alloc_generic is called by net_alloc, which is called without any locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It is r

  • 7.1 High severity

    Linux: Exposure of Resource to Wrong Sphere

    CVE-2024-36033Linux

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix info leak when fetching board id Add the missing sanity check when fetching the board id to avoid leaking slab data when later requesting the firmware.

  • 7.1 High severity

    Linux: Exposure of Resource to Wrong Sphere

    CVE-2024-36032Linux

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix info leak when fetching fw build id Add the missing sanity checks and move the 255-byte build-id buffer off the stack to avoid leaking stack data through debugfs in case th

  • 9.8 Critical severity

    Linux: Use of a Key Past its Expiration Date

    CVE-2024-36031Linux

    In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for

  • 7.1 High severity

    Linux: Double Free

    CVE-2024-36030Linux

    In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: fix the double free in rvu_npc_freemem() Clang static checker(scan-build) warning: drivers/net/ethernet/marvell/octeontx2/af/rvu_npc.c:line 2184, column 2 Attempt to free release

  • 7.1 High severity

    Linux: Out-of-bounds Read

    CVE-2024-36019Linux

    In the Linux kernel, the following vulnerability has been resolved: regmap: maple: Fix cache corruption in regcache_maple_drop() When keeping the upper end of a cache block entry, the entry[] array must be indexed by the offset from the base register of the bl

  • 7.8 High severity

    Linux: Out-of-bounds Read

    CVE-2024-36016Linux

    In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() Assuming the following: - side A configures the n_gsm in basic option mode - side B sends the header of a basic option mode frame with

  • 7.8 High severity

    Linux: Improper Validation of Array Index

    CVE-2024-36015Linux

    In the Linux kernel, the following vulnerability has been resolved: ppdev: Add an error check in register_device In register_device, the return value of ida_simple_get is unchecked, in witch ida_simple_get will use an invalid index value. To address this issue

  • 8.8 High severity

    Linux: Use After Free

    CVE-2024-36013Linux

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect() Extend a critical section to prevent chan from early freeing. Also make the l2cap_connect() return type void. Nothing is using the

  • 7.8 High severity

    Linux: Use After Free

    CVE-2024-36012Linux

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: msft: fix slab-use-after-free in msft_do_close() Tying the msft->data lifetime to hdev by freeing it in hci_release_dev() to fix the following case: [use] msft_do_close() msft = hde

  • 7.8 High severity

    Linux: Concurrent Execution using Shared Resource with Improper Synchronization

    CVE-2023-52872Linux

    In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix race condition in status line change on dead connections gsm_cleanup_mux() cleans up the gsm by closing all DLCIs, stopping all timers, removing the virtual tty devices and cle

  • 7.8 High severity

    Linux: Out-of-bounds Write

    CVE-2023-52868Linux

    In the Linux kernel, the following vulnerability has been resolved: thermal: core: prevent potential string overflow The dev->id value comes from ida_alloc() so it's a number between zero and INT_MAX. If it's too high then these sprintf()s will overflow.

  • 7.8 High severity

    Linux: Out-of-bounds Write

    CVE-2023-52867Linux

    In the Linux kernel, the following vulnerability has been resolved: drm/radeon: possible buffer overflow Buffer 'afmt_status' of size 6 could overflow, since index 'afmt_idx' is checked after access.

  • 7.1 High severity

    Linux: Out-of-bounds Read

    CVE-2023-52866Linux

    In the Linux kernel, the following vulnerability has been resolved: HID: uclogic: Fix user-memory-access bug in uclogic_params_ugee_v2_init_event_hooks() When CONFIG_HID_UCLOGIC=y and CONFIG_KUNIT_ALL_TESTS=y, launch kernel and then the below user-memory-acces

  • 7.8 High severity

    Linux: Out-of-bounds Write

    CVE-2023-52864Linux

    In the Linux kernel, the following vulnerability has been resolved: platform/x86: wmi: Fix opening of char device Since commit fa1f68db6ca7 ("drivers: misc: pass miscdevice pointer via file private data"), the miscdevice stores a pointer to itself inside filp-

  • 7.8 High severity

    Linux: Use After Free

    CVE-2023-52859Linux

    In the Linux kernel, the following vulnerability has been resolved: perf: hisi: Fix use-after-free when register pmu fails When we fail to register the uncore pmu, the pmu context may not been allocated. The error handing will call cpuhp_state_remove_instance(

  • 7.8 High severity

    Linux: Use After Free

    CVE-2023-52854Linux

    In the Linux kernel, the following vulnerability has been resolved: padata: Fix refcnt handling in padata_free_shell() In a high-load arm64 environment, the pcrypt_aead01 test in LTP can lead to system UAF (Use-After-Free) issues. Due to the lengthy analysis o

  • 7.8 High severity

    Linux: Use After Free

    CVE-2023-52852Linux

    In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to avoid use-after-free on dic Call trace: __memcpy+0x128/0x250 f2fs_read_multi_pages+0x940/0xf7c f2fs_mpage_readpages+0x5a8/0x624 f2fs_readahead+0x5c/0x110 page_cache_ra_u

  • 7.8 High severity

    Linux: Double Free

    CVE-2023-52851Linux

    In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix init stage error handling to avoid double free of same QP and UAF In the unlikely event that workqueue allocation fails and returns NULL in mlx5_mkey_cache_init(), delete the call

  • 7.0 High severity

    Linux: Concurrent Execution using Shared Resource with Improper Synchronization

    CVE-2023-52847Linux

    In the Linux kernel, the following vulnerability has been resolved: media: bttv: fix use after free error due to btv->timeout timer There may be some a race condition between timer function bttv_irq_timeout and bttv_remove. The timer is setup in probe and ther

  • 7.8 High severity

    Linux: Use After Free

    CVE-2023-52846Linux

    In the Linux kernel, the following vulnerability has been resolved: hsr: Prevent use after free in prp_create_tagged_frame() The prp_fill_rct() function can fail. In that situation, it frees the skb and returns NULL. Meanwhile on the success path, it returns t

  • 7.1 High severity

    Linux: Use of Uninitialized Resource

    CVE-2023-52842Linux

    In the Linux kernel, the following vulnerability has been resolved: virtio/vsock: Fix uninit-value in virtio_transport_recv_pkt() KMSAN reported the following uninit-value access issue: ===================================================== BUG: KMSAN: uninit-v

  • 7.8 High severity

    Linux: Use After Free

    CVE-2023-52840Linux

    In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - fix use after free in rmi_unregister_function() The put_device() calls rmi_release_function() which frees "fn" so the dereference on the next line "fn->num_of_irqs" is

  • 7.8 High severity

    Linux: Use After Free

    CVE-2023-52837Linux

    In the Linux kernel, the following vulnerability has been resolved: nbd: fix uaf in nbd_open Commit 4af5f2e03013 ("nbd: use blk_mq_alloc_disk and blk_cleanup_disk") cleans up disk by blk_cleanup_disk() and it won't set disk->private_data as NULL as before. UAF

  • 7.8 High severity

    Linux: Out-of-bounds Write

    CVE-2023-52836Linux

    In the Linux kernel, the following vulnerability has been resolved: locking/ww_mutex/test: Fix potential workqueue corruption In some cases running with the test-ww_mutex code, I was seeing odd behavior where sometimes it seemed flush_workqueue was returning b