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 51 of 724
CVE-2025-68368UNKNOWN≥ 0, < 6.18.3-12025-12-24
CVE-2025-68368 CVE-2025-68368: In the Linux kernel, the following vulnerability has been resolved: md: init bioset in mddev_init IO operations may be needed before md_run(), such as
In the Linux kernel, the following vulnerability has been resolved: md: init bioset in mddev_init IO operations may be needed before md_run(), such as updating metadata after writing sysfs. Without bioset, this triggers a NULL pointer dereference as below: BUG: kernel NULL pointer dereference, address: 00000000000000
osv
CVE-2023-54030UNKNOWN≥ 0, < 6.5.3-12025-12-24
CVE-2023-54030 CVE-2023-54030: In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't overflow multishot recv Don't allow overflowing multishot recv
In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't overflow multishot recv Don't allow overflowing multishot recv CQEs, it might get out of hand, hurt performance, and in the worst case scenario OOM the task.
osv
CVE-2023-54055UNKNOWN≥ 5.14.0, < 5.15.108≥ 5.16.0, < 6.1.25+1 more2025-12-24
CVE-2023-54055 RDMA/irdma: Fix memory leak of PBLE objects
RDMA/irdma: Fix memory leak of PBLE objects
In the Linux kernel, the following vulnerability has been resolved:
RDMA/irdma: Fix memory leak of PBLE objects
On rmmod of irdma, the PBLE object memory is not being freed. PBLE object
memory are not statically pre-allocated at function initialization time
unlike other HMC objects. PBLEs objects and the Segment Descriptors (SD)
for it can be dynamically allocated during scale up and SD's re
osv
CVE-2023-54096UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-24
CVE-2023-54096 CVE-2023-54096: In the Linux kernel, the following vulnerability has been resolved: soundwire: fix enumeration completion The soundwire subsystem uses two completion
In the Linux kernel, the following vulnerability has been resolved: soundwire: fix enumeration completion The soundwire subsystem uses two completion structures that allow drivers to wait for soundwire device to become enumerated on the bus and initialised by their drivers, respectively. The code implementing the sign
osv
CVE-2025-68359UNKNOWN≥ 0, < 6.17.13-12025-12-24
CVE-2025-68359 CVE-2025-68359: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double free of qgroup record after failure to add delayed ref head In t
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double free of qgroup record after failure to add delayed ref head In the previous code it was possible to incur into a double kfree() scenario when calling add_delayed_ref_head(). This could happen if the record was reported to already ex
osv
CVE-2023-54105UNKNOWN≥ 5.10.0, < 5.10.200≥ 5.11.0, < 5.15.138+2 more2025-12-24
CVE-2023-54105 can: isotp: check CAN address family in isotp_bind()
can: isotp: check CAN address family in isotp_bind()
In the Linux kernel, the following vulnerability has been resolved:
can: isotp: check CAN address family in isotp_bind()
Add missing check to block non-AF_CAN binds.
Syzbot created some code which matched the right sockaddr struct size
but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family
field:
bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10
osv
CVE-2023-54144UNKNOWN≥ 0, < 6.1.7-12025-12-24
CVE-2023-54144 CVE-2023-54144: In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix kernel warning during topology setup This patch fixes the followin
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix kernel warning during topology setup This patch fixes the following kernel warning seen during driver load by correctly initializing the p2plink attr before creating the sysfs file: [ +0.002865] ------------[ cut here ]------------ [
osv
CVE-2025-68362UNKNOWN≥ 2.6.27, < 5.10.248≥ 5.11.0, < 5.15.198+5 more2025-12-24
CVE-2025-68362 wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()
wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()
In the Linux kernel, the following vulnerability has been resolved:
wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()
The rtl8187_rx_cb() calculates the rx descriptor header address
by subtracting its size from the skb tail pointer.
However, it does not validate if the received packet
(skb->len from urb->actu
osv
CVE-2023-54046UNKNOWN≥ 5.4.0, < 5.4.235≥ 5.5.0, < 5.10.173+3 more2025-12-24
CVE-2023-54046 crypto: essiv - Handle EBUSY correctly
crypto: essiv - Handle EBUSY correctly
In the Linux kernel, the following vulnerability has been resolved:
crypto: essiv - Handle EBUSY correctly
As it is essiv only handles the special return value of EINPROGERSS,
which means that in all other cases it will free data related to the
request.
However, as the caller of essiv may specify MAY_BACKLOG, we also need
to expect EBUSY and treat it in the same way. Otherwise backlogged
requests wil
osv
CVE-2023-54127UNKNOWN≥ 0, < 5.10.197-1≥ 0, < 6.1.55-1+1 more2025-12-24
CVE-2023-54127 CVE-2023-54127: In the Linux kernel, the following vulnerability has been resolved: fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount() Syzkaller re
In the Linux kernel, the following vulnerability has been resolved: fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount() Syzkaller reported the following issue: ================================================================== BUG: KASAN: double-free in slab_free mm/slub.c:3787 [inline] BUG: KASAN:
osv
CVE-2023-54008UNKNOWN≥ 0, < 6.5.3-12025-12-24
CVE-2023-54008 CVE-2023-54008: In the Linux kernel, the following vulnerability has been resolved: virtio_vdpa: build affinity masks conditionally We try to build affinity mask via
In the Linux kernel, the following vulnerability has been resolved: virtio_vdpa: build affinity masks conditionally We try to build affinity mask via create_affinity_masks() unconditionally which may lead several issues: - the affinity mask is not used for parent without affinity support (only VDUSE support the affini
osv
CVE-2023-54021UNKNOWN≥ 2.6.25, < 4.14.316≥ 4.15.0, < 4.19.284+5 more2025-12-24
CVE-2023-54021 ext4: set goal start correctly in ext4_mb_normalize_request
ext4: set goal start correctly in ext4_mb_normalize_request
In the Linux kernel, the following vulnerability has been resolved:
ext4: set goal start correctly in ext4_mb_normalize_request
We need to set ac_g_ex to notify the goal start used in
ext4_mb_find_by_goal. Set ac_g_ex instead of ac_f_ex in
ext4_mb_normalize_request.
Besides we should assure goal start is in range [first_data_block,
blocks_count) as ext4_mb_ini
osv
CVE-2022-50742UNKNOWN≥ 5.2.0, < 5.4.220≥ 5.5.0, < 5.10.150+3 more2025-12-24
CVE-2022-50742 misc: ocxl: fix possible refcount leak in afu_ioctl()
misc: ocxl: fix possible refcount leak in afu_ioctl()
In the Linux kernel, the following vulnerability has been resolved:
misc: ocxl: fix possible refcount leak in afu_ioctl()
eventfd_ctx_put need to be called to put the refcount that gotten by
eventfd_ctx_fdget when ocxl_irq_set_handler fails.
osv
CVE-2022-50719UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50719 CVE-2022-50719: In the Linux kernel, the following vulnerability has been resolved: ALSA: line6: fix stack overflow in line6_midi_transmit Correctly calculate availab
In the Linux kernel, the following vulnerability has been resolved: ALSA: line6: fix stack overflow in line6_midi_transmit Correctly calculate available space including the size of the chunk buffer. This fixes a buffer overflow when multiple MIDI sysex messages are sent to a PODxt device.
osv
CVE-2022-50756UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50756 CVE-2022-50756: In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix mempool alloc size Convert the max size to bytes to match the units
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix mempool alloc size Convert the max size to bytes to match the units of the divisor that calculates the worst-case number of PRP entries. The result is used to determine how many PRP Lists are required. The code was previously rounding th
osv
CVE-2023-54011UNKNOWN≥ 0, < 6.1.20-12025-12-24
CVE-2023-54011 CVE-2023-54011: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix an issue found by KASAN Write only correct size (32 instead of 6
In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix an issue found by KASAN Write only correct size (32 instead of 64 bytes).
osv
CVE-2022-50755UNKNOWN≥ 4.2.0, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-12-24
CVE-2022-50755 udf: Avoid double brelse() in udf_rename()
udf: Avoid double brelse() in udf_rename()
In the Linux kernel, the following vulnerability has been resolved:
udf: Avoid double brelse() in udf_rename()
syzbot reported a warning like below [1]:
VFS: brelse: Trying to free free buffer
WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0
...
Call Trace:
invalidate_bh_lru+0x99/0x150
smp_call_function_many_cond+0xe2a/0x10c0
? generic_remap_file_range_prep+0x50/0x50
? __brel
osv
CVE-2022-50731UNKNOWN≥ 5.2.0, < 5.4.220≥ 5.5.0, < 5.10.150+3 more2025-12-24
CVE-2022-50731 crypto: akcipher - default implementation for setting a private key
crypto: akcipher - default implementation for setting a private key
In the Linux kernel, the following vulnerability has been resolved:
crypto: akcipher - default implementation for setting a private key
Changes from v1:
* removed the default implementation from set_pub_key: it is assumed that
an implementation must always have this callback defined as there are
no use case for an algorithm, which doesn't need
osv
CVE-2023-54033UNKNOWN≥ 5.11.0, < 5.15.115≥ 5.16.0, < 6.1.31+1 more2025-12-24
CVE-2023-54033 bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCPU maps allocate a new element on update before locking the
target hash table bucket. Right after that the maps try to lock the bucket.
If this fails, then maps return -EBUSY to the caller without releasing the
alloca
osv
CVE-2022-50766UNKNOWN≥ 0, < 6.0.3-12025-12-24
CVE-2022-50766 CVE-2022-50766: In the Linux kernel, the following vulnerability has been resolved: btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buff
In the Linux kernel, the following vulnerability has been resolved: btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer syzbot is reporting uninit-value in btrfs_clean_tree_block() [1], for commit bc877d285ca3dba2 ("btrfs: Deduplicate extent_buffer init code") missed that btrfs_set_he
osv