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 12 of 725
CVE-2026-23253HIGHCVSS 7.8≥ 2.6.17, < 6.1.167≥ 6.2.0, < 6.6.130+3 more2026-03-18
CVE-2026-23253 [HIGH] media: dvb-core: fix wrong reinitialization of ringbuffer on reopen media: dvb-core: fix wrong reinitialization of ringbuffer on reopen In the Linux kernel, the following vulnerability has been resolved: media: dvb-core: fix wrong reinitialization of ringbuffer on reopen dvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the DVR device. dvb_ringbuffer_init() calls init_waitqueue_head(), which reinitializes the waitqueue list head to empty. Since dmxdev->
osv
CVE-2026-23243HIGHCVSS 7.8≥ 2.6.24, < 5.10.252≥ 5.11.0, < 5.15.202+5 more2026-03-18
CVE-2026-23243 [HIGH] RDMA/umad: Reject negative data_len in ib_umad_write RDMA/umad: Reject negative data_len in ib_umad_write In the Linux kernel, the following vulnerability has been resolved: RDMA/umad: Reject negative data_len in ib_umad_write ib_umad_write computes data_len from user-controlled count and the MAD header sizes. With a mismatched user MAD header size and RMPP header length, data_len can become negative and reach ib_create_send_mad(). This can make the padding calculation e
osv
CVE-2026-23270HIGHCVSS 7.8≥ 0, < 6.1.167≥ 6.2.0, < 6.6.130+3 more2026-03-18
CVE-2026-23270 [HIGH] net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks In the Linux kernel, the following vulnerability has been resolved: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks As Paolo said earlier [1]: "Since the blamed commit below, classify can return TC_ACT_CONSUMED while the current skb being held by the defragmentation engine. As repo
osv
CVE-2026-23248HIGHCVSS 7.8≥ 6.14.0, < 6.18.17≥ 6.19.0, < 6.19.72026-03-18
CVE-2026-23248 [HIGH] perf/core: Fix refcount bug and potential UAF in perf_mmap perf/core: Fix refcount bug and potential UAF in perf_mmap In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix refcount bug and potential UAF in perf_mmap Syzkaller reported a refcount_t: addition on 0; use-after-free warning in perf_mmap. The issue is caused by a race condition between a failing mmap() setup and a concurrent mmap() on a dependent event (e.g., using output redirect
osv
CVE-2026-23245HIGHCVSS 7.8≥ 0, < 6.19.8-12026-03-18
CVE-2026-23245 [HIGH] CVE-2026-23245: In the Linux kernel, the following vulnerability has been resolved: net/sched: act_gate: snapshot parameters with RCU on replace The gate action can b In the Linux kernel, the following vulnerability has been resolved: net/sched: act_gate: snapshot parameters with RCU on replace The gate action can be replaced while the hrtimer callback or dump path is walking the schedule list. Convert the parameters to an RCU-protected snapshot and swap updates under tcf_l
osv
CVE-2026-23246HIGHCVSS 8.8≥ 6.5.0, < 6.6.130≥ 6.7.0, < 6.12.77+2 more2026-03-18
CVE-2026-23246 [HIGH] wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration link_id is taken from the ML Reconfiguration element (control & 0x000f), so it can be 0..15. link_removal_timeout[] has IEEE80211_MLD_MAX_NUM_LINKS (15) elements, so index 15 is out-of-bounds. Skip su
osv
CVE-2026-23268HIGHCVSS 7.8≥ 4.11.0, < 6.6.130≥ 6.7.0, < 6.12.77+2 more2026-03-18
CVE-2026-23268 [HIGH] apparmor: fix unprivileged local user can do privileged policy management apparmor: fix unprivileged local user can do privileged policy management In the Linux kernel, the following vulnerability has been resolved: apparmor: fix unprivileged local user can do privileged policy management An unprivileged local user can load, replace, and remove profiles by opening the apparmorfs interfaces, via a confused deputy attack, by passing the opened fd to a privileged process, a
osv
CVE-2026-23269HIGHCVSS 7.1≥ 3.4.0, < 6.6.130≥ 6.7.0, < 6.12.77+2 more2026-03-18
CVE-2026-23269 [HIGH] apparmor: validate DFA start states are in bounds in unpack_pdb apparmor: validate DFA start states are in bounds in unpack_pdb In the Linux kernel, the following vulnerability has been resolved: apparmor: validate DFA start states are in bounds in unpack_pdb Start states are read from untrusted data and used as indexes into the DFA state tables. The aa_dfa_next() function call in unpack_pdb() will access dfa->tables[YYTD_ID_BASE][start], and if the start state exceeds t
osv
CVE-2026-23242HIGHCVSS 7.5≥ 0, < 6.18.14-12026-03-18
CVE-2026-23242 [HIGH] CVE-2026-23242: In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix potential NULL pointer dereference in header processing If siw_get_h In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix potential NULL pointer dereference in header processing If siw_get_hdr() returns -EINVAL before set_rx_fpdu_context(), qp->rx_fpdu can be NULL. The error path in siw_tcp_rx_data() dereferences qp->rx_fpdu->more_ddp_segs without c
osv
CVE-2025-71266UNKNOWN≥ 5.15.0, < 5.15.202≥ 5.16.0, < 6.1.165+4 more2026-03-18
CVE-2025-71266 fs: ntfs3: check return value of indx_find to avoid infinite loop fs: ntfs3: check return value of indx_find to avoid infinite loop In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: check return value of indx_find to avoid infinite loop We found an infinite loop bug in the ntfs3 file system that can lead to a Denial-of-Service (DoS) condition. A malformed dentry in the ntfs3 filesystem can cause the kernel to hang during the lookup operations. By s
osv
CVE-2026-23252UNKNOWN≥ 6.10.0, < 6.12.78≥ 6.13.0, < 6.18.16+1 more2026-03-18
CVE-2026-23252 xfs: get rid of the xchk_xfile_*_descr calls xfs: get rid of the xchk_xfile_*_descr calls In the Linux kernel, the following vulnerability has been resolved: xfs: get rid of the xchk_xfile_*_descr calls The xchk_xfile_*_descr macros call kasprintf, which can fail to allocate memory if the formatted string is larger than 16 bytes (or whatever the nofail guarantees are nowadays). Some of them could easily exceed that, and Jiaming Zhang found a few places where that can happen wit
osv
CVE-2026-23244UNKNOWN≥ 0, < 6.19.8-12026-03-18
CVE-2026-23244 CVE-2026-23244: In the Linux kernel, the following vulnerability has been resolved: nvme: fix memory allocation in nvme_pr_read_keys() nvme_pr_read_keys() takes num_k In the Linux kernel, the following vulnerability has been resolved: nvme: fix memory allocation in nvme_pr_read_keys() nvme_pr_read_keys() takes num_keys from userspace and uses it to calculate the allocation size for rse via struct_size(). The upper limit is PR_KEYS_MAX (64K). A malicious or buggy userspace can pass
osv
CVE-2026-23260UNKNOWN≥ 0, < 6.12.73-1≥ 0, < 6.18.10-12026-03-18
CVE-2026-23260 CVE-2026-23260: In the Linux kernel, the following vulnerability has been resolved: regmap: maple: free entry on mas_store_gfp() failure regcache_maple_write() alloca In the Linux kernel, the following vulnerability has been resolved: regmap: maple: free entry on mas_store_gfp() failure regcache_maple_write() allocates a new block ('entry') to merge adjacent ranges and then stores it with mas_store_gfp(). When mas_store_gfp() fails, the new 'entry' remains allocated and is never f
osv
CVE-2026-23249UNKNOWN≥ 6.8.0, < 6.12.75≥ 6.13.0, < 6.18.16+1 more2026-03-18
CVE-2026-23249 xfs: check for deleted cursors when revalidating two btrees xfs: check for deleted cursors when revalidating two btrees In the Linux kernel, the following vulnerability has been resolved: xfs: check for deleted cursors when revalidating two btrees The free space and inode btree repair functions will rebuild both btrees at the same time, after which it needs to evaluate both btrees to confirm that the corruptions are gone. However, Jiaming Zhang ran syzbot and produced a crash
osv
CVE-2026-23256UNKNOWN≥ 4.10.0, < 5.10.250≥ 5.11.0, < 5.15.200+4 more2026-03-18
CVE-2026-23256 net: liquidio: Fix off-by-one error in VF setup_nic_devices() cleanup net: liquidio: Fix off-by-one error in VF setup_nic_devices() cleanup In the Linux kernel, the following vulnerability has been resolved: net: liquidio: Fix off-by-one error in VF 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 leak. Fix this by changing
osv
CVE-2025-71265UNKNOWN≥ 5.15.0, < 5.15.202≥ 5.16.0, < 6.1.165+4 more2026-03-18
CVE-2025-71265 fs: ntfs3: fix infinite loop in attr_load_runs_range on inconsistent metadata fs: ntfs3: fix infinite loop in attr_load_runs_range on inconsistent metadata In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: fix infinite loop in attr_load_runs_range on inconsistent metadata 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 attribute he
osv
CVE-2026-23263UNKNOWN≥ 0, < 6.18.10-12026-03-18
CVE-2026-23263 CVE-2026-23263: In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix page array leak d9f595b9a65e ("io_uring/zcrx: fix leaking pages In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix page array leak d9f595b9a65e ("io_uring/zcrx: fix leaking pages on sg init fail") fixed a page leakage but didn't free the page array, release it as well.
osv
CVE-2026-23267UNKNOWN≥ 0, < 6.1.164-1≥ 0, < 6.12.74-1+1 more2026-03-18
CVE-2026-23267 CVE-2026-23267: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic com In the Linux kernel, the following vulnerability has been resolved: f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes During SPO tests, when mounting F2FS, an -EINVAL error was returned from f2fs_recover_inode_page. The issue occurred under the following scena
osv
CVE-2026-23261UNKNOWN≥ 0, < 6.12.73-1≥ 0, < 6.18.10-12026-03-18
CVE-2026-23261 CVE-2026-23261: In the Linux kernel, the following vulnerability has been resolved: nvme-fc: release admin tagset if init fails nvme_fabrics creates an NVMe/FC contro In the Linux kernel, the following vulnerability has been resolved: nvme-fc: release admin tagset if init fails nvme_fabrics creates an NVMe/FC controller in following path: nvmf_dev_write() -> nvmf_create_ctrl() -> nvme_fc_create_ctrl() -> nvme_fc_init_ctrl() nvme_fc_init_ctrl() allocates the admin blk-mq resources
osv
CVE-2026-23254UNKNOWN≥ 0, < 6.12.73-1≥ 0, < 6.18.10-12026-03-18
CVE-2026-23254 CVE-2026-23254: In the Linux kernel, the following vulnerability has been resolved: net: gro: fix outer network offset The udp GRO complete stage assumes that all the In the Linux kernel, the following vulnerability has been resolved: net: gro: fix outer network offset The udp GRO complete stage assumes that all the packets inserted the RX have the `encapsulation` flag zeroed. Such assumption is not true, as a few H/W NICs can set such flag when H/W offloading the checksum for an
osv