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 74 of 724
CVE-2025-40357UNKNOWN≥ 6.11.0, < 6.12.56≥ 6.13.0, < 6.17.62025-12-16
CVE-2025-40357 net/smc: fix general protection fault in __smc_diag_dump
net/smc: fix general protection fault in __smc_diag_dump
In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix general protection fault in __smc_diag_dump
The syzbot report a crash:
Oops: general protection fault, probably for non-canonical address 0xfbd5a5d5a0000003: 0000 [#1] SMP KASAN NOPTI
KASAN: maybe wild-memory-access in range [0xdead4ead00000018-0xdead4ead0000001f]
CPU: 1 UID: 0 PID: 69
osv
CVE-2025-40356UNKNOWN≥ 0, < 6.17.6-12025-12-16
CVE-2025-40356 CVE-2025-40356: In the Linux kernel, the following vulnerability has been resolved: spi: rockchip-sfc: Fix DMA-API usage Use DMA-API dma_map_single() call for getting
In the Linux kernel, the following vulnerability has been resolved: spi: rockchip-sfc: Fix DMA-API usage Use DMA-API dma_map_single() call for getting the DMA address of the transfer buffer instead of hacking with virt_to_phys(). This fixes the following DMA-API debug warning: ------------[ cut here ]------------ DMA
osv
CVE-2025-68198UNKNOWN≥ 6.5.0, < 6.6.118≥ 6.7.0, < 6.12.59+1 more2025-12-16
CVE-2025-68198 crash: fix crashkernel resource shrink
crash: fix crashkernel resource shrink
In the Linux kernel, the following vulnerability has been resolved:
crash: fix crashkernel resource shrink
When crashkernel is configured with a high reservation, shrinking its
value below the low crashkernel reservation causes two issues:
1. Invalid crashkernel resource objects
2. Kernel crash if crashkernel shrinking is done twice
For example, with crashkernel=200M,high, the kernel reserves 200MB
osv
CVE-2025-68322UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.8-12025-12-16
CVE-2025-68322 CVE-2025-68322: In the Linux kernel, the following vulnerability has been resolved: parisc: Avoid crash due to unaligned access in unwinder Guenter Roeck reported thi
In the Linux kernel, the following vulnerability has been resolved: parisc: Avoid crash due to unaligned access in unwinder Guenter Roeck reported this kernel crash on his emulated B160L machine: Starting network: udhcpc: started, v1.36.1 Backtrace: [] unwind_once+0x1c/0x5c [] walk_stackframe.isra.0+0x74/0xb8 [] arch
osv
CVE-2025-68208UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-16
CVE-2025-68208 CVE-2025-68208: In the Linux kernel, the following vulnerability has been resolved: bpf: account for current allocated stack depth in widen_imprecise_scalars() The us
In the Linux kernel, the following vulnerability has been resolved: bpf: account for current allocated stack depth in widen_imprecise_scalars() The usage pattern for widen_imprecise_scalars() looks as follows: prev_st = find_prev_entry(env, ...); queued_st = push_stack(...); widen_imprecise_scalars(env, prev_st, queu
osv
CVE-2025-68266UNKNOWN≥ 2.6.12, < 5.10.248≥ 5.11.0, < 5.15.198+4 more2025-12-16
CVE-2025-68266 bfs: Reconstruct file type when loading from disk
bfs: Reconstruct file type when loading from disk
In the Linux kernel, the following vulnerability has been resolved:
bfs: Reconstruct file type when loading from disk
syzbot is reporting that S_IFMT bits of inode->i_mode can become bogus when
the S_IFMT bits of the 32bits "mode" field loaded from disk are corrupted
or when the 32bits "attributes" field loaded from disk are corrupted.
A documentation says that BFS uses only low
osv
CVE-2025-68284UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-16
CVE-2025-68284 CVE-2025-68284: In the Linux kernel, the following vulnerability has been resolved: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() The l
In the Linux kernel, the following vulnerability has been resolved: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() The len field originates from untrusted network packets. Boundary checks have been added to prevent potential out-of-bounds writes when decrypting the connection secret or p
osv
CVE-2025-68193UNKNOWN≥ 6.10.0, < 6.17.82025-12-16
CVE-2025-68193 drm/xe/guc: Add devm release action to safely tear down CT
drm/xe/guc: Add devm release action to safely tear down CT
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/guc: Add devm release action to safely tear down CT
When a buffer object (BO) is allocated with the XE_BO_FLAG_GGTT_INVALIDATE
flag, the driver initiates TLB invalidation requests via the CTB mechanism
while releasing the BO. However a premature release of the CTB BO can lead
to system cr
osv
CVE-2025-68207UNKNOWN≥ 0, < 6.12.59≥ 6.13.0, < 6.17.92025-12-16
CVE-2025-68207 drm/xe/guc: Synchronize Dead CT worker with unbind
drm/xe/guc: Synchronize Dead CT worker with unbind
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/guc: Synchronize Dead CT worker with unbind
Cancel and wait for any Dead CT worker to complete before continuing
with device unbinding. Else the worker will end up using resources freed
by the undind operation.
(cherry picked from commit 492671339114e376aaa38626d637a2751cdef263)
osv
CVE-2025-68220UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68220 CVE-2025-68220: In the Linux kernel, the following vulnerability has been resolved: net: ethernet: ti: netcp: Standardize knav_dma_open_channel to return NULL on erro
In the Linux kernel, the following vulnerability has been resolved: net: ethernet: ti: netcp: Standardize knav_dma_open_channel to return NULL on error Make knav_dma_open_channel consistently return NULL on error instead of ERR_PTR. Currently the header include/linux/soc/ti/knav_dma.h returns NULL when the driver is
osv
CVE-2025-68226UNKNOWN≥ 6.17.8, < 6.17.102025-12-16
CVE-2025-68226 smb: client: fix incomplete backport in cfids_invalidation_worker()
smb: client: fix incomplete backport in cfids_invalidation_worker()
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix incomplete backport in cfids_invalidation_worker()
The previous commit bdb596ceb4b7 ("smb: client: fix potential UAF in
smb2_close_cached_fid()") was an incomplete backport and missed one
kref_put() call in cfids_invalidation_worker() that should have been
conv
osv
CVE-2025-68194UNKNOWN≥ 2.6.35, < 5.4.302≥ 5.5.0, < 5.10.247+5 more2025-12-16
CVE-2025-68194 media: imon: make send_packet() more robust
media: imon: make send_packet() more robust
In the Linux kernel, the following vulnerability has been resolved:
media: imon: make send_packet() more robust
syzbot is reporting that imon has three problems which result in
hung tasks due to forever holding device lock [1].
First problem is that when usb_rx_callback_intf0() once got -EPROTO error
after ictx->dev_present_intf0 became true, usb_rx_callback_intf0()
resubmits urb after prin
osv
CVE-2025-68217UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68217 CVE-2025-68217: In the Linux kernel, the following vulnerability has been resolved: Input: pegasus-notetaker - fix potential out-of-bounds access In the pegasus_notet
In the Linux kernel, the following vulnerability has been resolved: Input: pegasus-notetaker - fix potential out-of-bounds access In the pegasus_notetaker driver, the pegasus_probe() function allocates the URB transfer buffer using the wMaxPacketSize value from the endpoint descriptor. An attacker can use a malicious
osv
CVE-2025-68306UNKNOWN≥ 6.11.0, < 6.12.61≥ 6.13.0, < 6.17.112025-12-16
CVE-2025-68306 Bluetooth: btusb: mediatek: Fix kernel crash when releasing mtk iso interface
Bluetooth: btusb: mediatek: Fix kernel crash when releasing mtk iso interface
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btusb: mediatek: Fix kernel crash when releasing mtk iso interface
When performing reset tests and encountering abnormal card drop issues
that lead to a kernel crash, it is necessary to perform a null check
before releasing resources to avoid atte
osv
CVE-2025-68227UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68227 CVE-2025-68227: In the Linux kernel, the following vulnerability has been resolved: mptcp: Fix proto fallback detection with BPF The sockmap feature allows bpf syscal
In the Linux kernel, the following vulnerability has been resolved: mptcp: Fix proto fallback detection with BPF The sockmap feature allows bpf syscall from userspace, or based on bpf sockops, replacing the sk_prot of sockets during protocol stack processing with sockmap's custom read/write interfaces. ''' tcp_rcv_st
osv
CVE-2025-68196UNKNOWN≥ 0, < 6.17.8-12025-12-16
CVE-2025-68196 CVE-2025-68196: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Cache streams targeting link when performing LT automation [WHY]
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Cache streams targeting link when performing LT automation [WHY] Last LT automation update can cause crash by referencing current_state and calling into dc_update_planes_and_stream which may clobber current_state. [HOW] Cache relevant
osv
CVE-2025-68248UNKNOWN≥ 6.17.0, < 6.17.62025-12-16
CVE-2025-68248 vmw_balloon: indicate success when effectively deflating during migration
vmw_balloon: indicate success when effectively deflating during migration
In the Linux kernel, the following vulnerability has been resolved:
vmw_balloon: indicate success when effectively deflating during migration
When migrating a balloon page, we first deflate the old page to then
inflate the new page.
However, if inflating the new page succeeded, we effectively deflated the
old page, reducing the bal
osv
CVE-2025-68168UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68168 CVE-2025-68168: In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager in
In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager initialization in txInit() was not properly initializing TxBlock[0].waitor waitqueue, causing a crash when txEnd(0) is called on read-only filesystems. When a filesystem
osv
CVE-2025-40346UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.158-1+2 more2025-12-16
CVE-2025-40346 CVE-2025-40346: In the Linux kernel, the following vulnerability has been resolved: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() Fix inco
In the Linux kernel, the following vulnerability has been resolved: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() Fix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity() which causes the code to proceed with NULL clock pointers. The current logic uses !PTR_ERR_OR_ZERO(cpu_c
osv
CVE-2025-68321UNKNOWN≥ 4.18.0, < 5.15.197≥ 5.16.0, < 6.1.159+3 more2025-12-16
CVE-2025-68321 page_pool: always add GFP_NOWARN for ATOMIC allocations
page_pool: always add GFP_NOWARN for ATOMIC allocations
In the Linux kernel, the following vulnerability has been resolved:
page_pool: always add GFP_NOWARN for ATOMIC allocations
Driver authors often forget to add GFP_NOWARN for page allocation
from the datapath. This is annoying to users as OOMs are a fact
of life, and we pretty much expect network Rx to hit page allocation
failures during OOM. Make page pool add GFP_NOW
osv