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 116 of 738
CVE-2023-53692UNKNOWN≥ 0, < 4.19.271≥ 4.20.0, < 5.4.243+5 more2025-10-22
CVE-2023-53692 ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline
ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline
Syzbot found the following issue:
loop0: detected capacity change from 0 to 2048
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 without journal. Quota mode: none.
BUG: KASA
osv
CVE-2023-53710UNKNOWN≥ 6.0.0, < 6.1.16≥ 6.2.0, < 6.2.32025-10-22
CVE-2023-53710 wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read
wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read
Kernel NULL pointer dereference when ACPI SAR table isn't implemented well.
Fix the error code of return to mark the ACPI SAR table as invalid.
[ 5.077128] mt7921e 0000:06:00.0: sar cnt = 0
[ 5.077381] BUG: kernel NULL
osv
CVE-2023-53728UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.112-1+1 more2025-10-22
CVE-2023-53728 CVE-2023-53728: In the Linux kernel, the following vulnerability has been resolved: posix-timers: Ensure timer ID search-loop limit is valid posix_timer_add() tries t
In the Linux kernel, the following vulnerability has been resolved: posix-timers: Ensure timer ID search-loop limit is valid posix_timer_add() tries to allocate a posix timer ID by starting from the cached ID which was stored by the last successful allocation. This is done in a loop searching the ID space for a free
osv
CVE-2023-53704UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-10-22
CVE-2023-53704 CVE-2023-53704: In the Linux kernel, the following vulnerability has been resolved: clk: imx: clk-imx8mp: improve error handling in imx8mp_clocks_probe() Replace of_i
In the Linux kernel, the following vulnerability has been resolved: clk: imx: clk-imx8mp: improve error handling in imx8mp_clocks_probe() Replace of_iomap() and kzalloc() with devm_of_iomap() and devm_kzalloc() which can automatically release the related memory when the device or driver is removed or unloaded to avoi
osv
CVE-2022-50564UNKNOWN≥ 2.6.32, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-10-22
CVE-2022-50564 s390/netiucv: Fix return type of netiucv_tx()
s390/netiucv: Fix return type of netiucv_tx()
In the Linux kernel, the following vulnerability has been resolved:
s390/netiucv: Fix return type of netiucv_tx()
With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
indirect call targets are validated against the expected function
pointer prototype to make sure the call target is valid to help mitigate
ROP attacks. If they are not identical, there is a failure at run ti
osv
CVE-2023-53723UNKNOWN≥ 4.2.0, < 5.4.243≥ 5.5.0, < 5.10.180+4 more2025-10-22
CVE-2023-53723 drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend
drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend
sdma_v4_0_ip is shared on a few asics, but in sdma_v4_0_hw_fini,
driver unconditionally disables ecc_irq which is only enabled on
those asics enabling sdma ecc. This will introduce a warning i
osv
CVE-2022-50575UNKNOWN≥ 4.18.0, < 4.19.270≥ 4.20.0, < 5.4.229+4 more2025-10-22
CVE-2022-50575 xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
In the Linux kernel, the following vulnerability has been resolved:
xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
As 'kdata.num' is user-controlled data, if user tries to allocate
memory larger than(>=) MAX_ORDER, then kcalloc() will fail, it
creates a stack trace and messes up dmesg with a warning.
Call trace:
-> priv
osv
CVE-2022-50582UNKNOWN≥ 5.9.0, < 5.10.150≥ 5.11.0, < 5.15.75+2 more2025-10-22
CVE-2022-50582 regulator: core: Prevent integer underflow
regulator: core: Prevent integer underflow
In the Linux kernel, the following vulnerability has been resolved:
regulator: core: Prevent integer underflow
By using a ratio of delay to poll_enabled_time that is not integer
time_remaining underflows and does not exit the loop as expected.
As delay could be derived from DT and poll_enabled_time is defined
in the driver this can easily happen.
Use a signed iterator to make sure that the lo
osv
CVE-2023-53732UNKNOWN≥ 5.15.0, < 5.15.113≥ 5.16.0, < 6.1.81+1 more2025-10-22
CVE-2023-53732 fs/ntfs3: Fix NULL dereference in ni_write_inode
fs/ntfs3: Fix NULL dereference in ni_write_inode
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Fix NULL dereference in ni_write_inode
Syzbot reports a NULL dereference in ni_write_inode.
When creating a new inode, if allocation fails in mi_init function
(called in mi_format_new function), mi->mrec is set to NULL.
In the error path of this inode creation, mi->mrec is later
dereferenced in ni_write_i
osv
CVE-2023-53708UNKNOWN≥ 5.11.0, < 5.15.133≥ 5.16.0, < 6.1.55+1 more2025-10-22
CVE-2023-53708 ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects
ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects
In the Linux kernel, the following vulnerability has been resolved:
ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects
If a badly constructed firmware includes multiple `ACPI_TYPE_PACKAGE`
objects while evaluating the AMD LPS0 _DSM, there will be a memory
leak. Explicitly guard against this.
osv
CVE-2023-53727UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-10-22
CVE-2023-53727 CVE-2023-53727: In the Linux kernel, the following vulnerability has been resolved: net/sched: fq_pie: avoid stalls in fq_pie_timer() When setting a high number of fl
In the Linux kernel, the following vulnerability has been resolved: net/sched: fq_pie: avoid stalls in fq_pie_timer() When setting a high number of flows (limit being 65536), fq_pie_timer() is currently using too much time as syzbot reported. Add logic to yield the cpu every 2048 flows (less than 150 usec on debug ke
osv
CVE-2023-53707UNKNOWN≥ 4.2.0, < 6.1.47≥ 6.2.0, < 6.4.122025-10-22
CVE-2023-53707 drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1
drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1
The type of size is unsigned int, if size is 0x40000000, there will
be an integer overflow, size will be zero after size *= sizeof(uint32_t),
will cause uninitialized memory to be referenced later.
osv
CVE-2023-53726UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-10-22
CVE-2023-53726 CVE-2023-53726: In the Linux kernel, the following vulnerability has been resolved: arm64: csum: Fix OoB access in IP checksum code for negative lengths Although comm
In the Linux kernel, the following vulnerability has been resolved: arm64: csum: Fix OoB access in IP checksum code for negative lengths Although commit c2c24edb1d9c ("arm64: csum: Fix pathological zero-length calls") added an early return for zero-length input, syzkaller has popped up with an example of a _negative_
osv
CVE-2023-53711UNKNOWN≥ 5.7.0, < 5.10.195≥ 5.11.0, < 5.15.132+2 more2025-10-22
CVE-2023-53711 NFS: Fix a potential data corruption
NFS: Fix a potential data corruption
In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix a potential data corruption
We must ensure that the subrequests are joined back into the head before
we can retransmit a request. If the head was not on the commit lists,
because the server wrote it synchronously, we still need to add it back
to the retransmission list.
Add a call that mirrors the effect of nfs_cancel_remove_inod
osv
CVE-2022-50579UNKNOWN≥ 0, < 5.10.158-1≥ 0, < 6.0.3-12025-10-22
CVE-2022-50579 CVE-2022-50579: In the Linux kernel, the following vulnerability has been resolved: arm64: ftrace: fix module PLTs with mcount Li Huafei reports that mcount-based ftr
In the Linux kernel, the following vulnerability has been resolved: arm64: ftrace: fix module PLTs with mcount Li Huafei reports that mcount-based ftrace with module PLTs was broken by commit: a6253579977e4c6f ("arm64: ftrace: consistently handle PLTs.") When a module PLTs are used and a module is loaded sufficiently
osv
CVE-2023-53729UNKNOWN≥ 4.16.0, < 4.19.295≥ 4.20.0, < 5.4.257+4 more2025-10-22
CVE-2023-53729 soc: qcom: qmi_encdec: Restrict string length in decode
soc: qcom: qmi_encdec: Restrict string length in decode
In the Linux kernel, the following vulnerability has been resolved:
soc: qcom: qmi_encdec: Restrict string length in decode
The QMI TLV value for strings in a lot of qmi element info structures
account for null terminated strings with MAX_LEN + 1. If a string is
actually MAX_LEN + 1 length, this will cause an out of bounds access
when the NULL character is appended in
osv
CVE-2022-50557UNKNOWN≥ 5.17.0, < 6.0.16≥ 6.1.0, < 6.1.22025-10-22
CVE-2022-50557 pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()
pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()
The thunderbay_add_functions() will free memory of thunderbay_funcs
when everything is ok, but thunderbay_funcs will not be freed when
thunderbay_add_functions() fails, then there
osv
CVE-2023-53697UNKNOWN≥ 5.18.0, < 6.1.53≥ 6.2.0, < 6.4.16+1 more2025-10-22
CVE-2023-53697 nvdimm: Fix memleak of pmu attr_groups in unregister_nvdimm_pmu()
nvdimm: Fix memleak of pmu attr_groups in unregister_nvdimm_pmu()
In the Linux kernel, the following vulnerability has been resolved:
nvdimm: Fix memleak of pmu attr_groups in unregister_nvdimm_pmu()
Memory pointed by 'nd_pmu->pmu.attr_groups' is allocated in function
'register_nvdimm_pmu' and is lost after 'kfree(nd_pmu)' call in function
'unregister_nvdimm_pmu'.
osv
CVE-2022-50568UNKNOWN≥ 2.6.35, < 4.19.270≥ 4.20.0, < 5.4.229+4 more2025-10-22
CVE-2022-50568 usb: gadget: f_hid: fix f_hidg lifetime vs cdev
usb: gadget: f_hid: fix f_hidg lifetime vs cdev
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: f_hid: fix f_hidg lifetime vs cdev
The embedded struct cdev does not have its lifetime correctly tied to
the enclosing struct f_hidg, so there is a use-after-free if /dev/hidgN
is held open while the gadget is deleted.
This can readily be replicated with libusbgx's example programs (for
conciseness - op
osv
CVE-2022-50581UNKNOWN≥ 2.6.12, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-10-22
CVE-2022-50581 hfs: fix OOB Read in __hfs_brec_find
hfs: fix OOB Read in __hfs_brec_find
In the Linux kernel, the following vulnerability has been resolved:
hfs: fix OOB Read in __hfs_brec_find
Syzbot reported a OOB read bug:
BUG: KASAN: slab-out-of-bounds in hfs_strcmp+0x117/0x190
fs/hfs/string.c:84
Read of size 1 at addr ffff88807eb62c4e by task kworker/u4:1/11
CPU: 1 PID: 11 Comm: kworker/u4:1 Not tainted
6.1.0-rc6-syzkaller-00308-g644e9524388a #0
Workqueue: writeback wb_workfn (flush-7:0
osv