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 25 of 724
CVE-2026-23041UNKNOWN≥ 0, < 6.18.8-12026-02-04
CVE-2026-23041 CVE-2026-23041: In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix NULL pointer crash in bnxt_ptp_enable during error cleanup When bnxt_
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix NULL pointer crash in bnxt_ptp_enable during error cleanup When bnxt_init_one() fails during initialization (e.g., bnxt_init_int_mode returns -ENODEV), the error path calls bnxt_free_hwrm_resources() which destroys the DMA pool and sets
osv
CVE-2026-23052UNKNOWN≥ 0, < 6.18.8-12026-02-04
CVE-2026-23052 CVE-2026-23052: In the Linux kernel, the following vulnerability has been resolved: ftrace: Do not over-allocate ftrace memory The pg_remaining calculation in ftrace_
In the Linux kernel, the following vulnerability has been resolved: ftrace: Do not over-allocate ftrace memory The pg_remaining calculation in ftrace_process_locs() assumes that ENTRIES_PER_PAGE multiplied by 2^order equals the actual capacity of the allocated page group. However, ENTRIES_PER_PAGE is PAGE_SIZE / ENTR
osv
CVE-2026-23045UNKNOWN≥ 0, < 6.18.8-12026-02-04
CVE-2026-23045 CVE-2026-23045: In the Linux kernel, the following vulnerability has been resolved: net/ena: fix missing lock when update devlink params Fix assert lock warning while
In the Linux kernel, the following vulnerability has been resolved: net/ena: fix missing lock when update devlink params Fix assert lock warning while calling devl_param_driverinit_value_set() in ena. WARNING: net/devlink/core.c:261 at devl_assert_locked+0x62/0x90, CPU#0: kworker/0:0/9 CPU: 0 UID: 0 PID: 9 Comm: kwor
osv
CVE-2025-71199UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2026-02-04
CVE-2025-71199 CVE-2025-71199: In the Linux kernel, the following vulnerability has been resolved: iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver at9
In the Linux kernel, the following vulnerability has been resolved: iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver at91_adc_interrupt can call at91_adc_touch_data_handler function to start the work by schedule_work(&st->touch_st.workq). If we remove the module which will call at91_adc_
osv
CVE-2026-23049UNKNOWN≥ 4.19.0, < 5.10.249≥ 5.11.0, < 5.15.199+4 more2026-02-04
CVE-2026-23049 drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel
drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel
In the Linux kernel, the following vulnerability has been resolved:
drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel
The connector type for the DataImage SCF0700C48GGU18 panel is missing and
devm_drm_panel_bridge_add() requires connector type to be set. This leads
to a warning and a backtrace in the kernel log
osv
CVE-2025-71196UNKNOWN≥ 4.17.0, < 5.10.249≥ 5.11.0, < 5.15.199+4 more2026-02-04
CVE-2025-71196 phy: stm32-usphyc: Fix off by one in probe()
phy: stm32-usphyc: Fix off by one in probe()
In the Linux kernel, the following vulnerability has been resolved:
phy: stm32-usphyc: Fix off by one in probe()
The "index" variable is used as an index into the usbphyc->phys[] array
which has usbphyc->nphys elements. So if it is equal to usbphyc->nphys
then it is one element out of bounds. The "index" comes from the
device tree so it's data that we trust and it's unlikely to be wrong,
h
osv
CVE-2025-71194UNKNOWN≥ 3.11.0, < 5.10.249≥ 5.11.0, < 5.15.199+4 more2026-02-04
CVE-2025-71194 btrfs: fix deadlock in wait_current_trans() due to ignored transaction type
btrfs: fix deadlock in wait_current_trans() due to ignored transaction type
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix deadlock in wait_current_trans() due to ignored transaction type
When wait_current_trans() is called during start_transaction(), it
currently waits for a blocked transaction without considering whether
the given transaction type actually needs to wait
osv
CVE-2026-23054UNKNOWN≥ 0, < 6.1.162-1≥ 0, < 6.12.69-1+1 more2026-02-04
CVE-2026-23054 CVE-2026-23054: In the Linux kernel, the following vulnerability has been resolved: net: hv_netvsc: reject RSS hash key programming without RX indirection table RSS c
In the Linux kernel, the following vulnerability has been resolved: net: hv_netvsc: reject RSS hash key programming without RX indirection table RSS configuration requires a valid RX indirection table. When the device reports a single receive queue, rndis_filter_device_add() does not allocate an indirection table, ac
osv
CVE-2026-23046UNKNOWN≥ 0, < 6.18.8-12026-02-04
CVE-2026-23046 CVE-2026-23046: In the Linux kernel, the following vulnerability has been resolved: virtio_net: fix device mismatch in devm_kzalloc/devm_kfree Initial rss_hdr allocat
In the Linux kernel, the following vulnerability has been resolved: virtio_net: fix device mismatch in devm_kzalloc/devm_kfree Initial rss_hdr allocation uses virtio_device->device, but virtnet_set_queues() frees using net_device->device. This device mismatch causing below devres warning [ 3788.514041] ------------[
osv
CVE-2026-23055UNKNOWN≥ 0, < 6.12.69-1≥ 0, < 6.18.8-12026-02-04
CVE-2026-23055 CVE-2026-23055: In the Linux kernel, the following vulnerability has been resolved: i2c: riic: Move suspend handling to NOIRQ phase Commit 53326135d0e0 ("i2c: riic: A
In the Linux kernel, the following vulnerability has been resolved: i2c: riic: Move suspend handling to NOIRQ phase Commit 53326135d0e0 ("i2c: riic: Add suspend/resume support") added suspend support for the Renesas I2C driver and following this change on RZ/G3E the following WARNING is seen on entering suspend ... [
osv
CVE-2026-23042UNKNOWN≥ 0, < 6.18.8-12026-02-04
CVE-2026-23042 CVE-2026-23042: In the Linux kernel, the following vulnerability has been resolved: idpf: fix aux device unplugging when rdma is not supported by vport If vport flags
In the Linux kernel, the following vulnerability has been resolved: idpf: fix aux device unplugging when rdma is not supported by vport If vport flags do not contain VIRTCHNL2_VPORT_ENABLE_RDMA, driver does not allocate vdev_info for this vport. This leads to kernel NULL pointer dereference in idpf_idc_vport_dev_down
osv
CVE-2026-23044UNKNOWN≥ 0, < 6.18.8-12026-02-04
CVE-2026-23044 CVE-2026-23044: In the Linux kernel, the following vulnerability has been resolved: PM: hibernate: Fix crash when freeing invalid crypto compressor When crypto_alloc_
In the Linux kernel, the following vulnerability has been resolved: PM: hibernate: Fix crash when freeing invalid crypto compressor When crypto_alloc_acomp() fails, it returns an ERR_PTR value, not NULL. The cleanup code in save_compressed_image() and load_compressed_image() unconditionally calls crypto_free_acomp()
osv
CVE-2026-23048UNKNOWN≥ 0, < 6.18.8-12026-02-04
CVE-2026-23048 CVE-2026-23048: In the Linux kernel, the following vulnerability has been resolved: udp: call skb_orphan() before skb_attempt_defer_free() Standard UDP receive path d
In the Linux kernel, the following vulnerability has been resolved: udp: call skb_orphan() before skb_attempt_defer_free() Standard UDP receive path does not use skb->destructor. But skmsg layer does use it, since it calls skb_set_owner_sk_safe() from udp_read_skb(). This then triggers this warning in skb_attempt_def
osv
CVE-2026-23025HIGHCVSS 7.8≥ 6.1.57, < 6.1.162≥ 6.2.1, < 6.6.122+4 more2026-01-31
CVE-2026-23025 [HIGH] CVE-2026-23025: In the Linux kernel, the following vulnerability has been resolved:
mm/page_alloc: prevent pcp corr
In the Linux kernel, the following vulnerability has been resolved:
mm/page_alloc: prevent pcp corruption with SMP=n
The kernel test robot has reported:
BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28
lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0
CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00
nvdosv
CVE-2025-71186MEDIUMCVSS 5.5≥ 4.15.1, < 5.10.249≥ 5.11, < 5.15.199+6 more2026-01-31
CVE-2025-71186 [MEDIUM] CWE-401 CVE-2025-71186: In the Linux kernel, the following vulnerability has been resolved:
dmaengine: stm32: dmamux: fix d
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: stm32: dmamux: fix device leak on route allocation
Make sure to drop the reference taken when looking up the DMA mux
platform device during route allocation.
Note that holding a reference to a device does not prevent its driver
data from going away so there is no point
nvdosv
CVE-2026-23023MEDIUMCVSS 5.5≥ 6.7.1, < 6.12.66≥ 6.13, < 6.18.6+2 more2026-01-31
CVE-2026-23023 [MEDIUM] CWE-401 CVE-2026-23023: In the Linux kernel, the following vulnerability has been resolved:
idpf: fix memory leak in idpf_v
In the Linux kernel, the following vulnerability has been resolved:
idpf: fix memory leak in idpf_vport_rel()
Free vport->rx_ptype_lkup in idpf_vport_rel() to avoid leaking memory
during a reset. Reported by kmemleak:
unreferenced object 0xff450acac838a000 (size 4096):
comm "kworker/u258:5", pid 7732, jiffies 4296830044
hex dump (first 32 bytes):
nvdosv
CVE-2026-23022MEDIUMCVSS 5.5≥ 6.17.1, < 6.18.6v6.17+1 more2026-01-31
CVE-2026-23022 [MEDIUM] CWE-401 CVE-2026-23022: In the Linux kernel, the following vulnerability has been resolved:
idpf: fix memory leak in idpf_v
In the Linux kernel, the following vulnerability has been resolved:
idpf: fix memory leak in idpf_vc_core_deinit()
Make sure to free hw->lan_regs. Reported by kmemleak during reset:
unreferenced object 0xff1b913d02a936c0 (size 96):
comm "kworker/u258:14", pid 2174, jiffies 4294958305
hex dump (first 32 bytes):
00 00 00 c0 a8 ba 2d ff 00 00 00 00
nvdosv
CVE-2025-71185MEDIUMCVSS 5.5≥ 4.4.1, < 5.10.249≥ 5.11, < 5.15.199+6 more2026-01-31
CVE-2025-71185 [MEDIUM] CWE-401 CVE-2025-71185: In the Linux kernel, the following vulnerability has been resolved:
dmaengine: ti: dma-crossbar: fi
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation
Make sure to drop the reference taken when looking up the crossbar
platform device during am335x route allocation.
nvdosv
CVE-2025-71188MEDIUMCVSS 5.5≥ 4.3.1, < 5.10.249≥ 5.11, < 5.15.199+6 more2026-01-31
CVE-2025-71188 [MEDIUM] CWE-401 CVE-2025-71188: In the Linux kernel, the following vulnerability has been resolved:
dmaengine: lpc18xx-dmamux: fix
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: lpc18xx-dmamux: fix device leak on route allocation
Make sure to drop the reference taken when looking up the DMA mux
platform device during route allocation.
Note that holding a reference to a device does not prevent its driver
data from going away so there is no point
nvdosv
CVE-2025-71180MEDIUMCVSS 5.5≥ 5.13.1, < 5.15.198≥ 5.16, < 6.1.161+5 more2026-01-31
CVE-2025-71180 [MEDIUM] CVE-2025-71180: In the Linux kernel, the following vulnerability has been resolved:
counter: interrupt-cnt: Drop IR
In the Linux kernel, the following vulnerability has been resolved:
counter: interrupt-cnt: Drop IRQF_NO_THREAD flag
An IRQ handler can either be IRQF_NO_THREAD or acquire spinlock_t, as
CONFIG_PROVE_RAW_LOCK_NESTING warns:
[ BUG: Invalid wait context ]
6.18.0-rc1+git... #1
some-user-space-process/1251 is trying to lock:
(&counter->events_list_lock){....}
nvdosv