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 88 of 724
CVE-2025-40285UNKNOWN≥ 0, < 6.1.159≥ 6.2.0, < 6.6.117+2 more2025-12-06
CVE-2025-40285 smb/server: fix possible refcount leak in smb2_sess_setup() smb/server: fix possible refcount leak in smb2_sess_setup() In the Linux kernel, the following vulnerability has been resolved: smb/server: fix possible refcount leak in smb2_sess_setup() Reference count of ksmbd_session will leak when session need reconnect. Fix this by adding the missing ksmbd_user_session_put().
osv
CVE-2025-40271UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-06
CVE-2025-40271 CVE-2025-40271: In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix uaf in proc_readdir_de() Pde is erased from subdir rbtree through rb_ In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix uaf in proc_readdir_de() Pde is erased from subdir rbtree through rb_erase(), but not set the node to EMPTY, which may result in uaf access. We should use RB_CLEAR_NODE() set the erased node to EMPTY, then pde_subdir_next() will return N
osv
CVE-2025-40274UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-06
CVE-2025-40274 CVE-2025-40274: In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying When unbi In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying When unbinding a memslot from a guest_memfd instance, remove the bindings even if the guest_memfd file is dying, i.e. even if its file refcount has gone to zero. If the memslot
osv
CVE-2025-40281UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-06
CVE-2025-40281 CVE-2025-40281: In the Linux kernel, the following vulnerability has been resolved: sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto syzbot rep In the Linux kernel, the following vulnerability has been resolved: sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto syzbot reported a possible shift-out-of-bounds [1] Blamed commit added rto_alpha_max and rto_beta_max set to 1000. It is unclear if some sctp users are setting very large rto_alp
osv
CVE-2025-40270UNKNOWN≥ 0, < 6.17.9-12025-12-06
CVE-2025-40270 CVE-2025-40270: In the Linux kernel, the following vulnerability has been resolved: mm, swap: fix potential UAF issue for VMA readahead Since commit 78524b05f1a3 ("mm In the Linux kernel, the following vulnerability has been resolved: mm, swap: fix potential UAF issue for VMA readahead Since commit 78524b05f1a3 ("mm, swap: avoid redundant swap device pinning"), the common helper for allocating and preparing a folio in the swap cache layer no longer tries to get a swap device refer
osv
CVE-2025-40286UNKNOWN≥ 5.15.0, < 6.1.159≥ 6.2.0, < 6.6.117+2 more2025-12-06
CVE-2025-40286 smb/server: fix possible memory leak in smb2_read() smb/server: fix possible memory leak in smb2_read() In the Linux kernel, the following vulnerability has been resolved: smb/server: fix possible memory leak in smb2_read() Memory leak occurs when ksmbd_vfs_read() fails. Fix this by adding the missing kvfree().
osv
CVE-2025-40269UNKNOWN≥ 0, < 4.4.230≥ 4.5.0, < 4.9.230+10 more2025-12-06
CVE-2025-40269 ALSA: usb-audio: Fix potential overflow of PCM transfer buffer ALSA: usb-audio: Fix potential overflow of PCM transfer buffer In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix potential overflow of PCM transfer buffer The PCM stream data in USB-audio driver is transferred over USB URB packet buffers, and each packet size is determined dynamically. The packet sizes are limited by some factors such as wMaxPacketSize USB descriptor. OTOH, in
osv
CVE-2025-40273UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-06
CVE-2025-40273 CVE-2025-40273: In the Linux kernel, the following vulnerability has been resolved: NFSD: free copynotify stateid in nfs4_free_ol_stateid() Typically copynotify state In the Linux kernel, the following vulnerability has been resolved: NFSD: free copynotify stateid in nfs4_free_ol_stateid() Typically copynotify stateid is freed either when parent's stateid is being close/freed or in nfsd4_laundromat if the stateid hasn't been used in a lease period. However, in case when the server
osv
CVE-2025-40282UNKNOWN≥ 3.14.0, < 5.4.302≥ 5.5.0, < 5.10.247+5 more2025-12-06
CVE-2025-40282 Bluetooth: 6lowpan: reset link-local header on ipv6 recv path Bluetooth: 6lowpan: reset link-local header on ipv6 recv path In the Linux kernel, the following vulnerability has been resolved: Bluetooth: 6lowpan: reset link-local header on ipv6 recv path Bluetooth 6lowpan.c netdev has header_ops, so it must set link-local header for RX skb, otherwise things crash, eg. with AF_PACKET SOCK_RAW Add missing skb_reset_mac_header() for uncompressed ipv6 RX path. For the compressed o
osv
CVE-2025-40277UNKNOWN≥ 4.3.0, < 5.4.302≥ 5.5.0, < 5.10.247+5 more2025-12-06
CVE-2025-40277 drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE This data originates from userspace and is used in buffer offset calculations which could potentially overflow causing an out-of-bounds access.
osv
CVE-2025-40280UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-06
CVE-2025-40280 CVE-2025-40280: In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_mon_reinit_self() In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_mon_reinit_self(). syzbot reported use-after-free of tipc_net(net)->monitors[] in tipc_mon_reinit_self(). [0] The array is protected by RTNL, but tipc_mon_reinit_self() iterates over it without RTNL. tipc_mon_reinit_self() is called from tipc_net_fi
osv
CVE-2025-40272UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-06
CVE-2025-40272 CVE-2025-40272: In the Linux kernel, the following vulnerability has been resolved: mm/secretmem: fix use-after-free race in fault handler When a page fault occurs in In the Linux kernel, the following vulnerability has been resolved: mm/secretmem: fix use-after-free race in fault handler When a page fault occurs in a secret memory file created with `memfd_secret(2)`, the kernel will allocate a new folio for it, mark the underlying page as not-present in the direct map, and add it
osv
CVE-2025-40283UNKNOWN≥ 4.11.0, < 5.4.302≥ 5.5.0, < 5.10.247+5 more2025-12-06
CVE-2025-40283 Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF There is a KASAN: slab-use-after-free read in btusb_disconnect(). Calling "usb_driver_release_interface(&btusb_driver, data->intf)" will free the btusb data associated with the interface. The same data is then use
osv
CVE-2025-40276UNKNOWN≥ 6.10.0, < 6.12.64≥ 6.13.0, < 6.17.92025-12-06
CVE-2025-40276 drm/panthor: Flush shmem writes before mapping buffers CPU-uncached drm/panthor: Flush shmem writes before mapping buffers CPU-uncached In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Flush shmem writes before mapping buffers CPU-uncached The shmem layer zeroes out the new pages using cached mappings, and if we don't CPU-flush we might leave dirty cachelines behind, leading to potential data leaks and/or asynchronous buffer corruption when dirty
osv
CVE-2025-40279UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-06
CVE-2025-40279 CVE-2025-40279: In the Linux kernel, the following vulnerability has been resolved: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak In tcf_connm In the Linux kernel, the following vulnerability has been resolved: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak In tcf_connmark_dump(), the variable 'opt' was partially initialized using a designatied initializer. While the padding bytes are reamined uninitialized. nla_put() copies the entir
osv
CVE-2025-40287UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-06
CVE-2025-40287 CVE-2025-40287: In the Linux kernel, the following vulnerability has been resolved: exfat: fix improper check of dentry In the Linux kernel, the following vulnerability has been resolved: exfat: fix improper check of dentry.stream.valid_size We found an infinite loop bug in the exFAT file system that can lead to a Denial-of-Service (DoS) condition. When a dentry in an exFAT filesystem is malformed, the following system calls — SYS_openat, SYS_ftruncate, and SYS_pwrite64 — can caus
osv
CVE-2025-40268UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-06
CVE-2025-40268 CVE-2025-40268: In the Linux kernel, the following vulnerability has been resolved: cifs: client: fix memory leak in smb3_fs_context_parse_param The user calls fsconf In the Linux kernel, the following vulnerability has been resolved: cifs: client: fix memory leak in smb3_fs_context_parse_param The user calls fsconfig twice, but when the program exits, free() only frees ctx->source for the second fsconfig, not the first. Regarding fc->source, there is no code in the fs context rel
osv
CVE-2025-40251MEDIUMCVSS 5.5≥ 5.14, < 6.1.164≥ 6.2, < 6.6.118+3 more2025-12-04
CVE-2025-40251 [MEDIUM] CWE-476 CVE-2025-40251: In the Linux kernel, the following vulnerability has been resolved: devlink: rate: Unset parent poi In the Linux kernel, the following vulnerability has been resolved: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy The function devl_rate_nodes_destroy is documented to "Unset parent for all rate objects". However, it was only calling the driver-specific `rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing the pare
nvdosv
CVE-2025-40256UNKNOWN≥ 6.16.0, < 6.17.102025-12-04
CVE-2025-40256 xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added In the Linux kernel, the following vulnerability has been resolved: xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added In commit b441cf3f8c4b ("xfrm: delete x->tunnel as we delete x"), I missed the case where state creation fails between full initialization (->in
osv
CVE-2025-40219UNKNOWN≥ 0, < 6.19.6-12025-12-04
CVE-2025-40219 CVE-2025-40219: In the Linux kernel, the following vulnerability has been resolved: PCI/IOV: Fix race between SR-IOV enable/disable and hotplug Commit 05703271c3cd (" In the Linux kernel, the following vulnerability has been resolved: PCI/IOV: Fix race between SR-IOV enable/disable and hotplug Commit 05703271c3cd ("PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV") tried to fix a race between the VF removal inside sriov_del_vfs() and concurrent hot unplug by t
osv