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 68 of 724
CVE-2025-68242UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.9-12025-12-16
CVE-2025-68242 CVE-2025-68242: In the Linux kernel, the following vulnerability has been resolved: NFS: Fix LTP test failures when timestamps are delegated The utimes01 and utime06 In the Linux kernel, the following vulnerability has been resolved: NFS: Fix LTP test failures when timestamps are delegated The utimes01 and utime06 tests fail when delegated timestamps are enabled, specifically in subtests that modify the atime and mtime fields using the 'nobody' user ID. The problem can be reproduc
osv
CVE-2025-68171UNKNOWN≥ 5.16.0, < 6.1.159≥ 6.2.0, < 6.6.117+2 more2025-12-16
CVE-2025-68171 x86/fpu: Ensure XFD state on signal delivery x86/fpu: Ensure XFD state on signal delivery In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Ensure XFD state on signal delivery Sean reported [1] the following splat when running KVM tests: WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70 Call Trace: fpu__clear_user_states+0x9c/0x100 arch_do_signal_or_restart+0x142/0x210 exit_to_user_mode_loop+0x55/0x100 do_syscall_64+0x205/0x2c0 entry_SYSC
osv
CVE-2025-68239UNKNOWN≥ 5.12.0, < 6.1.167≥ 6.2.0, < 6.6.130+2 more2025-12-16
CVE-2025-68239 binfmt_misc: restore write access before closing files opened by open_exec() binfmt_misc: restore write access before closing files opened by open_exec() In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: restore write access before closing files opened by open_exec() bm_register_write() opens an executable file using open_exec(), which internally calls do_open_execat() and denies write access on the file to avoid modification while it is being exe
osv
CVE-2025-68307UNKNOWN≥ 0, < 6.1.159-1≥ 0, < 6.12.63-1+1 more2025-12-16
CVE-2025-68307 CVE-2025-68307: In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs The d In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs The driver lacks the cleanup of failed transfers of URBs. This reduces the number of available URBs per error by 1. This leads to reduced performance and ultimately to a com
osv
CVE-2025-68286UNKNOWN≥ 4.15.0, < 5.10.247≥ 5.11.0, < 5.15.197+4 more2025-12-16
CVE-2025-68286 drm/amd/display: Check NULL before accessing drm/amd/display: Check NULL before accessing In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check NULL before accessing [WHAT] IGT kms_cursor_legacy's long-nonblocking-modeset-vs-cursor-atomic fails with NULL pointer dereference. This can be reproduced with both an eDP panel and a DP monitors connected. BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access i
osv
CVE-2025-68315UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.8-12025-12-16
CVE-2025-68315 CVE-2025-68315: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to detect potential corrupted nid in free_nid_list As reported, on-disk In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to detect potential corrupted nid in free_nid_list As reported, on-disk footer.ino and footer.nid is the same and out-of-range, let's add sanity check on f2fs_alloc_nid() to detect any potential corruption in free_nid_list.
osv
CVE-2025-68292UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.11-12025-12-16
CVE-2025-68292 CVE-2025-68292: In the Linux kernel, the following vulnerability has been resolved: mm/memfd: fix information leak in hugetlb folios When allocating hugetlb folios fo In the Linux kernel, the following vulnerability has been resolved: mm/memfd: fix information leak in hugetlb folios When allocating hugetlb folios for memfd, three initialization steps are missing: 1. Folios are not zeroed, leading to kernel memory disclosure to userspace 2. Folios are not marked uptodate before add
osv
CVE-2025-40350UNKNOWN≥ 0, < 6.12.57-1≥ 0, < 6.17.6-12025-12-16
CVE-2025-40350 CVE-2025-40350: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ XDP pro In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ XDP programs can change the layout of an xdp_buff through bpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver cannot assume the size of the linear data area
osv
CVE-2025-68262UNKNOWN≥ 6.17.0, < 6.17.12≥ 6.18.0, < 6.18.12025-12-16
CVE-2025-68262 crypto: zstd - fix double-free in per-CPU stream cleanup crypto: zstd - fix double-free in per-CPU stream cleanup In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstd_streams (per-CPU contexts) are freed in zstd_exit() during every tfm destruction, rather than being managed at
osv
CVE-2025-68243UNKNOWN≥ 6.17.0, < 6.17.92025-12-16
CVE-2025-68243 NFS: Check the TLS certificate fields in nfs_match_client() NFS: Check the TLS certificate fields in nfs_match_client() In the Linux kernel, the following vulnerability has been resolved: NFS: Check the TLS certificate fields in nfs_match_client() If the TLS security policy is of type RPC_XPRTSEC_TLS_X509, then the cert_serial and privkey_serial fields need to match as well since they define the client's identity, as presented to the server.
osv
CVE-2025-68222UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.10-12025-12-16
CVE-2025-68222 CVE-2025-68222: In the Linux kernel, the following vulnerability has been resolved: pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc s32_pinctrl_desc is a In the Linux kernel, the following vulnerability has been resolved: pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc s32_pinctrl_desc is allocated with devm_kmalloc(), but not all of its fields are initialized. Notably, num_custom_params is used in pinconf_generic_parse_dt_config(), resulting in intermitt
osv
CVE-2025-68185UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.1.159-1+2 more2025-12-16
CVE-2025-68185 CVE-2025-68185: In the Linux kernel, the following vulnerability has been resolved: nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing T In the Linux kernel, the following vulnerability has been resolved: nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing Theoretically it's an oopsable race, but I don't believe one can manage to hit it on real hardware; might become doable on a KVM, but it still won't be easy to attack. A
osv
CVE-2025-68205UNKNOWN≥ 6.17.0, < 6.17.92025-12-16
CVE-2025-68205 ALSA: hda/hdmi: Fix breakage at probing nvhdmi-mcp driver ALSA: hda/hdmi: Fix breakage at probing nvhdmi-mcp driver In the Linux kernel, the following vulnerability has been resolved: ALSA: hda/hdmi: Fix breakage at probing nvhdmi-mcp driver After restructuring and splitting the HDMI codec driver code, each HDMI codec driver contains the own build_controls and build_pcms ops. A copy-n-paste error put the wrong entries for nvhdmi-mcp driver; both build_controls and build_pcms ar
osv
CVE-2025-68255UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2025-12-16
CVE-2025-68255 CVE-2025-68255: In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing The Support In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing The Supported Rates IE length from an incoming Association Request frame was used directly as the memcpy() length when copying into a fixed-size 16-byte stack buffer (supportRate)
osv
CVE-2025-68249UNKNOWN≥ 5.9.0, < 5.10.246≥ 5.11.0, < 5.15.196+4 more2025-12-16
CVE-2025-68249 most: usb: hdm_probe: Fix calling put_device() before device initialization most: usb: hdm_probe: Fix calling put_device() before device initialization In the Linux kernel, the following vulnerability has been resolved: most: usb: hdm_probe: Fix calling put_device() before device initialization The early error path in hdm_probe() can jump to err_free_mdev before &mdev->dev has been initialized with device_initialize(). Calling put_device(&mdev->dev) there triggers a device core
osv
CVE-2025-68224UNKNOWN≥ 0, < 5.10.247-1≥ 0, < 6.17.10-12025-12-16
CVE-2025-68224 CVE-2025-68224: In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix a regression triggered by scsi_host_busy() Commit 995412e23bb2 ("b In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix a regression triggered by scsi_host_busy() Commit 995412e23bb2 ("blk-mq: Replace tags->lock with SRCU for tag iterators") introduced the following regression: Call trace: __srcu_read_lock+0x30/0x80 (P) blk_mq_tagset_busy_iter+0x44/0x3
osv
CVE-2025-68187UNKNOWN≥ 6.17.0, < 6.17.82025-12-16
CVE-2025-68187 net: mdio: Check regmap pointer returned by device_node_to_regmap() net: mdio: Check regmap pointer returned by device_node_to_regmap() In the Linux kernel, the following vulnerability has been resolved: net: mdio: Check regmap pointer returned by device_node_to_regmap() The call to device_node_to_regmap() in airoha_mdio_probe() can return an ERR_PTR() if regmap initialization fails. Currently, the driver stores the pointer without validation, which could lead to a crash if it
osv
CVE-2025-68260UNKNOWN≥ 6.18.0, < 6.18.12025-12-16
CVE-2025-68260 rust_binder: fix race condition on death_list rust_binder: fix race condition on death_list In the Linux kernel, the following vulnerability has been resolved: rust_binder: fix race condition on death_list Rust Binder contains the following unsafe operation: // SAFETY: A `NodeDeath` is never inserted into the death list // of any node other than its owner, so it is either in this // death list or in no death list. unsafe { node_inner.death_list.remove(self) }; This operation
osv
CVE-2025-68305UNKNOWN≥ 0, < 6.12.63-1≥ 0, < 6.17.11-12025-12-16
CVE-2025-68305 CVE-2025-68305: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind There is a po In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in
osv
CVE-2025-68318UNKNOWN≥ 6.11.0, < 6.17.82025-12-16
CVE-2025-68318 clk: thead: th1520-ap: set all AXI clocks to CLK_IS_CRITICAL clk: thead: th1520-ap: set all AXI clocks to CLK_IS_CRITICAL In the Linux kernel, the following vulnerability has been resolved: clk: thead: th1520-ap: set all AXI clocks to CLK_IS_CRITICAL The AXI crossbar of TH1520 has no proper timeout handling, which means gating AXI clocks can easily lead to bus timeout and thus system hang. Set all AXI clock gates to CLK_IS_CRITICAL. All these clock gates are ungated by default
osv