Linux Kernel vulnerabilities
14,742 known vulnerabilities affecting linux/linux_kernel.
Total CVEs
14,742
CISA KEV
29
actively exploited
Public exploits
296
Exploited in wild
31
Severity breakdown
CRITICAL112HIGH3715MEDIUM8619LOW440UNKNOWN1856
Vulnerabilities
Page 118 of 738
CVE-2025-40017UNKNOWN≥ 6.15.0, < 6.16.11≥ 6.17.0, < 6.17.12025-10-20
CVE-2025-40017 media: iris: Fix memory leak by freeing untracked persist buffer
media: iris: Fix memory leak by freeing untracked persist buffer
In the Linux kernel, the following vulnerability has been resolved:
media: iris: Fix memory leak by freeing untracked persist buffer
One internal buffer which is allocated only once per session was not
being freed during session close because it was not being tracked as
part of internal buffer list which resulted in a memory leak.
Add the necessary
osv
CVE-2025-40004UNKNOWN≥ 6.12.0, < 6.12.53≥ 6.13.0, < 6.17.32025-10-20
CVE-2025-40004 net/9p: Fix buffer overflow in USB transport layer
net/9p: Fix buffer overflow in USB transport layer
In the Linux kernel, the following vulnerability has been resolved:
net/9p: Fix buffer overflow in USB transport layer
A buffer overflow vulnerability exists in the USB 9pfs transport layer
where inconsistent size validation between packet header parsing and
actual data copying allows a malicious USB host to overflow heap buffers.
The issue occurs because:
- usb9pfs_rx_header(
osv
CVE-2025-40006UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-20
CVE-2025-40006 CVE-2025-40006: In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix folio is still mapped when deleted Migration may be raced with fal
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix folio is still mapped when deleted Migration may be raced with fallocating hole. remove_inode_single_folio will unmap the folio if the folio is still mapped. However, it's called without folio lock. If the folio is migrated and the ma
osv
CVE-2025-40011UNKNOWN≥ 3.3.0, < 5.4.300≥ 5.5.0, < 5.10.245+5 more2025-10-20
CVE-2025-40011 drm/gma500: Fix null dereference in hdmi teardown
drm/gma500: Fix null dereference in hdmi teardown
In the Linux kernel, the following vulnerability has been resolved:
drm/gma500: Fix null dereference in hdmi teardown
pci_set_drvdata sets the value of pdev->driver_data to NULL,
after which the driver_data obtained from the same dev is
dereferenced in oaktrail_hdmi_i2c_exit, and the i2c_dev is
extracted from it. To prevent this, swap these calls.
Found by Linux Verification Cen
osv
CVE-2025-40012UNKNOWN≥ 6.10.0, < 6.12.50≥ 6.13.0, < 6.16.102025-10-20
CVE-2025-40012 net/smc: fix warning in smc_rx_splice() when calling get_page()
net/smc: fix warning in smc_rx_splice() when calling get_page()
In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix warning in smc_rx_splice() when calling get_page()
smc_lo_register_dmb() allocates DMB buffers with kzalloc(), which are
later passed to get_page() in smc_rx_splice(). Since kmalloc memory is
not page-backed, this triggers WARN_ON_ONCE() in get_page() and prevents
holding
osv
CVE-2025-40009UNKNOWN≥ 0, < 6.12.57-1≥ 0, < 6.16.10-12025-10-20
CVE-2025-40009 CVE-2025-40009: In the Linux kernel, the following vulnerability has been resolved: fs/proc/task_mmu: check p->vec_buf for NULL When the PAGEMAP_SCAN ioctl is invoked
In the Linux kernel, the following vulnerability has been resolved: fs/proc/task_mmu: check p->vec_buf for NULL When the PAGEMAP_SCAN ioctl is invoked with vec_len = 0 reaches pagemap_scan_backout_range(), kernel panics with null-ptr-deref: [ 44.936808] Oops: general protection fault, probably for non-canonical addre
osv
CVE-2025-40013UNKNOWN≥ 0, < 6.1.158-1≥ 0, < 6.12.57-1+1 more2025-10-20
CVE-2025-40013 CVE-2025-40013: In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: audioreach: fix potential null pointer dereference It is possible that
In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: audioreach: fix potential null pointer dereference It is possible that the topology parsing function audioreach_widget_load_module_common() could return NULL or an error pointer. Add missing NULL check so that we do not dereference it.
osv
CVE-2025-40010UNKNOWN≥ 6.0.0, < 6.1.155≥ 6.2.0, < 6.6.109+2 more2025-10-20
CVE-2025-40010 afs: Fix potential null pointer dereference in afs_put_server
afs: Fix potential null pointer dereference in afs_put_server
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix potential null pointer dereference in afs_put_server
afs_put_server() accessed server->debug_id before the NULL check, which
could lead to a null pointer dereference. Move the debug_id assignment,
ensuring we never dereference a NULL server pointer.
osv
CVE-2025-40016UNKNOWN≥ 5.7.0, < 6.6.110≥ 6.7.0, < 6.12.51+2 more2025-10-20
CVE-2025-40016 media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID
media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID
In the Linux kernel, the following vulnerability has been resolved:
media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID
Per UVC 1.1+ specification 3.7.2, units and terminals must have a non-zero
unique ID.
```
Each Unit and Terminal within the video function is assigned a unique
identification number, the Unit ID (UID) or Te
osv
CVE-2025-40007UNKNOWN≥ 6.16.0, < 6.16.102025-10-20
CVE-2025-40007 netfs: fix reference leak
netfs: fix reference leak
In the Linux kernel, the following vulnerability has been resolved:
netfs: fix reference leak
Commit 20d72b00ca81 ("netfs: Fix the request's work item to not
require a ref") modified netfs_alloc_request() to initialize the
reference counter to 2 instead of 1. The rationale was that the
requet's "work" would release the second reference after completion
(via netfs_{read,write}_collection_worker()). That works most of the
time i
osv
CVE-2025-40008UNKNOWN≥ 0, < 6.1.158-1≥ 0, < 6.12.57-1+1 more2025-10-20
CVE-2025-40008 CVE-2025-40008: In the Linux kernel, the following vulnerability has been resolved: kmsan: fix out-of-bounds access to shadow memory Running sha224_kunit on a KMSAN-e
In the Linux kernel, the following vulnerability has been resolved: kmsan: fix out-of-bounds access to shadow memory Running sha224_kunit on a KMSAN-enabled kernel results in a crash in kmsan_internal_set_shadow_origin(): BUG: unable to handle page fault for address: ffffbc3840291000 #PF: supervisor read access in ke
osv
CVE-2025-40002UNKNOWN≥ 0, < 6.17.6-12025-10-18
CVE-2025-40002 CVE-2025-40002: In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Fix use-after-free in tb_dp_dprx_work The original code relies on can
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Fix use-after-free in tb_dp_dprx_work The original code relies on cancel_delayed_work() in tb_dp_dprx_stop(), which does not ensure that the delayed work item tunnel->dprx_work has fully completed if it was already running. This leads to
osv
CVE-2025-40003UNKNOWN≥ 4.18.0, < 6.12.54≥ 6.13.0, < 6.17.42025-10-18
CVE-2025-40003 net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work
net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work
In the Linux kernel, the following vulnerability has been resolved:
net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work
The origin code calls cancel_delayed_work() in ocelot_stats_deinit()
to cancel the cyclic delayed work item ocelot->stats_work. However,
cancel_delayed_work() may fail to cancel the work item if it is already
e
osv
CVE-2025-40001UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-18
CVE-2025-40001 CVE-2025-40001: In the Linux kernel, the following vulnerability has been resolved: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue During the detaching of Mar
In the Linux kernel, the following vulnerability has been resolved: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue During the detaching of Marvell's SAS/SATA controller, the original code calls cancel_delayed_work() in mvs_free() to cancel the delayed work item mwq->work_q. However, if mwq->work_q is already
osv
CVE-2025-39967HIGHCVSS 7.8≥ 4.4.235, < 4.5≥ 4.9.235, < 4.10+12 more2025-10-15
CVE-2025-39967 [HIGH] CWE-190 CVE-2025-39967: In the Linux kernel, the following vulnerability has been resolved:
fbcon: fix integer overflow in
In the Linux kernel, the following vulnerability has been resolved:
fbcon: fix integer overflow in fbcon_do_set_font
Fix integer overflow vulnerabilities in fbcon_do_set_font() where font
size calculations could overflow when handling user-controlled font
parameters.
The vulnerabilities occur when:
1. CALC_FONTSZ(h, pitch, charcount) performs h * pi
nvdosv
CVE-2025-39966HIGHCVSS 7.0≥ 6.11, < 6.12.50≥ 6.13, < 6.16.10+1 more2025-10-15
CVE-2025-39966 [HIGH] CWE-362 CVE-2025-39966: In the Linux kernel, the following vulnerability has been resolved:
iommufd: Fix race during abort
In the Linux kernel, the following vulnerability has been resolved:
iommufd: Fix race during abort for file descriptors
fput() doesn't actually call file_operations release() synchronously, it
puts the file on a work queue and it will be released eventually.
This is normally fine, except for iommufd the file and the iommufd_object
are tied to gether
nvdosv
CVE-2025-39974UNKNOWN≥ 0, < 6.16.10-12025-10-15
CVE-2025-39974 CVE-2025-39974: In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Fix slab-out-of-bounds in _parse_integer_limit() When config osno
In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Fix slab-out-of-bounds in _parse_integer_limit() When config osnoise cpus by write() syscall, the following KASAN splat may be observed: BUG: KASAN: slab-out-of-bounds in _parse_integer_limit+0x103/0x130 Read of size 1 at addr ffff88
osv
CVE-2025-39981UNKNOWN≥ 5.17.0, < 6.12.59≥ 6.13.0, < 6.16.102025-10-15
CVE-2025-39981 Bluetooth: MGMT: Fix possible UAFs
Bluetooth: MGMT: Fix possible UAFs
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: MGMT: Fix possible UAFs
This attemps to fix possible UAFs caused by struct mgmt_pending being
freed while still being processed like in the following trace, in order
to fix mgmt_pending_valid is introduce and use to check if the
mgmt_pending hasn't been removed from the pending list, on the complete
callbacks it is used to check an
osv
CVE-2025-39996UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-10-15
CVE-2025-39996 CVE-2025-39996: In the Linux kernel, the following vulnerability has been resolved: media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove Th
In the Linux kernel, the following vulnerability has been resolved: media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove The original code uses cancel_delayed_work() in flexcop_pci_remove(), which does not guarantee that the delayed work item irq_check_work has fully completed if it was alr
osv
CVE-2025-39971UNKNOWN≥ 4.17.0, < 5.4.300≥ 5.5.0, < 5.10.245+5 more2025-10-15
CVE-2025-39971 i40e: fix idx validation in config queues msg
i40e: fix idx validation in config queues msg
In the Linux kernel, the following vulnerability has been resolved:
i40e: fix idx validation in config queues msg
Ensure idx is within range of active/initialized TCs when iterating over
vf->ch[idx] in i40e_vc_config_queues_msg().
osv