Linux Kernel vulnerabilities

14,742 known vulnerabilities affecting linux/linux_kernel.

Total CVEs
14,742
CISA KEV
29
actively exploited
Public exploits
296
Exploited in wild
31
Severity breakdown
CRITICAL112HIGH3715MEDIUM8619LOW440UNKNOWN1856

Vulnerabilities

Page 117 of 738
CVE-2023-53724UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-10-22
CVE-2023-53724 CVE-2023-53724: In the Linux kernel, the following vulnerability has been resolved: mfd: pcf50633-adc: Fix potential memleak in pcf50633_adc_async_read() `req` is all In the Linux kernel, the following vulnerability has been resolved: mfd: pcf50633-adc: Fix potential memleak in pcf50633_adc_async_read() `req` is allocated in pcf50633_adc_async_read(), but adc_enqueue_request() could fail to insert the `req` into queue. We need to check the return value and free it in the case of f
osv
CVE-2022-50577UNKNOWN≥ 0, < 6.1.4-12025-10-22
CVE-2022-50577 CVE-2022-50577: In the Linux kernel, the following vulnerability has been resolved: ima: Fix memory leak in __ima_inode_hash() Commit f3cc6b25dcc5 ("ima: always measu In the Linux kernel, the following vulnerability has been resolved: ima: Fix memory leak in __ima_inode_hash() Commit f3cc6b25dcc5 ("ima: always measure and audit files in policy") lets measurement or audit happen even if the file digest cannot be calculated. As a result, iint->ima_hash could have been allocated desp
osv
CVE-2022-50562UNKNOWN≥ 4.18.0, < 5.10.163≥ 5.11.0, < 5.15.87+2 more2025-10-22
CVE-2022-50562 tpm: acpi: Call acpi_put_table() to fix memory leak tpm: acpi: Call acpi_put_table() to fix memory leak In the Linux kernel, the following vulnerability has been resolved: tpm: acpi: Call acpi_put_table() to fix memory leak The start and length of the event log area are obtained from TPM2 or TCPA table, so we call acpi_get_table() to get the ACPI information, but the acpi_get_table() should be coupled with acpi_put_table() to release the ACPI memory, add the acpi_put_table() pr
osv
CVE-2022-50574UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-10-22
CVE-2022-50574 CVE-2022-50574: In the Linux kernel, the following vulnerability has been resolved: drm/omap: dss: Fix refcount leak bugs In dss_init_ports() and __dss_uninit_ports() In the Linux kernel, the following vulnerability has been resolved: drm/omap: dss: Fix refcount leak bugs In dss_init_ports() and __dss_uninit_ports(), we should call of_node_put() for the reference returned by of_graph_get_port_by_id() in fail path or when it is not used anymore.
osv
CVE-2023-53702UNKNOWN≥ 5.19.0, < 6.1.30≥ 6.2.0, < 6.3.42025-10-22
CVE-2023-53702 s390/crypto: use vector instructions only if available for ChaCha20 s390/crypto: use vector instructions only if available for ChaCha20 In the Linux kernel, the following vulnerability has been resolved: s390/crypto: use vector instructions only if available for ChaCha20 Commit 349d03ffd5f6 ("crypto: s390 - add crypto library interface for ChaCha20") added a library interface to the s390 specific ChaCha20 implementation. However no check was added to verify if the required faci
osv
CVE-2023-53731UNKNOWN≥ 0, < 4.14.322≥ 4.15.0, < 4.19.291+6 more2025-10-22
CVE-2023-53731 netlink: fix potential deadlock in netlink_set_err() netlink: fix potential deadlock in netlink_set_err() In the Linux kernel, the following vulnerability has been resolved: netlink: fix potential deadlock in netlink_set_err() syzbot reported a possible deadlock in netlink_set_err() [1] A similar issue was fixed in commit 1d482e666b8e ("netlink: disable IRQs for netlink_lock_table()") in netlink_lock_table() This patch adds IRQ safety to netlink_set_err() and __netlink_diag_d
osv
CVE-2023-53725UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-10-22
CVE-2023-53725 CVE-2023-53725: In the Linux kernel, the following vulnerability has been resolved: clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe Smatch reports In the Linux kernel, the following vulnerability has been resolved: clocksource/drivers/cadence-ttc: Fix memory leak in ttc_timer_probe Smatch reports: drivers/clocksource/timer-cadence-ttc.c:529 ttc_timer_probe() warn: 'timer_baseaddr' from of_iomap() not released on lines: 498,508,516. timer_baseaddr may have the p
osv
CVE-2022-50573UNKNOWN≥ 6.2.0, < 6.2.32025-10-22
CVE-2022-50573 wifi: mt76: mt7915: fix mt7915_rate_txpower_get() resource leaks wifi: mt76: mt7915: fix mt7915_rate_txpower_get() resource leaks In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7915: fix mt7915_rate_txpower_get() resource leaks Coverity message: variable "buf" going out of scope leaks the storage. Addresses-Coverity-ID: 1527799 ("Resource leaks")
osv
CVE-2023-53703UNKNOWN≥ 6.0.0, < 6.1.40≥ 6.2.0, < 6.4.52025-10-22
CVE-2023-53703 HID: amd_sfh: Fix for shift-out-of-bounds HID: amd_sfh: Fix for shift-out-of-bounds In the Linux kernel, the following vulnerability has been resolved: HID: amd_sfh: Fix for shift-out-of-bounds Shift operation of 'exp' and 'shift' variables exceeds the maximum number of shift values in the u32 range leading to UBSAN shift-out-of-bounds. ... [ 6.120512] UBSAN: shift-out-of-bounds in drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50 [ 6.120598] shift exponent 104 is too large
osv
CVE-2023-53712UNKNOWN≥ 2.6.38, < 5.15.133≥ 5.16.0, < 6.1.55+1 more2025-10-22
CVE-2023-53712 ARM: 9317/1: kexec: Make smp stop calls asynchronous ARM: 9317/1: kexec: Make smp stop calls asynchronous In the Linux kernel, the following vulnerability has been resolved: ARM: 9317/1: kexec: Make smp stop calls asynchronous If a panic is triggered by a hrtimer interrupt all online cpus will be notified and set offline. But as highlighted by commit 19dbdcb8039c ("smp: Warn on function calls from softirq context") this call should not be made synchronous with disabled interrup
osv
CVE-2022-50565UNKNOWN≥ 5.19.0, < 6.0.16≥ 6.1.0, < 6.1.22025-10-22
CVE-2022-50565 wifi: plfxlc: fix potential memory leak in __lf_x_usb_enable_rx() wifi: plfxlc: fix potential memory leak in __lf_x_usb_enable_rx() In the Linux kernel, the following vulnerability has been resolved: wifi: plfxlc: fix potential memory leak in __lf_x_usb_enable_rx() urbs does not be freed in exception paths in __lf_x_usb_enable_rx(). That will trigger memory leak. To fix it, add kfree() for urbs within "error" label. Compile tested only.
osv
CVE-2023-53701UNKNOWN≥ 0, < 4.14.3152025-10-22
CVE-2023-53701 netfilter: nf_tables: deactivate anonymous set from preparation phase netfilter: nf_tables: deactivate anonymous set from preparation phase In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: deactivate anonymous set from preparation phase [ backport for 4.14 of c1592a89942e9678f7d9c8030efa777c0d57edab ] Toggle deleted anonymous sets as inactive in the next generation, so users cannot perform any update on it. Clear the generation bitmask
osv
CVE-2023-53719UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-10-22
CVE-2023-53719 CVE-2023-53719: In the Linux kernel, the following vulnerability has been resolved: serial: arc_uart: fix of_iomap leak in `arc_serial_probe` Smatch reports: drivers/ In the Linux kernel, the following vulnerability has been resolved: serial: arc_uart: fix of_iomap leak in `arc_serial_probe` Smatch reports: drivers/tty/serial/arc_uart.c:631 arc_serial_probe() warn: 'port->membase' from of_iomap() not released on lines: 631. In arc_serial_probe(), if uart_add_one_port() fails, port
osv
CVE-2022-50571UNKNOWN≥ 0, < 6.1.4-12025-10-22
CVE-2022-50571 CVE-2022-50571: In the Linux kernel, the following vulnerability has been resolved: btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure Now that In the Linux kernel, the following vulnerability has been resolved: btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure Now that lockdep is staying enabled through our entire CI runs I started seeing the following stack in generic/475 ------------[ cut here ]------------ WARNING: CPU: 1 PID: 21718
osv
CVE-2023-53694UNKNOWN≥ 0, < 6.1.25-12025-10-22
CVE-2023-53694 CVE-2023-53694: In the Linux kernel, the following vulnerability has been resolved: riscv: ftrace: Fixup panic by disabling preemption In RISCV, we must use an AUIPC In the Linux kernel, the following vulnerability has been resolved: riscv: ftrace: Fixup panic by disabling preemption In RISCV, we must use an AUIPC + JALR pair to encode an immediate, forming a jump that jumps to an address over 4K. This may cause errors if we want to enable kernel preemption and remove dependency f
osv
CVE-2023-53720UNKNOWN≥ 6.3.0, < 6.3.22025-10-22
CVE-2023-53720 net/mlx5e: Release the label when replacing existing ct entry net/mlx5e: Release the label when replacing existing ct entry In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Release the label when replacing existing ct entry Cited commit doesn't release the label mapping when replacing existing ct entry which leads to following memleak report: unreferenced object 0xffff8881854cf280 (size 96): comm "kworker/u48:74", pid 23093, jiffies 4296664564 (ag
osv
CVE-2023-53721UNKNOWN≥ 6.3.0, < 6.5.52025-10-22
CVE-2023-53721 wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan() wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan() In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan() In ath12k_mac_op_hw_scan(), the return value of kzalloc() is directly used in memcpy(), which may lead to a NULL pointer dereference on failure of kzalloc(). Fix this bug by adding a check of arg.e
osv
CVE-2023-53713UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.4-12025-10-22
CVE-2023-53713 CVE-2023-53713: In the Linux kernel, the following vulnerability has been resolved: arm64: sme: Use STR P to clear FFR context field in streaming SVE mode The FFR is In the Linux kernel, the following vulnerability has been resolved: arm64: sme: Use STR P to clear FFR context field in streaming SVE mode The FFR is a predicate register which can vary between 16 and 256 bits in size depending upon the configured vector length. When saving the SVE state in streaming SVE mode, the FFR
osv
CVE-2025-40005MEDIUMCVSS 5.5≥ 5.9, < 6.6.125≥ 6.7, < 6.16.10+1 more2025-10-20
CVE-2025-40005 [MEDIUM] CVE-2025-40005: In the Linux kernel, the following vulnerability has been resolved: spi: cadence-quadspi: Implement In the Linux kernel, the following vulnerability has been resolved: spi: cadence-quadspi: Implement refcount to handle unbind during busy driver support indirect read and indirect write operation with assumption no force device removal(unbind) operation. However force device removal(removal) is still available to root superuser. Unbinding driver during o
nvdosv
CVE-2025-40015UNKNOWN≥ 0, < 6.16.11-12025-10-20
CVE-2025-40015 CVE-2025-40015: In the Linux kernel, the following vulnerability has been resolved: media: stm32-csi: Fix dereference before NULL check In 'stm32_csi_start', 'csidev- In the Linux kernel, the following vulnerability has been resolved: media: stm32-csi: Fix dereference before NULL check In 'stm32_csi_start', 'csidev->s_subdev' is dereferenced directly while assigning a value to the 'src_pad'. However the same value is being checked against NULL at a later point of time indicating t
osv