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 59 of 724
CVE-2025-68366UNKNOWN≥ 4.12.0, < 5.10.248≥ 5.11.0, < 5.15.198+5 more2025-12-24
CVE-2025-68366 nbd: defer config unlock in nbd_genl_connect
nbd: defer config unlock in nbd_genl_connect
In the Linux kernel, the following vulnerability has been resolved:
nbd: defer config unlock in nbd_genl_connect
There is one use-after-free warning when running NBD_CMD_CONNECT and
NBD_CLEAR_SOCK:
nbd_genl_connect
nbd_alloc_and_init_config // config_refs=1
nbd_start_device // config_refs=2
set NBD_RT_HAS_CONFIG_REF open nbd // config_refs=3
recv_work done // config_refs=2
NBD_CLEAR_SOCK
osv
CVE-2023-54061UNKNOWN≥ 6.1.0, < 6.3.32025-12-24
CVE-2023-54061 x86: fix clear_user_rep_good() exception handling annotation
x86: fix clear_user_rep_good() exception handling annotation
In the Linux kernel, the following vulnerability has been resolved:
x86: fix clear_user_rep_good() exception handling annotation
This code no longer exists in mainline, because it was removed in
commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory
clearing") upstream.
However, rather than backport the full range of x86 memory clearing and
c
osv
CVE-2023-54048UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-12-24
CVE-2023-54048 CVE-2023-54048: In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Prevent handling any completions after qp destroy HW may generate co
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Prevent handling any completions after qp destroy HW may generate completions that indicates QP is destroyed. Driver should not be scheduling any more completion handlers for this QP, after the QP is destroyed. Since CQs are active duri
osv
CVE-2023-54143UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.3-12025-12-24
CVE-2023-54143 CVE-2023-54143: In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: fix resource leaks in vdec_msg_queue_init() If we encount
In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: fix resource leaks in vdec_msg_queue_init() If we encounter any error in the vdec_msg_queue_init() then we need to set "msg_queue->wdma_addr.size = 0;". Normally, this is done inside the vdec_msg_queue_deinit() function. Howe
osv
CVE-2023-54073UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-24
CVE-2023-54073 CVE-2023-54073: In the Linux kernel, the following vulnerability has been resolved: tpm: Add !tpm_amd_is_rng_defective() to the hwrng_unregister() call site The follo
In the Linux kernel, the following vulnerability has been resolved: tpm: Add !tpm_amd_is_rng_defective() to the hwrng_unregister() call site The following crash was reported: [ 1950.279393] list_del corruption, ffff99560d485790->next is NULL [ 1950.279400] ------------[ cut here ]------------ [ 1950.279401] kernel BU
osv
CVE-2023-54047UNKNOWN≥ 4.9.0, < 6.1.30≥ 6.2.0, < 6.3.42025-12-24
CVE-2023-54047 drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
In the Linux kernel, the following vulnerability has been resolved:
drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
This fixes a use-after-free crash during rmmod.
The DRM encoder is embedded inside the larger rockchip_hdmi,
which is allocated with the component. The component memory
gets freed before the main drm device is destroyed. Fix it
by running enc
osv
CVE-2023-54066UNKNOWN≥ 5.5.0, < 5.10.197≥ 5.11.0, < 5.15.133+2 more2025-12-24
CVE-2023-54066 media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer
media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer
In the Linux kernel, the following vulnerability has been resolved:
media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer
In gl861_i2c_master_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 gl861_i2c_master_xfer. If acc
osv
CVE-2022-50733UNKNOWN≥ 2.6.13, < 4.9.331≥ 4.10.0, < 4.14.296+6 more2025-12-24
CVE-2022-50733 usb: idmouse: fix an uninit-value in idmouse_open
usb: idmouse: fix an uninit-value in idmouse_open
In the Linux kernel, the following vulnerability has been resolved:
usb: idmouse: fix an uninit-value in idmouse_open
In idmouse_create_image, if any ftip_command fails, it will
go to the reset label. However, this leads to the data in
bulk_in_buffer[HEADER..IMGSIZE] uninitialized. And the check
for valid image incurs an uninitialized dereference.
Fix this by moving the check be
osv
CVE-2023-54024UNKNOWN≥ 0, < 5.4.235≥ 5.5.0, < 5.10.173+3 more2025-12-24
CVE-2023-54024 KVM: Destroy target device if coalesced MMIO unregistration fails
KVM: Destroy target device if coalesced MMIO unregistration fails
In the Linux kernel, the following vulnerability has been resolved:
KVM: Destroy target device if coalesced MMIO unregistration fails
Destroy and free the target coalesced MMIO device if unregistering said
device fails. As clearly noted in the code, kvm_io_bus_unregister_dev()
does not destroy the target device.
BUG: memory leak
unreferenced objec
osv
CVE-2025-68346UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2025-12-24
CVE-2025-68346 CVE-2025-68346: In the Linux kernel, the following vulnerability has been resolved: ALSA: dice: fix buffer overflow in detect_stream_formats() The function detect_str
In the Linux kernel, the following vulnerability has been resolved: ALSA: dice: fix buffer overflow in detect_stream_formats() The function detect_stream_formats() reads the stream_count value directly from a FireWire device without validating it. This can lead to out-of-bounds writes when a malicious device provides
osv
CVE-2023-54082UNKNOWN≥ 4.2.0, < 5.10.1922025-12-24
CVE-2023-54082 af_unix: Fix null-ptr-deref in unix_stream_sendpage().
af_unix: Fix null-ptr-deref in unix_stream_sendpage().
In the Linux kernel, the following vulnerability has been resolved:
af_unix: Fix null-ptr-deref in unix_stream_sendpage().
Bing-Jhong Billy Jheng reported null-ptr-deref in unix_stream_sendpage()
with detailed analysis and a nice repro.
unix_stream_sendpage() tries to add data to the last skb in the peer's
recv queue without locking the queue.
If the peer's FD is pass
osv
CVE-2022-50745UNKNOWN≥ 5.10.0, < 5.10.163≥ 5.11.0, < 5.15.87+2 more2025-12-24
CVE-2022-50745 staging: media: tegra-video: fix device_node use after free
staging: media: tegra-video: fix device_node use after free
In the Linux kernel, the following vulnerability has been resolved:
staging: media: tegra-video: fix device_node use after free
At probe time this code path is followed:
* tegra_csi_init
* tegra_csi_channels_alloc
* for_each_child_of_node(node, channel) -- iterates over channels
* automatically gets 'channel'
* tegra_csi_channel_alloc()
* saves into chan->of_
osv
CVE-2022-50739UNKNOWN≥ 0, < 6.1.4-12025-12-24
CVE-2022-50739 CVE-2022-50739: In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Add null pointer check for inode operations This adds a sanity check for
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Add null pointer check for inode operations This adds a sanity check for the i_op pointer of the inode which is returned after reading Root directory MFT record. We should check the i_op is valid before trying to create the root dentry, oth
osv
CVE-2023-54123UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-24
CVE-2023-54123 CVE-2023-54123: In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix memleak for 'conf->bio_split' In the error path of raid10_run(), 'c
In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix memleak for 'conf->bio_split' In the error path of raid10_run(), 'conf' need be freed, however, 'conf->bio_split' is missed and memory will be leaked. Since there are 3 places to free 'conf', factor out a helper to fix the problem.
osv
CVE-2022-50783UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50783 CVE-2022-50783: In the Linux kernel, the following vulnerability has been resolved: mptcp: use proper req destructor for IPv6 Before, only the destructor from TCP req
In the Linux kernel, the following vulnerability has been resolved: mptcp: use proper req destructor for IPv6 Before, only the destructor from TCP request sock in IPv4 was called even if the subflow was IPv6. It is important to use the right destructor to avoid memory leaks with some advanced IPv6 features, e.g. when
osv
CVE-2025-68357UNKNOWN≥ 6.6.120, < 6.6.130≥ 6.12.63, < 6.12.642025-12-24
CVE-2025-68357 iomap: allocate s_dio_done_wq for async reads as well
iomap: allocate s_dio_done_wq for async reads as well
In the Linux kernel, the following vulnerability has been resolved:
iomap: allocate s_dio_done_wq for async reads as well
Since commit 222f2c7c6d14 ("iomap: always run error completions in user
context"), read error completions are deferred to s_dio_done_wq. This
means the workqueue also needs to be allocated for async reads.
osv
CVE-2023-54077UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-24
CVE-2023-54077 CVE-2023-54077: In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix memory leak if ntfs_read_mft failed Label ATTR_ROOT in ntfs_read_mft
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix memory leak if ntfs_read_mft failed Label ATTR_ROOT in ntfs_read_mft() sets is_root = true and ni->ni_flags |= NI_FLAG_DIR, then next attr will goto label ATTR_ALLOC and alloc ni->dir.alloc_run. However two states are not always consist
osv
CVE-2022-50715UNKNOWN≥ 0, < 4.9.337≥ 4.10.0, < 4.14.303+6 more2025-12-24
CVE-2022-50715 md/raid1: stop mdx_raid1 thread when raid1 array run failed
md/raid1: stop mdx_raid1 thread when raid1 array run failed
In the Linux kernel, the following vulnerability has been resolved:
md/raid1: stop mdx_raid1 thread when raid1 array run failed
fail run raid1 array when we assemble array with the inactive disk only,
but the mdx_raid1 thread were not stop, Even if the associated resources
have been released. it will caused a NULL dereference when we do poweroff.
This causes
osv
CVE-2025-68734UNKNOWN≥ 2.6.29, < 5.4.302≥ 5.5.0, < 5.10.247+5 more2025-12-24
CVE-2025-68734 isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()
isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()
In the Linux kernel, the following vulnerability has been resolved:
isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()
In hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when
setup_instance() fails with an error code. Fix that by freeing the urb
before freeing the hw structure. Also change the error paths to use the
goto ladder style.
Compile t
osv
CVE-2023-54069UNKNOWN≥ 0, < 5.10.205-1≥ 0, < 6.1.64-1+1 more2025-12-24
CVE-2023-54069 CVE-2023-54069: In the Linux kernel, the following vulnerability has been resolved: ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow When we calculate the end
In the Linux kernel, the following vulnerability has been resolved: ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow When we calculate the end position of ext4_free_extent, this position may be exactly where ext4_lblk_t (i.e. uint) overflows. For example, if ac_g_ex.fe_logical is 4294965248 and ac_orig_goal_len
osv