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 27 of 724
CVE-2026-23027UNKNOWN≥ 6.13.0, < 6.18.72026-01-31
CVE-2026-23027 LoongArch: KVM: Fix kvm_device leak in kvm_pch_pic_destroy()
LoongArch: KVM: Fix kvm_device leak in kvm_pch_pic_destroy()
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: KVM: Fix kvm_device leak in kvm_pch_pic_destroy()
In kvm_ioctl_create_device(), kvm_device has allocated memory,
kvm_device->destroy() seems to be supposed to free its kvm_device
struct, but kvm_pch_pic_destroy() is not currently doing this, that
would lead to a memory leak.
So,
osv
CVE-2026-23035UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.8-12026-01-31
CVE-2026-23035 CVE-2026-23035: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv mlx5e_priv is an un
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv mlx5e_priv is an unstable structure that can be memset(0) if profile attaching fails. Pass netdev to mlx5e_destroy_netdev() to guarantee it will work on a valid netdev. On mlx5e_remove: C
osv
CVE-2026-23033UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2026-01-31
CVE-2026-23033 CVE-2026-23033: In the Linux kernel, the following vulnerability has been resolved: dmaengine: omap-dma: fix dma_pool resource leak in error paths The dma_pool create
In the Linux kernel, the following vulnerability has been resolved: dmaengine: omap-dma: fix dma_pool resource leak in error paths The dma_pool created by dma_pool_create() is not destroyed when dma_async_device_register() or of_dma_controller_register() fails, causing a resource leak in the probe error paths. Add dm
osv
CVE-2026-23037UNKNOWN≥ 5.13.0, < 5.15.199≥ 5.16.0, < 6.1.162+3 more2026-01-31
CVE-2026-23037 can: etas_es58x: allow partial RX URB allocation to succeed
can: etas_es58x: allow partial RX URB allocation to succeed
In the Linux kernel, the following vulnerability has been resolved:
can: etas_es58x: allow partial RX URB allocation to succeed
When es58x_alloc_rx_urbs() fails to allocate the requested number of
URBs but succeeds in allocating some, it returns an error code.
This causes es58x_open() to return early, skipping the cleanup label
'free_urbs', which leads to the
osv
CVE-2026-23038UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2026-01-31
CVE-2026-23038 CVE-2026-23038: In the Linux kernel, the following vulnerability has been resolved: pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() In nfs4_ff_alloc_
In the Linux kernel, the following vulnerability has been resolved: pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() In nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails, the function jumps to the out_scratch label without freeing the already allocated dsaddrs list, leading to a m
osv
CVE-2026-23029UNKNOWN≥ 6.13.0, < 6.18.72026-01-31
CVE-2026-23029 LoongArch: KVM: Fix kvm_device leak in kvm_eiointc_destroy()
LoongArch: KVM: Fix kvm_device leak in kvm_eiointc_destroy()
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: KVM: Fix kvm_device leak in kvm_eiointc_destroy()
In kvm_ioctl_create_device(), kvm_device has allocated memory,
kvm_device->destroy() seems to be supposed to free its kvm_device
struct, but kvm_eiointc_destroy() is not currently doing this, that
would lead to a memory leak.
So,
osv
CVE-2026-23039UNKNOWN≥ 0, < 6.18.8-12026-01-31
CVE-2026-23039 CVE-2026-23039: In the Linux kernel, the following vulnerability has been resolved: drm/gud: fix NULL fb and crtc dereferences on USB disconnect On disconnect drm_ato
In the Linux kernel, the following vulnerability has been resolved: drm/gud: fix NULL fb and crtc dereferences on USB disconnect On disconnect drm_atomic_helper_disable_all() is called which sets both the fb and crtc for a plane to NULL before invoking a commit. This causes a kernel oops on every display disconnect.
osv
CVE-2026-23036UNKNOWN≥ 0, < 6.18.8-12026-01-31
CVE-2026-23036 CVE-2026-23036: In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before iget_failed() in btrfs_read_locked_inode() In btrfs_rea
In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before iget_failed() in btrfs_read_locked_inode() In btrfs_read_locked_inode() if we fail to lookup the inode, we jump to the 'out' label with a path that has a read locked leaf and then we call iget_failed(). This can result in a
osv
CVE-2026-23032UNKNOWN≥ 6.4.0, < 6.6.122≥ 6.7.0, < 6.12.67+1 more2026-01-31
CVE-2026-23032 null_blk: fix kmemleak by releasing references to fault configfs items
null_blk: fix kmemleak by releasing references to fault configfs items
In the Linux kernel, the following vulnerability has been resolved:
null_blk: fix kmemleak by releasing references to fault configfs items
When CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk
driver sets up fault injection support by creating the timeout_inject,
requeue_inject, and init_hctx_fault_inject configfs items as
osv
CVE-2026-23030UNKNOWN≥ 0, < 6.1.162-1≥ 0, < 6.12.69-1+1 more2026-01-31
CVE-2026-23030 CVE-2026-23030: In the Linux kernel, the following vulnerability has been resolved: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() The fo
In the Linux kernel, the following vulnerability has been resolved: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() The for_each_available_child_of_node() calls of_node_put() to release child_np in each success loop. After breaking from the loop with the child_np has been released, the cod
osv
CVE-2026-23014MEDIUMCVSS 5.5≥ 6.17.8, < 6.18≥ 6.18.1, < 6.18.6+2 more2026-01-28
CVE-2026-23014 [MEDIUM] CVE-2026-23014: In the Linux kernel, the following vulnerability has been resolved:
perf: Ensure swevent hrtimer is
In the Linux kernel, the following vulnerability has been resolved:
perf: Ensure swevent hrtimer is properly destroyed
With the change to hrtimer_try_to_cancel() in
perf_swevent_cancel_hrtimer() it appears possible for the hrtimer to
still be active by the time the event gets freed.
Make sure the event does a full hrtimer_cancel() on the free path by
ins
nvdosv
CVE-2026-23010HIGHCVSS 7.8≥ 6.1.120, < 6.1.162≥ 6.6.64, < 6.6.122+5 more2026-01-25
CVE-2026-23010 [HIGH] CWE-416 CVE-2026-23010: In the Linux kernel, the following vulnerability has been resolved:
ipv6: Fix use-after-free in ine
In the Linux kernel, the following vulnerability has been resolved:
ipv6: Fix use-after-free in inet6_addr_del().
syzbot reported use-after-free of inet6_ifaddr in
inet6_addr_del(). [0]
The cited commit accidentally moved ipv6_del_addr() for
mngtmpaddr before reading its ifp->flags for temporary
addresses in inet6_addr_del().
Let's move ipv6_del_a
nvdosv
CVE-2026-23013HIGHCVSS 7.8≥ 6.9.1, < 6.12.67≥ 6.13, < 6.18.7+2 more2026-01-25
CVE-2026-23013 [HIGH] CWE-416 CVE-2026-23013: In the Linux kernel, the following vulnerability has been resolved:
net: octeon_ep_vf: fix free_irq
In the Linux kernel, the following vulnerability has been resolved:
net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback
octep_vf_request_irqs() requests MSI-X queue IRQs with dev_id set to
ioq_vector. If request_irq() fails part-way, the rollback loop calls
free_irq() with dev_id set to 'oct', which does not match the original
dev_id and
nvdosv
CVE-2026-23001HIGHCVSS 7.8≥ 3.18.1, < 5.10.249≥ 5.11, < 5.15.199+6 more2026-01-25
CVE-2026-23001 [HIGH] CWE-416 CVE-2026-23001: In the Linux kernel, the following vulnerability has been resolved:
macvlan: fix possible UAF in ma
In the Linux kernel, the following vulnerability has been resolved:
macvlan: fix possible UAF in macvlan_forward_source()
Add RCU protection on (struct macvlan_source_entry)->vlan.
Whenever macvlan_hash_del_source() is called, we must clear
entry->vlan pointer before RCU grace period starts.
This allows macvlan_forward_source() to skip over
entrie
nvdosv
CVE-2026-23012HIGHCVSS 7.8≥ 6.17.1, < 6.18.7v6.17+1 more2026-01-25
CVE-2026-23012 [HIGH] CWE-416 CVE-2026-23012: In the Linux kernel, the following vulnerability has been resolved:
mm/damon/core: remove call_cont
In the Linux kernel, the following vulnerability has been resolved:
mm/damon/core: remove call_control in inactive contexts
If damon_call() is executed against a DAMON context that is not running,
the function returns error while keeping the damon_call_control object
linked to the context's call_controls list. Let's suppose the object is
deallocated
nvdosv
CVE-2026-22998HIGHCVSS 7.5≥ 5.4.268, < 5.5≥ 5.10.209, < 5.10.249+6 more2026-01-25
CVE-2026-22998 [HIGH] CWE-476 CVE-2026-22998: In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: fix NULL pointer dere
In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec
Commit efa56305908b ("nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length")
added ttag bounds checking and data_offset
validation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate
whet
nvdosv
CVE-2025-71162HIGHCVSS 7.8≥ 4.7, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-01-25
CVE-2025-71162 [HIGH] CWE-416 CVE-2025-71162: In the Linux kernel, the following vulnerability has been resolved:
dmaengine: tegra-adma: Fix use-
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: tegra-adma: Fix use-after-free
A use-after-free bug exists in the Tegra ADMA driver when audio streams
are terminated, particularly during XRUN conditions. The issue occurs
when the DMA buffer is freed by tegra_adma_terminate_all() before the
vchan completion tasklet fini
nvdosv
CVE-2026-22997MEDIUMCVSS 5.5≥ 5.4, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-01-25
CVE-2026-22997 [MEDIUM] CVE-2026-22997: In the Linux kernel, the following vulnerability has been resolved:
net: can: j1939: j1939_xtp_rx_r
In the Linux kernel, the following vulnerability has been resolved:
net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts
Since j1939_session_deactivate_activate_next() in j1939_tp_rxtimer() is
called only when the timer is enabled, we need to call
j1939_session_deactivate_activate_next() if we cancelled the
nvdosv
CVE-2026-23011MEDIUMCVSS 5.5≥ 3.10.1, < 5.10.249≥ 5.11, < 5.15.199+6 more2026-01-25
CVE-2026-23011 [MEDIUM] CVE-2026-23011: In the Linux kernel, the following vulnerability has been resolved:
ipv4: ip_gre: make ipgre_header
In the Linux kernel, the following vulnerability has been resolved:
ipv4: ip_gre: make ipgre_header() robust
Analog to commit db5b4e39c4e6 ("ip6_gre: make ip6gre_header() robust")
Over the years, syzbot found many ways to crash the kernel
in ipgre_header() [1].
This involves team or bonding drivers ability to dynamically
change their dev->needed_headroo
nvdosv
CVE-2026-23009MEDIUMCVSS 5.5≥ 6.16.1, < 6.18.7v6.16+1 more2026-01-25
CVE-2026-23009 [MEDIUM] CVE-2026-23009: In the Linux kernel, the following vulnerability has been resolved:
xhci: sideband: don't dereferen
In the Linux kernel, the following vulnerability has been resolved:
xhci: sideband: don't dereference freed ring when removing sideband endpoint
xhci_sideband_remove_endpoint() incorrecly assumes that the endpoint is
running and has a valid transfer ring.
Lianqin reported a crash during suspend/wake-up stress testing, and
found the cause to be dereferenc
nvdosv