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 48 of 724
CVE-2022-50886UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-30
CVE-2022-50886 CVE-2022-50886: In the Linux kernel, the following vulnerability has been resolved: mmc: toshsd: fix return value check of mmc_add_host() mmc_add_host() may return er In the Linux kernel, the following vulnerability has been resolved: mmc: toshsd: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, the memory that allocated in mmc_alloc_host() will be leaked and it will lead a kernel crash because of deleting not added device in
osv
CVE-2023-54258UNKNOWN≥ 0, < 6.4.13-12025-12-30
CVE-2023-54258 CVE-2023-54258: In the Linux kernel, the following vulnerability has been resolved: cifs: fix potential oops in cifs_oplock_break With deferred close we can have clos In the Linux kernel, the following vulnerability has been resolved: cifs: fix potential oops in cifs_oplock_break With deferred close we can have closes that race with lease breaks, and so with the current checks for whether to send the lease response, oplock_response(), this can mean that an unmount (kill_sb) can oc
osv
CVE-2022-50845UNKNOWN≥ 4.13.0, < 4.14.303≥ 4.15.0, < 4.19.270+5 more2025-12-30
CVE-2022-50845 ext4: fix inode leak in ext4_xattr_inode_create() on an error path ext4: fix inode leak in ext4_xattr_inode_create() on an error path In the Linux kernel, the following vulnerability has been resolved: ext4: fix inode leak in ext4_xattr_inode_create() on an error path There is issue as follows when do setxattr with inject fault: [localhost]# fsck.ext4 -fn /dev/sda e2fsck 1.46.6-rc1 (12-Sep-2022) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pa
osv
CVE-2023-54293UNKNOWN≥ 5.7.0, < 5.10.188≥ 5.11.0, < 5.15.121+2 more2025-12-30
CVE-2023-54293 bcache: fixup btree_cache_wait list damage bcache: fixup btree_cache_wait list damage In the Linux kernel, the following vulnerability has been resolved: bcache: fixup btree_cache_wait list damage We get a kernel crash about "list_add corruption. next->prev should be prev (ffff9c801bc01210), but was ffff9c77b688237c. (next=ffffae586d8afe68)." crash> struct list_head 0xffff9c801bc01210 struct list_head { next = 0xffffae586d8afe68, prev = 0xffffae586d8afe68 } crash> struct list_
osv
CVE-2023-54173UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-30
CVE-2023-54173 CVE-2023-54173: In the Linux kernel, the following vulnerability has been resolved: bpf: Disable preemption in bpf_event_output We received report [1] of kernel crash In the Linux kernel, the following vulnerability has been resolved: bpf: Disable preemption in bpf_event_output We received report [1] of kernel crash, which is caused by using nesting protection without disabled preemption. The bpf_event_output can be called by programs executed by bpf_prog_run_array_cg function tha
osv
CVE-2023-54309UNKNOWN≥ 4.8.0, < 4.14.322≥ 4.15.0, < 4.19.291+5 more2025-12-30
CVE-2023-54309 tpm: tpm_vtpm_proxy: fix a race condition in /dev/vtpmx creation tpm: tpm_vtpm_proxy: fix a race condition in /dev/vtpmx creation In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_vtpm_proxy: fix a race condition in /dev/vtpmx creation /dev/vtpmx is made visible before 'workqueue' is initialized, which can lead to a memory corruption in the worst case scenario. Address this by initializing 'workqueue' as the very first step of the driver initializati
osv
CVE-2022-50855UNKNOWN≥ 6.0.0, < 6.0.16≥ 6.1.0, < 6.1.22025-12-30
CVE-2022-50855 bpf: prevent leak of lsm program after failed attach bpf: prevent leak of lsm program after failed attach In the Linux kernel, the following vulnerability has been resolved: bpf: prevent leak of lsm program after failed attach In [0], we added the ability to bpf_prog_attach LSM programs to cgroups, but in our validation to make sure the prog is meant to be attached to BPF_LSM_CGROUP, we return too early if the check fails. This results in lack of decrementing prog's refcnt (thr
osv
CVE-2022-50854UNKNOWN≥ 0, < 6.0.7-12025-12-30
CVE-2022-50854 CVE-2022-50854: In the Linux kernel, the following vulnerability has been resolved: nfc: virtual_ncidev: Fix memory leak in virtual_nci_send() skb should be free in v In the Linux kernel, the following vulnerability has been resolved: nfc: virtual_ncidev: Fix memory leak in virtual_nci_send() skb should be free in virtual_nci_send(), otherwise kmemleak will report memleak. Steps for reproduction (simulated in qemu): cd tools/testing/selftests/nci make ./nci_dev BUG: memory leak un
osv
CVE-2022-50823UNKNOWN≥ 3.10.0, < 4.9.331≥ 4.10.0, < 4.14.296+6 more2025-12-30
CVE-2022-50823 clk: tegra: Fix refcount leak in tegra114_clock_init clk: tegra: Fix refcount leak in tegra114_clock_init In the Linux kernel, the following vulnerability has been resolved: clk: tegra: Fix refcount leak in tegra114_clock_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.
osv
CVE-2022-50884UNKNOWN≥ 2.6.16, < 4.9.331≥ 4.10.0, < 4.14.296+6 more2025-12-30
CVE-2022-50884 drm: Prevent drm_copy_field() to attempt copying a NULL pointer drm: Prevent drm_copy_field() to attempt copying a NULL pointer In the Linux kernel, the following vulnerability has been resolved: drm: Prevent drm_copy_field() to attempt copying a NULL pointer There are some struct drm_driver fields that are required by drivers since drm_copy_field() attempts to copy them to user-space via DRM_IOCTL_VERSION. But it can be possible that a driver has a bug and did not set some of
osv
CVE-2023-54232UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.25-12025-12-30
CVE-2023-54232 CVE-2023-54232: In the Linux kernel, the following vulnerability has been resolved: m68k: Only force 030 bus error if PC not in exception table __get_kernel_nofault() In the Linux kernel, the following vulnerability has been resolved: m68k: Only force 030 bus error if PC not in exception table __get_kernel_nofault() does copy data in supervisor mode when forcing a task backtrace log through /proc/sysrq_trigger. This is expected cause a bus error exception on e.g. NULL pointer dere
osv
CVE-2023-54208UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-12-30
CVE-2023-54208 CVE-2023-54208: In the Linux kernel, the following vulnerability has been resolved: media: ov5675: Fix memleak in ov5675_init_controls() There is a kmemleak when test In the Linux kernel, the following vulnerability has been resolved: media: ov5675: Fix memleak in ov5675_init_controls() There is a kmemleak when testing the media/i2c/ov5675.c with bpf mock device: AssertionError: unreferenced object 0xffff888107362160 (size 16): comm "python3", pid 277, jiffies 4294832798 (age 20.7
osv
CVE-2023-54226UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-30
CVE-2023-54226 CVE-2023-54226: In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix data races around sk->sk_shutdown In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix data races around sk->sk_shutdown. KCSAN found a data race around sk->sk_shutdown where unix_release_sock() and unix_shutdown() update it under unix_state_lock(), OTOH unix_poll() and unix_dgram_poll() read it locklessly. We need to annotate the writes and reads with WRITE
osv
CVE-2022-50819UNKNOWN≥ 5.6.0, < 5.10.150≥ 5.11.0, < 5.15.75+2 more2025-12-30
CVE-2022-50819 udmabuf: Set ubuf->sg = NULL if the creation of sg table fails udmabuf: Set ubuf->sg = NULL if the creation of sg table fails In the Linux kernel, the following vulnerability has been resolved: udmabuf: Set ubuf->sg = NULL if the creation of sg table fails When userspace tries to map the dmabuf and if for some reason (e.g. OOM) the creation of the sg table fails, ubuf->sg needs to be set to NULL. Otherwise, when the userspace subsequently closes the dmabuf fd, we'd try to erron
osv
CVE-2022-50812UNKNOWN≥ 0, < 6.1.4-12025-12-30
CVE-2022-50812 CVE-2022-50812: In the Linux kernel, the following vulnerability has been resolved: security: Restrict CONFIG_ZERO_CALL_USED_REGS to gcc or clang > 15 In the Linux kernel, the following vulnerability has been resolved: security: Restrict CONFIG_ZERO_CALL_USED_REGS to gcc or clang > 15.0.6 A bad bug in clang's implementation of -fzero-call-used-regs can result in NULL pointer dereferences (see the links above the check for more information). Restrict CONFIG_CC_HAS_ZERO_CALL_USED_RE
osv
CVE-2023-54314UNKNOWN≥ 2.6.23, < 4.14.326≥ 4.15.0, < 4.19.295+5 more2025-12-30
CVE-2023-54314 media: af9005: Fix null-ptr-deref in af9005_i2c_xfer media: af9005: Fix null-ptr-deref in af9005_i2c_xfer In the Linux kernel, the following vulnerability has been resolved: media: af9005: Fix null-ptr-deref in af9005_i2c_xfer In af9005_i2c_xfer, msg is controlled by user. When msg[i].buf is null and msg[i].len is zero, former checks on msg[i].buf would be passed. Malicious data finally reach af9005_i2c_xfer. If accessing msg[i].buf[0] without sanity check, null ptr deref would
osv
CVE-2023-54320UNKNOWN≥ 6.3.0, < 6.3.42025-12-30
CVE-2023-54320 platform/x86/amd: pmc: Fix memory leak in amd_pmc_stb_debugfs_open_v2() platform/x86/amd: pmc: Fix memory leak in amd_pmc_stb_debugfs_open_v2() In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd: pmc: Fix memory leak in amd_pmc_stb_debugfs_open_v2() Function amd_pmc_stb_debugfs_open_v2() may be called when the STB debug mechanism enabled. When amd_pmc_send_cmd() fails, the 'buf' needs to be released.
osv
CVE-2023-54229UNKNOWN≥ 5.9.0, < 5.10.188≥ 5.11.0, < 5.15.150+2 more2025-12-30
CVE-2023-54229 wifi: ath11k: fix registration of 6Ghz-only phy without the full channel range wifi: ath11k: fix registration of 6Ghz-only phy without the full channel range In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix registration of 6Ghz-only phy without the full channel range Because of what seems to be a typo, a 6Ghz-only phy for which the BDF does not allow the 7115Mhz channel will fail to register: WARNING: CPU: 2 PID: 106 at net/wireless/core.c:
osv
CVE-2023-54245UNKNOWN≥ 0, < 6.1.25-12025-12-30
CVE-2023-54245 CVE-2023-54245: In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds When we run syzkaller we In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds When we run syzkaller we get below Out of Bound. "KASAN: slab-out-of-bounds Read in regcache_flat_read" Below is the backtrace of the issue: dump_backtrace+0x0/0x4c8 show_stack+0x34/0x44 dump_
osv
CVE-2023-54313UNKNOWN≥ 5.15.0, < 5.15.121≥ 5.16.0, < 6.1.40+1 more2025-12-30
CVE-2023-54313 ovl: fix null pointer dereference in ovl_get_acl_rcu() ovl: fix null pointer dereference in ovl_get_acl_rcu() In the Linux kernel, the following vulnerability has been resolved: ovl: fix null pointer dereference in ovl_get_acl_rcu() Following process: P1 P2 path_openat link_path_walk may_lookup inode_permission(rcu) ovl_permission acl_permission_check check_acl get_cached_acl_rcu ovl_get_inode_acl realinode = ovl_inode_real(ovl_inode) drop_cache __dentry_kill(ovl_dentry) iput(o
osv