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 58 of 724
CVE-2023-54132UNKNOWN≥ 4.19.0, < 5.4.243≥ 5.5.0, < 5.10.180+4 more2025-12-24
CVE-2023-54132 erofs: stop parsing non-compact HEAD index if clusterofs is invalid
erofs: stop parsing non-compact HEAD index if clusterofs is invalid
In the Linux kernel, the following vulnerability has been resolved:
erofs: stop parsing non-compact HEAD index if clusterofs is invalid
Syzbot generated a crafted image [1] with a non-compact HEAD index of
clusterofs 33024 while valid numbers should be 0 ~ lclustersize-1,
which causes the following unexpected behavior as below:
BUG: unable to
osv
CVE-2022-50729UNKNOWN≥ 5.15.0, < 5.15.86≥ 5.16.0, < 6.0.16+1 more2025-12-24
CVE-2022-50729 ksmbd: Fix resource leak in ksmbd_session_rpc_open()
ksmbd: Fix resource leak in ksmbd_session_rpc_open()
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: Fix resource leak in ksmbd_session_rpc_open()
When ksmbd_rpc_open() fails then it must call ksmbd_rpc_id_free() to
undo the result of ksmbd_ipc_id_alloc().
osv
CVE-2023-54053UNKNOWN≥ 5.4.0, < 5.4.244≥ 5.5.0, < 5.10.181+3 more2025-12-24
CVE-2023-54053 wifi: iwlwifi: pcie: fix possible NULL pointer dereference
wifi: iwlwifi: pcie: fix possible NULL pointer dereference
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: pcie: fix possible NULL pointer dereference
It is possible that iwl_pci_probe() will fail and free the trans,
then afterwards iwl_pci_remove() will be called and crash by trying
to access trans which is already freed, fix it.
iwlwifi 0000:01:00.0: Detected crf-id 0xa5a5a5a2, cnv-
osv
CVE-2025-68370UNKNOWN≥ 0, < 6.17.13-12025-12-24
CVE-2025-68370 CVE-2025-68370: In the Linux kernel, the following vulnerability has been resolved: coresight: tmc: add the handle of the event to the path The handle is essential fo
In the Linux kernel, the following vulnerability has been resolved: coresight: tmc: add the handle of the event to the path The handle is essential for retrieving the AUX_EVENT of each CPU and is required in perf mode. It has been added to the coresight_path so that dependent devices can access it from the path when
osv
CVE-2023-54057UNKNOWN≥ 4.7.0, < 5.4.237≥ 5.5.0, < 5.10.175+3 more2025-12-24
CVE-2023-54057 iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter
iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter
In the Linux kernel, the following vulnerability has been resolved:
iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter
The 'acpiid' buffer in the parse_ivrs_acpihid function may overflow,
because the string specifier in the format string sscanf()
has no width limitation.
Found by InfoTeCS on be
osv
CVE-2023-54140UNKNOWN≥ 3.10.0, < 4.14.326≥ 4.15.0, < 4.19.295+6 more2025-12-24
CVE-2023-54140 nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
A syzbot stress test using a corrupted disk image reported that
mark_buffer_dirty() called from __nilfs_mark_inode_dirty() or
nilfs_palloc_commit_alloc_entry() may output a kernel warning, and can
pani
osv
CVE-2025-68739UNKNOWN≥ 6.17.0, < 6.17.13≥ 6.18.0, < 6.18.22025-12-24
CVE-2025-68739 PM / devfreq: hisi: Fix potential UAF in OPP handling
PM / devfreq: hisi: Fix potential UAF in OPP handling
In the Linux kernel, the following vulnerability has been resolved:
PM / devfreq: hisi: Fix potential UAF in OPP handling
Ensure all required data is acquired before calling dev_pm_opp_put(opp)
to maintain correct resource acquisition and release order.
osv
CVE-2023-54156UNKNOWN≥ 5.9.0, < 5.10.188≥ 5.11.0, < 5.15.121+3 more2025-12-24
CVE-2023-54156 sfc: fix crash when reading stats while NIC is resetting
sfc: fix crash when reading stats while NIC is resetting
In the Linux kernel, the following vulnerability has been resolved:
sfc: fix crash when reading stats while NIC is resetting
efx_net_stats() (.ndo_get_stats64) can be called during an ethtool
selftest, during which time nic_data->mc_stats is NULL as the NIC has
been fini'd. In this case do not attempt to fetch the latest stats
from the hardware, else we will crash o
osv
CVE-2023-54097UNKNOWN≥ 5.2.0, < 5.4.243≥ 5.5.0, < 5.10.180+4 more2025-12-24
CVE-2023-54097 regulator: stm32-pwr: fix of_iomap leak
regulator: stm32-pwr: fix of_iomap leak
In the Linux kernel, the following vulnerability has been resolved:
regulator: stm32-pwr: fix of_iomap leak
Smatch reports:
drivers/regulator/stm32-pwr.c:166 stm32_pwr_regulator_probe() warn:
'base' from of_iomap() not released on lines: 151,166.
In stm32_pwr_regulator_probe(), base is not released
when devm_kzalloc() fails to allocate memory or
devm_regulator_register() fails to register a new reg
osv
CVE-2023-54052UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.5.3-12025-12-24
CVE-2023-54052 CVE-2023-54052: In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU txs may be dropped if the
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU txs may be dropped if the frame is aggregated in AMSDU. When the problem shows up, some SKBs would be hold in driver to cause network stopped temporarily. Even if the problem can be recovered b
osv
CVE-2023-54099UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-24
CVE-2023-54099 CVE-2023-54099: In the Linux kernel, the following vulnerability has been resolved: fs: Protect reconfiguration of sb read-write from racing writes The reconfigure /
In the Linux kernel, the following vulnerability has been resolved: fs: Protect reconfiguration of sb read-write from racing writes The reconfigure / remount code takes a lot of effort to protect filesystem's reconfiguration code from racing writes on remounting read-only. However during remounting read-only filesyste
osv
CVE-2023-53995UNKNOWN≥ 2.6.15, < 5.4.257≥ 5.5.0, < 5.10.195+3 more2025-12-24
CVE-2023-53995 net: ipv4: fix one memleak in __inet_del_ifa()
net: ipv4: fix one memleak in __inet_del_ifa()
In the Linux kernel, the following vulnerability has been resolved:
net: ipv4: fix one memleak in __inet_del_ifa()
I got the below warning when do fuzzing test:
unregister_netdevice: waiting for bond0 to become free. Usage count = 2
It can be repoduced via:
ip link add bond0 type bond
sysctl -w net.ipv4.conf.bond0.promote_secondaries=1
ip addr add 4.117.174.103/0 scope 0x40 dev bond0
osv
CVE-2023-54074UNKNOWN≥ 5.18.0, < 6.1.31≥ 6.2.0, < 6.3.52025-12-24
CVE-2023-54074 net/mlx5e: Use correct encap attribute during invalidation
net/mlx5e: Use correct encap attribute during invalidation
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Use correct encap attribute during invalidation
With introduction of post action infrastructure most of the users of encap
attribute had been modified in order to obtain the correct attribute by
calling mlx5e_tc_get_encap_attr() helper instead of assuming encap action
is always on def
osv
CVE-2023-54079UNKNOWN≥ 3.3.0, < 4.14.316≥ 4.15.0, < 4.19.284+5 more2025-12-24
CVE-2023-54079 power: supply: bq27xxx: Fix poll_interval handling and races on remove
power: supply: bq27xxx: Fix poll_interval handling and races on remove
In the Linux kernel, the following vulnerability has been resolved:
power: supply: bq27xxx: Fix poll_interval handling and races on remove
Before this patch bq27xxx_battery_teardown() was setting poll_interval = 0
to avoid bq27xxx_battery_update() requeuing the delayed_work item.
There are 2 problems with this:
1. If the driver is unbou
osv
CVE-2023-54110UNKNOWN≥ 2.6.22, < 4.14.303≥ 4.15.0, < 4.19.270+5 more2025-12-24
CVE-2023-54110 usb: rndis_host: Secure rndis_query check against int overflow
usb: rndis_host: Secure rndis_query check against int overflow
In the Linux kernel, the following vulnerability has been resolved:
usb: rndis_host: Secure rndis_query check against int overflow
Variables off and len typed as uint32 in rndis_query function
are controlled by incoming RNDIS response message thus their
value may be manipulated. Setting off to a unexpectetly large
value will cause the sum with len and 8
osv
CVE-2023-54135UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.11-12025-12-24
CVE-2023-54135 CVE-2023-54135: In the Linux kernel, the following vulnerability has been resolved: maple_tree: fix potential out-of-bounds access in mas_wr_end_piv() Check the write
In the Linux kernel, the following vulnerability has been resolved: maple_tree: fix potential out-of-bounds access in mas_wr_end_piv() Check the write offset end bounds before using it as the offset into the pivot array. This avoids a possible out-of-bounds access on the pivot array if the write extends to the last s
osv
CVE-2022-50722UNKNOWN≥ 5.14.0, < 5.15.76≥ 5.16.0, < 6.0.62025-12-24
CVE-2022-50722 media: ipu3-imgu: Fix NULL pointer dereference in active selection access
media: ipu3-imgu: Fix NULL pointer dereference in active selection access
In the Linux kernel, the following vulnerability has been resolved:
media: ipu3-imgu: Fix NULL pointer dereference in active selection access
What the IMGU driver did was that it first acquired the pointers to active
and try V4L2 subdev state, and only then figured out which one to use.
The problem with that approach and a later pa
osv
CVE-2022-50724UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50724 CVE-2022-50724: In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix resource leak in regulator_register() I got some resource lea
In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix resource leak in regulator_register() I got some resource leak reports while doing fault injection test: OF: ERROR: memory leak, expected refcount 1 instead of 100, of_node_get()/of_node_put() unbalanced - destroy cset entry: att
osv
CVE-2022-50765UNKNOWN≥ 5.19.0, < 6.0.18≥ 6.1.0, < 6.1.42025-12-24
CVE-2022-50765 RISC-V: kexec: Fix memory leak of elf header buffer
RISC-V: kexec: Fix memory leak of elf header buffer
In the Linux kernel, the following vulnerability has been resolved:
RISC-V: kexec: Fix memory leak of elf header buffer
This is reported by kmemleak detector:
unreferenced object 0xff2000000403d000 (size 4096):
comm "kexec", pid 146, jiffies 4294900633 (age 64.792s)
hex dump (first 32 bytes):
7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 .ELF............
04 00 f3 00 01 00
osv
CVE-2025-68360UNKNOWN≥ 0, < 6.17.13-12025-12-24
CVE-2025-68360 CVE-2025-68360: In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks MT7996 dri
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks MT7996 driver can use both wed and wed_hif2 devices to offload traffic from/to the wireless NIC. In the current codebase we assume to always use the primary wed device in wed cal
osv