Linux Kernel vulnerabilities

14,483 known vulnerabilities affecting linux/linux_kernel.

Total CVEs
14,483
CISA KEV
29
actively exploited
Public exploits
288
Exploited in wild
31
Severity breakdown
CRITICAL112HIGH3698MEDIUM8486LOW419UNKNOWN1768

Vulnerabilities

Page 13 of 725
CVE-2026-23255UNKNOWN≥ 0, < 6.18.10-12026-03-18
CVE-2026-23255 CVE-2026-23255: In the Linux kernel, the following vulnerability has been resolved: net: add proper RCU protection to /proc/net/ptype Yin Fengwei reported an RCU stal In the Linux kernel, the following vulnerability has been resolved: net: add proper RCU protection to /proc/net/ptype Yin Fengwei reported an RCU stall in ptype_seq_show() and provided a patch. Real issue is that ptype_seq_next() and ptype_seq_show() violate RCU rules. ptype_seq_show() runs under rcu_read_lock(), and
osv
CVE-2026-23266UNKNOWN≥ 2.6.12, < 5.10.251≥ 5.11.0, < 5.15.201+5 more2026-03-18
CVE-2026-23266 fbdev: rivafb: fix divide error in nv3_arb() fbdev: rivafb: fix divide error in nv3_arb() In the Linux kernel, the following vulnerability has been resolved: fbdev: rivafb: fix divide error in nv3_arb() A userspace program can trigger the RIVA NV3 arbitration code by calling the FBIOPUT_VSCREENINFO ioctl on /dev/fb*. When doing so, the driver recomputes FIFO arbitration parameters in nv3_arb(), using state->mclk_khz (derived from the PRAMDAC MCLK PLL) as a divisor without valid
osv
CVE-2025-71268UNKNOWN≥ 4.4.0, < 6.1.163≥ 6.2.0, < 6.6.124+2 more2026-03-18
CVE-2025-71268 btrfs: fix reservation leak in some error paths when inserting inline extent btrfs: fix reservation leak in some error paths when inserting inline extent In the Linux kernel, the following vulnerability has been resolved: btrfs: fix reservation leak in some error paths when inserting inline extent If we fail to allocate a path or join a transaction, we return from __cow_file_range_inline() without freeing the reserved qgroup data, resulting in a leak. Fix this by ensuring we ca
osv
CVE-2026-23265UNKNOWN≥ 3.8.0, < 6.18.13≥ 6.19.0, < 6.19.32026-03-18
CVE-2026-23265 f2fs: fix to do sanity check on node footer in {read,write}_end_io f2fs: fix to do sanity check on node footer in {read,write}_end_io In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node footer in {read,write}_end_io -----------[ cut here ]------------ kernel BUG at fs/f2fs/data.c:358! Call Trace: blk_update_request+0x5eb/0xe70 block/blk-mq.c:987 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1149 blk_complete_reqs block/blk-mq.
osv
CVE-2026-23251UNKNOWN≥ 0, < 6.19.6-12026-03-18
CVE-2026-23251 CVE-2026-23251: In the Linux kernel, the following vulnerability has been resolved: xfs: only call xf{array,blob}_destroy if we have a valid pointer Only call the xfa In the Linux kernel, the following vulnerability has been resolved: xfs: only call xf{array,blob}_destroy if we have a valid pointer Only call the xfarray and xfblob destructor if we have a valid pointer, and be sure to null out that pointer afterwards. Note that this patch fixes a large number of commits, most of wh
osv
CVE-2026-23250UNKNOWN≥ 6.10.0, < 6.12.75≥ 6.13.0, < 6.18.16+1 more2026-03-18
CVE-2026-23250 xfs: check return value of xchk_scrub_create_subord xfs: check return value of xchk_scrub_create_subord In the Linux kernel, the following vulnerability has been resolved: xfs: check return value of xchk_scrub_create_subord Fix this function to return NULL instead of a mangled ENOMEM, then fix the callers to actually check for a null pointer and return ENOMEM. Most of the corrections here are for code merged between 6.2 and 6.10.
osv
CVE-2026-23262UNKNOWN≥ 5.10.0, < 5.10.250≥ 5.11.0, < 5.15.200+4 more2026-03-18
CVE-2026-23262 gve: Fix stats report corruption on queue count change gve: Fix stats report corruption on queue count change In the Linux kernel, the following vulnerability has been resolved: gve: Fix stats report corruption on queue count change The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC's stats. When the number of queues is changed, the driver's stat
osv
CVE-2025-71269UNKNOWN≥ 0, < 6.18.10-12026-03-18
CVE-2025-71269 CVE-2025-71269: In the Linux kernel, the following vulnerability has been resolved: btrfs: do not free data reservation in fallback from inline due to -ENOSPC If we f In the Linux kernel, the following vulnerability has been resolved: btrfs: do not free data reservation in fallback from inline due to -ENOSPC If we fail to create an inline extent due to -ENOSPC, we will attempt to go through the normal COW path, reserve an extent, create an ordered extent, etc. However we were alwa
osv
CVE-2026-23247UNKNOWN≥ 4.11.0, < 6.18.17≥ 6.19.0, < 6.19.72026-03-18
CVE-2026-23247 tcp: secure_seq: add back ports to TS offset tcp: secure_seq: add back ports to TS offset In the Linux kernel, the following vulnerability has been resolved: tcp: secure_seq: add back ports to TS offset This reverts 28ee1b746f49 ("secure_seq: downgrade to per-host timestamp offsets") tcp_tw_recycle went away in 2017. Zhouyan Deng reported off-path TCP source port leakage via SYN cookie side-channel that can be fixed in multiple ways. One of them is to bring back TCP ports in
osv
CVE-2026-23257UNKNOWN≥ 0, < 5.10.251-1≥ 0, < 6.1.164-1+2 more2026-03-18
CVE-2026-23257 CVE-2026-23257: In the Linux kernel, the following vulnerability has been resolved: net: liquidio: Fix off-by-one error in PF setup_nic_devices() cleanup In setup_nic In the Linux kernel, the following vulnerability has been resolved: net: liquidio: Fix off-by-one error in PF setup_nic_devices() cleanup In setup_nic_devices(), the initialization loop jumps to the label setup_nic_dev_free on failure. The current cleanup loop while(i--) skip the failing index i, causing a memory lea
osv
CVE-2025-71267UNKNOWN≥ 5.15.0, < 5.15.202≥ 5.16.0, < 6.1.165+4 more2026-03-18
CVE-2025-71267 fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST We found an infinite loop bug in the ntfs3 file system that can lead to a Denial-of-Service (DoS) condition. A malformed NTFS image can cause an infinite loop when an ATTR_LIST attribute indicates a zero data size while the
osv
CVE-2026-23258UNKNOWN≥ 4.18.0, < 5.10.250≥ 5.11.0, < 5.15.200+4 more2026-03-18
CVE-2026-23258 net: liquidio: Initialize netdev pointer before queue setup net: liquidio: Initialize netdev pointer before queue setup In the Linux kernel, the following vulnerability has been resolved: net: liquidio: Initialize netdev pointer before queue setup In setup_nic_devices(), the netdev is allocated using alloc_etherdev_mq(). However, the pointer to this structure is stored in oct->props[i].netdev only after the calls to netif_set_real_num_rx_queues() and netif_set_real_num_tx_queue
osv
CVE-2025-71270UNKNOWN≥ 6.2.0, < 6.6.124≥ 6.7.0, < 6.12.70+1 more2026-03-18
CVE-2025-71270 LoongArch: Enable exception fixup for specific ADE subcode LoongArch: Enable exception fixup for specific ADE subcode In the Linux kernel, the following vulnerability has been resolved: LoongArch: Enable exception fixup for specific ADE subcode This patch allows the LoongArch BPF JIT to handle recoverable memory access errors generated by BPF_PROBE_MEM* instructions. When a BPF program performs memory access operations, the instructions it executes may trigger ADEM exceptions.
osv
CVE-2026-23264UNKNOWN≥ 5.18.0, < 6.1.163≥ 6.2.0, < 6.6.124+2 more2026-03-18
CVE-2026-23264 Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" In the Linux kernel, the following vulnerability has been resolved: Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" This reverts commit 7294863a6f01248d72b61d38478978d638641bee. This commit was erroneously applied again after commit 0ab5d711ec74 ("drm/amd: Refactor `amdgpu_aspm` to be evaluated per device") removed it, leading to very har
osv
CVE-2026-23259UNKNOWN≥ 6.10.0, < 6.18.102026-03-18
CVE-2026-23259 io_uring/rw: free potentially allocated iovec on cache put failure io_uring/rw: free potentially allocated iovec on cache put failure In the Linux kernel, the following vulnerability has been resolved: io_uring/rw: free potentially allocated iovec on cache put failure If a read/write request goes through io_req_rw_cleanup() and has an allocated iovec attached and fails to put to the rw_cache, then it may end up with an unaccounted iovec pointer. Have io_rw_recycle() return whet
osv
CVE-2025-71239UNKNOWN≥ 6.6.0, < 6.6.128≥ 6.7.0, < 6.12.75+2 more2026-03-17
CVE-2025-71239 audit: add fchmodat2() to change attributes class audit: add fchmodat2() to change attributes class In the Linux kernel, the following vulnerability has been resolved: audit: add fchmodat2() to change attributes class fchmodat2(), introduced in version 6.6 is currently not in the change attribute class of audit. Calling fchmodat2() to change a file attribute in the same fashion than chmod() or fchmodat() will bypass audit rules such as: -w /tmp/test -p rwa -k test_rwa The cur
osv
CVE-2026-23241UNKNOWN≥ 0, < 6.19.6-12026-03-17
CVE-2026-23241 CVE-2026-23241: In the Linux kernel, the following vulnerability has been resolved: audit: add missing syscalls to read class The "at" variant of getxattr() and listx In the Linux kernel, the following vulnerability has been resolved: audit: add missing syscalls to read class The "at" variant of getxattr() and listxattr() are missing from the audit read class. Calling getxattrat() or listxattrat() on a file to read its extended attributes will bypass audit rules such as: -w /tmp/t
osv
CVE-2026-23240CRITICALCVSS 9.8≥ 5.3.0, < 6.12.75≥ 6.13.0, < 6.18.16+1 more2026-03-10
CVE-2026-23240 [CRITICAL] tls: Fix race condition in tls_sw_cancel_work_tx() tls: Fix race condition in tls_sw_cancel_work_tx() In the Linux kernel, the following vulnerability has been resolved: tls: Fix race condition in tls_sw_cancel_work_tx() This issue was discovered during a code audit. After cancel_delayed_work_sync() is called from tls_sk_proto_close(), tx_work_handler() can still be scheduled from paths such as the Delayed ACK handler or ksoftirqd. As a result, the tx_work_handler()
osv
CVE-2026-23239HIGHCVSS 7.8≥ 5.6.0, < 6.12.75≥ 6.13.0, < 6.18.16+1 more2026-03-10
CVE-2026-23239 [HIGH] espintcp: Fix race condition in espintcp_close() espintcp: Fix race condition in espintcp_close() In the Linux kernel, the following vulnerability has been resolved: espintcp: Fix race condition in espintcp_close() This issue was discovered during a code audit. After cancel_work_sync() is called from espintcp_close(), espintcp_tx_work() can still be scheduled from paths such as the Delayed ACK handler or ksoftirqd. As a result, the espintcp_tx_work() worker may derefere
osv
CVE-2024-14027UNKNOWN≥ 6.11.0, < 6.12.772026-03-09
CVE-2024-14027 xattr: switch to CLASS(fd) xattr: switch to CLASS(fd) In the Linux kernel, the following vulnerability has been resolved: fs/xattr: missing fdput() in fremovexattr error path In the Linux kernel, the fremovexattr() syscall calls fdget() to acquire a file reference but returns early without calling fdput() when strncpy_from_user() fails on the name argument. In multi-threaded processes where fdget() takes the slow path, this permanently leaks one file reference per call, pinning
osv
Linux Kernel vulnerabilities | cvebase