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 63 of 724
CVE-2023-54147UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-24
CVE-2023-54147 CVE-2023-54147: In the Linux kernel, the following vulnerability has been resolved: media: platform: mtk-mdp3: Add missing check and free for ida_alloc Add the check
In the Linux kernel, the following vulnerability has been resolved: media: platform: mtk-mdp3: Add missing check and free for ida_alloc Add the check for the return value of the ida_alloc in order to avoid NULL pointer dereference. Moreover, free allocated "ctx->id" if mdp_m2m_open fails later in order to avoid memory
osv
CVE-2022-50699UNKNOWN≥ 5.0.0, < 5.10.152≥ 5.11.0, < 5.15.76+1 more2025-12-24
CVE-2022-50699 selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context()
selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context()
In the Linux kernel, the following vulnerability has been resolved:
selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context()
The following warning was triggered on a hardware environment:
SELinux: Converting 162 SID table entries...
BUG: sleeping function called from invalid context at
__might_sleep+0x60/0x74 0x
osv
CVE-2023-54010UNKNOWN≥ 4.4.0, < 4.14.316≥ 4.15.0, < 4.19.284+5 more2025-12-24
CVE-2023-54010 ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in acpi_db_display_objects
ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in acpi_db_display_objects
In the Linux kernel, the following vulnerability has been resolved:
ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in acpi_db_display_objects
ACPICA commit 0d5f467d6a0ba852ea3aad68663cbcbd43300fd4
ACPI_ALLOCATE_ZEROED may fails, object_info might be null and will cause
null pointer dereference later
osv
CVE-2022-50730UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50730 CVE-2022-50730: In the Linux kernel, the following vulnerability has been resolved: ext4: silence the warning when evicting inode with dioread_nolock When evicting an
In the Linux kernel, the following vulnerability has been resolved: ext4: silence the warning when evicting inode with dioread_nolock When evicting an inode with default dioread_nolock, it could be raced by the unwritten extents converting kworker after writeback some new allocated dirty blocks. It convert unwritten
osv
CVE-2022-50705UNKNOWN≥ 0, < 5.15.90≥ 5.16.0, < 6.0.32025-12-24
CVE-2022-50705 io_uring/rw: defer fsnotify calls to task context
io_uring/rw: defer fsnotify calls to task context
In the Linux kernel, the following vulnerability has been resolved:
io_uring/rw: defer fsnotify calls to task context
We can't call these off the kiocb completion as that might be off
soft/hard irq context. Defer the calls to when we process the
task_work for this request. That avoids valid complaints like:
stack backtrace:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.0.0-rc6-syz
osv
CVE-2023-54148UNKNOWN≥ 0, < 6.1.52-1≥ 0, < 6.4.11-12025-12-24
CVE-2023-54148 CVE-2023-54148: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Move representor neigh cleanup to profile cleanup_tx For IP tunnel enca
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Move representor neigh cleanup to profile cleanup_tx For IP tunnel encapsulation in ECMP (Equal-Cost Multipath) mode, as the flow is duplicated to the peer eswitch, the related neighbour information on the peer uplink representor is create
osv
CVE-2025-68353UNKNOWN≥ 6.7.0, < 6.18.22025-12-24
CVE-2025-68353 net: vxlan: prevent NULL deref in vxlan_xmit_one
net: vxlan: prevent NULL deref in vxlan_xmit_one
In the Linux kernel, the following vulnerability has been resolved:
net: vxlan: prevent NULL deref in vxlan_xmit_one
Neither sock4 nor sock6 pointers are guaranteed to be non-NULL in
vxlan_xmit_one, e.g. if the iface is brought down. This can lead to the
following NULL dereference:
BUG: kernel NULL pointer dereference, address: 0000000000000010
Oops: Oops: 0000 [#1] SMP NOPTI
RIP:
osv
CVE-2022-50761UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.4-12025-12-24
CVE-2022-50761 CVE-2022-50761: In the Linux kernel, the following vulnerability has been resolved: x86/xen: Fix memory leak in xen_init_lock_cpu() In xen_init_lock_cpu(), the @name
In the Linux kernel, the following vulnerability has been resolved: x86/xen: Fix memory leak in xen_init_lock_cpu() In xen_init_lock_cpu(), the @name has allocated new string by kasprintf(), if bind_ipi_to_irqhandler() fails, it should be freed, otherwise may lead to a memory leak issue, fix it.
osv
CVE-2023-54116UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-24
CVE-2023-54116 CVE-2023-54116: In the Linux kernel, the following vulnerability has been resolved: drm/fbdev-generic: prohibit potential out-of-bounds access The fbdev test of IGT m
In the Linux kernel, the following vulnerability has been resolved: drm/fbdev-generic: prohibit potential out-of-bounds access The fbdev test of IGT may write after EOF, which lead to out-of-bound access for drm drivers with fbdev-generic. For example, run fbdev test on a x86+ast2400 platform, with 1680x1050 resoluti
osv
CVE-2023-54154UNKNOWN≥ 0, < 6.1.55-1≥ 0, < 6.5.6-12025-12-24
CVE-2023-54154 CVE-2023-54154: In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Fix target_cmd_counter leak The target_cmd_counter struct allo
In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Fix target_cmd_counter leak The target_cmd_counter struct allocated via target_alloc_cmd_counter() is never freed, resulting in leaks across various transport types, e.g.: unreferenced object 0xffff88801f920120 (size 96): comm "sh
osv
CVE-2023-54025UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.52-1+1 more2025-12-24
CVE-2023-54025 CVE-2023-54025: In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: Do not configure WoWlan in shutdown hook if not enabled In case WoWlan
In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: Do not configure WoWlan in shutdown hook if not enabled In case WoWlan was never configured during the operation of the system, the hw->wiphy->wowlan_config will be NULL. rsi_config_wowlan() checks whether wowlan_config is non-NULL and if i
osv
CVE-2025-68733UNKNOWN≥ 0, < 5.10.249-1≥ 0, < 6.1.162-1+2 more2025-12-24
CVE-2025-68733 CVE-2025-68733: In the Linux kernel, the following vulnerability has been resolved: smack: fix bug: unprivileged task can create labels If an unprivileged task is all
In the Linux kernel, the following vulnerability has been resolved: smack: fix bug: unprivileged task can create labels If an unprivileged task is allowed to relabel itself (/smack/relabel-self is not empty), it can freely create new labels by writing their names into own /proc/PID/attr/smack/current This occurs beca
osv
CVE-2023-54087UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.20-12025-12-24
CVE-2023-54087 CVE-2023-54087: In the Linux kernel, the following vulnerability has been resolved: ubi: Fix possible null-ptr-deref in ubi_free_volume() It willl cause null-ptr-dere
In the Linux kernel, the following vulnerability has been resolved: ubi: Fix possible null-ptr-deref in ubi_free_volume() It willl cause null-ptr-deref in the following case: uif_init() ubi_add_volume() cdev_add() -> if it fails, call kill_volumes() device_register() kill_volumes() -> if ubi_add_volume() fails call t
osv
CVE-2023-54002UNKNOWN≥ 5.17.0, < 6.1.29≥ 6.2.0, < 6.2.16+1 more2025-12-24
CVE-2023-54002 btrfs: fix assertion of exclop condition when starting balance
btrfs: fix assertion of exclop condition when starting balance
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix assertion of exclop condition when starting balance
Balance as exclusive state is compatible with paused balance and device
add, which makes some things more complicated. The assertion of valid
states when starting from paused balance needs to take into account two
more states
osv
CVE-2023-54058UNKNOWN≥ 0, < 6.1.37-1≥ 0, < 6.3.7-12025-12-24
CVE-2023-54058 CVE-2023-54058: In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Check if ffa_driver remove is present before executing Currentl
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Check if ffa_driver remove is present before executing Currently ffa_drv->remove() is called unconditionally from ffa_device_remove(). Since the driver registration doesn't check for it and allows it to be registered without .remov
osv
CVE-2023-54098UNKNOWN≥ 0, < 5.10.178-1≥ 0, < 6.1.7-12025-12-24
CVE-2023-54098 CVE-2023-54098: In the Linux kernel, the following vulnerability has been resolved: drm/i915/gvt: fix gvt debugfs destroy When gvt debug fs is destroyed, need to have
In the Linux kernel, the following vulnerability has been resolved: drm/i915/gvt: fix gvt debugfs destroy When gvt debug fs is destroyed, need to have a sane check if drm minor's debugfs root is still available or not, otherwise in case like device remove through unbinding, drm minor's debugfs directory has already b
osv
CVE-2023-54100UNKNOWN≥ 0, < 5.10.191-1≥ 0, < 6.1.37-1+1 more2025-12-24
CVE-2023-54100 CVE-2023-54100: In the Linux kernel, the following vulnerability has been resolved: scsi: qedi: Fix use after free bug in qedi_remove() In qedi_probe() we call __qedi
In the Linux kernel, the following vulnerability has been resolved: scsi: qedi: Fix use after free bug in qedi_remove() In qedi_probe() we call __qedi_probe() which initializes &qedi->recovery_work with qedi_recovery_handler() and &qedi->board_disable_work with qedi_board_disable_work(). When qedi_schedule_recovery_h
osv
CVE-2023-54108UNKNOWN≥ 0, < 5.4.235≥ 5.5.0, < 5.10.173+3 more2025-12-24
CVE-2023-54108 scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests
scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests
The following message and call trace was seen with debug kernels:
DMA-API: qla2xxx 0000:41:00.0: device driver failed to check map
error [device address=0x00000002a3ff38d8] [size=1024 bytes] [mapped as
single]
WARNING: CPU: 0 PID: 2930 at
osv
CVE-2025-68363UNKNOWN≥ 0, < 6.1.162-1≥ 0, < 6.12.63-1+1 more2025-12-24
CVE-2025-68363 CVE-2025-68363: In the Linux kernel, the following vulnerability has been resolved: bpf: Check skb->transport_header is set in bpf_skb_check_mtu The bpf_skb_check_mtu
In the Linux kernel, the following vulnerability has been resolved: bpf: Check skb->transport_header is set in bpf_skb_check_mtu The bpf_skb_check_mtu helper needs to use skb->transport_header when the BPF_MTU_CHK_SEGS flag is used: bpf_skb_check_mtu(skb, ifindex, &mtu_len, 0, BPF_MTU_CHK_SEGS) The transport_header i
osv
CVE-2023-54095UNKNOWN≥ 3.6.0, < 4.14.326≥ 4.15.0, < 4.19.295+6 more2025-12-24
CVE-2023-54095 powerpc/iommu: Fix notifiers being shared by PCI and VIO buses
powerpc/iommu: Fix notifiers being shared by PCI and VIO buses
In the Linux kernel, the following vulnerability has been resolved:
powerpc/iommu: Fix notifiers being shared by PCI and VIO buses
fail_iommu_setup() registers the fail_iommu_bus_notifier struct to both
PCI and VIO buses. struct notifier_block is a linked list node, so this
causes any notifiers later registered to either bus type to also be
registered to
osv