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 23 of 724
CVE-2026-23085MEDIUMCVSS 5.5≥ 3.19, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23085 [MEDIUM] CVE-2026-23085: In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3-its: Avoid trunc
In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3-its: Avoid truncating memory addresses
On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem
allocations to be backed by addresses physical memory above the 32-bit
address limit, as found while experimenting with larger VMSPLIT
configurations.
This caused the
nvdosv
CVE-2026-23108MEDIUMCVSS 5.5≥ 3.9, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23108 [MEDIUM] CWE-401 CVE-2026-23108: In the Linux kernel, the following vulnerability has been resolved:
can: usb_8dev: usb_8dev_read_bu
In the Linux kernel, the following vulnerability has been resolved:
can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak
Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb:
gs_usb_receive_bulk_callback(): fix URB memory leak").
In usb_8dev_open() -> usb_8dev_start(), the URBs for USB-in transfers are
allocated, added to
nvdosv
CVE-2026-23071MEDIUMCVSS 4.7≥ 4.15, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23071 [MEDIUM] CWE-362 CVE-2026-23071: In the Linux kernel, the following vulnerability has been resolved:
regmap: Fix race condition in h
In the Linux kernel, the following vulnerability has been resolved:
regmap: Fix race condition in hwspinlock irqsave routine
Previously, the address of the shared member '&map->spinlock_flags' was
passed directly to 'hwspin_lock_timeout_irqsave'. This creates a race
condition where multiple contexts contending for the lock could overwrite
the shar
nvdosv
CVE-2026-23080MEDIUMCVSS 5.5≥ 4.12, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23080 [MEDIUM] CWE-401 CVE-2026-23080: In the Linux kernel, the following vulnerability has been resolved:
can: mcba_usb: mcba_usb_read_bu
In the Linux kernel, the following vulnerability has been resolved:
can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak
Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb:
gs_usb_receive_bulk_callback(): fix URB memory leak").
In mcba_usb_probe() -> mcba_usb_start(), the URBs for USB-in transfers are
allocated, added to
nvdosv
CVE-2026-23086MEDIUMCVSS 5.5≥ 4.8, < 6.1.162≥ 6.2, < 6.6.122+3 more2026-02-04
CVE-2026-23086 [MEDIUM] CVE-2026-23086: In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: cap TX credit to
In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: cap TX credit to local buffer size
The virtio transports derives its TX credit directly from peer_buf_alloc,
which is set from the remote endpoint's SO_VM_SOCKETS_BUFFER_SIZE value.
On the host side this means that the amount of data we are willing to
queue for a connection
nvdosv
CVE-2026-23082MEDIUMCVSS 5.5v6.12.67v6.18.7+1 more2026-02-04
CVE-2026-23082 [MEDIUM] CWE-835 CVE-2026-23082: In the Linux kernel, the following vulnerability has been resolved:
can: gs_usb: gs_usb_receive_bul
In the Linux kernel, the following vulnerability has been resolved:
can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error
In commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix
URB memory leak"), the URB was re-anchored before usb_submit_urb() in
gs_usb_receive_bulk_callback() to prevent a leak of t
nvd
CVE-2026-23110MEDIUMCVSS 4.7≥ 5.5, < 5.10.249≥ 5.11, < 6.1.162+4 more2026-02-04
CVE-2026-23110 [MEDIUM] CWE-362 CVE-2026-23110: In the Linux kernel, the following vulnerability has been resolved:
scsi: core: Wake up the error h
In the Linux kernel, the following vulnerability has been resolved:
scsi: core: Wake up the error handler when final completions race against each other
The fragile ordering between marking commands completed or failed so
that the error handler only wakes when the last running command
completes or times out has race conditions. These race conditio
nvdosv
CVE-2026-23101MEDIUMCVSS 4.7≥ 3.7, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23101 [MEDIUM] CWE-908 CVE-2026-23101: In the Linux kernel, the following vulnerability has been resolved:
leds: led-class: Only Add LED t
In the Linux kernel, the following vulnerability has been resolved:
leds: led-class: Only Add LED to leds_list when it is fully ready
Before this change the LED was added to leds_list before led_init_core()
gets called adding it the list before led_classdev.set_brightness_work gets
initialized.
This leaves a window where led_trigger_register() of
nvdosv
CVE-2026-23087MEDIUMCVSS 5.5≥ 3.18, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23087 [MEDIUM] CWE-401 CVE-2026-23087: In the Linux kernel, the following vulnerability has been resolved:
scsi: xen: scsiback: Fix potent
In the Linux kernel, the following vulnerability has been resolved:
scsi: xen: scsiback: Fix potential memory leak in scsiback_remove()
Memory allocated for struct vscsiblk_info in scsiback_probe() is not
freed in scsiback_remove() leading to potential memory leaks on remove,
as well as in the scsiback_probe() error paths. Fix that by freeing it
i
nvdosv
CVE-2026-23091MEDIUMCVSS 5.5≥ 4.4, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23091 [MEDIUM] CWE-401 CVE-2026-23091: In the Linux kernel, the following vulnerability has been resolved:
intel_th: fix device leak on ou
In the Linux kernel, the following vulnerability has been resolved:
intel_th: fix device leak on output open()
Make sure to drop the reference taken when looking up the th device
during output device open() on errors and on close().
Note that a recent commit fixed the leak in a couple of open() error
paths but not all of them, and the reference i
nvdosv
CVE-2026-23088MEDIUMCVSS 5.5≥ 5.10.237, < 5.11≥ 5.15.124, < 5.16+5 more2026-02-04
CVE-2026-23088 [MEDIUM] CWE-476 CVE-2026-23088: In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix crash on synthetic
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix crash on synthetic stacktrace field usage
When creating a synthetic event based on an existing synthetic event that
had a stacktrace field and the new synthetic event used that field a
kernel crash occurred:
~# cd /sys/kernel/tracing
~# echo 's:stack unsigned long st
nvdosv
CVE-2026-23084MEDIUMCVSS 5.5≥ 3.12, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23084 [MEDIUM] CWE-476 CVE-2026-23084: In the Linux kernel, the following vulnerability has been resolved:
be2net: Fix NULL pointer derefe
In the Linux kernel, the following vulnerability has been resolved:
be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list
When the parameter pmac_id_valid argument of be_cmd_get_mac_from_list() is
set to false, the driver may request the PMAC_ID from the firmware of the
network card, and this function will store that PMAC_ID at the prov
nvdosv
CVE-2026-23061MEDIUMCVSS 5.5≥ 3.8, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23061 [MEDIUM] CWE-401 CVE-2026-23061: In the Linux kernel, the following vulnerability has been resolved:
can: kvaser_usb: kvaser_usb_rea
In the Linux kernel, the following vulnerability has been resolved:
can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak
Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb:
gs_usb_receive_bulk_callback(): fix URB memory leak").
In kvaser_usb_set_{,data_}bittiming() -> kvaser_usb_setup_rx_urbs(), the
URBs for USB-in t
nvdosv
CVE-2026-23072MEDIUMCVSS 5.5≥ 6.10, < 6.12.68≥ 6.13, < 6.18.8+1 more2026-02-04
CVE-2026-23072 [MEDIUM] CWE-401 CVE-2026-23072: In the Linux kernel, the following vulnerability has been resolved:
l2tp: Fix memleak in l2tp_udp_e
In the Linux kernel, the following vulnerability has been resolved:
l2tp: Fix memleak in l2tp_udp_encap_recv().
syzbot reported memleak of struct l2tp_session, l2tp_tunnel,
sock, etc. [0]
The cited commit moved down the validation of the protocol
version in l2tp_udp_encap_recv().
The new place requires an extra error handling to avoid the
memlea
nvdosv
CVE-2026-23069MEDIUMCVSS 5.5≥ 4.8, < 6.1.162≥ 6.2, < 6.6.122+3 more2026-02-04
CVE-2026-23069 [MEDIUM] CWE-191 CVE-2026-23069: In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: fix potential und
In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: fix potential underflow in virtio_transport_get_credit()
The credit calculation in virtio_transport_get_credit() uses unsigned
arithmetic:
ret = vvs->peer_buf_alloc - (vvs->tx_cnt - vvs->peer_fwd_cnt);
If the peer shrinks its advertised buffer (peer_buf_alloc) whil
nvdosv
CVE-2026-23100MEDIUMCVSS 5.5≥ 5.10.239, < 5.11≥ 5.15.186, < 5.16+6 more2026-02-04
CVE-2026-23100 [MEDIUM] CVE-2026-23100: In the Linux kernel, the following vulnerability has been resolved:
mm/hugetlb: fix hugetlb_pmd_sha
In the Linux kernel, the following vulnerability has been resolved:
mm/hugetlb: fix hugetlb_pmd_shared()
Patch series "mm/hugetlb: fixes for PMD table sharing (incl. using
mmu_gather)", v3.
One functional fix, one performance regression fix, and two related
comment fixes.
I cleaned up my prototype I recently shared [1] for the performance fix,
deferring
nvdosv
CVE-2026-23066MEDIUMCVSS 5.5≥ 4.11, < 6.18.8v6.192026-02-04
CVE-2026-23066 [MEDIUM] CWE-674 CVE-2026-23066: In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix recvmsg() unconditio
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix recvmsg() unconditional requeue
If rxrpc_recvmsg() fails because MSG_DONTWAIT was specified but the call at
the front of the recvmsg queue already has its mutex locked, it requeues
the call - whether or not the call is already queued. The call may be on
the queue becaus
nvdosv
CVE-2026-23105MEDIUMCVSS 5.5≥ 3.8, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23105 [MEDIUM] CVE-2026-23105: In the Linux kernel, the following vulnerability has been resolved:
net/sched: qfq: Use cl_is_activ
In the Linux kernel, the following vulnerability has been resolved:
net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag
This is more of a preventive patch to make the code more consistent and
to prevent possible exploits that employ child qlen manipulations on qfq.
use cl_is_active instead of relying on the child qdisc'
nvdosv
CVE-2026-23103MEDIUMCVSS 5.5≥ 4.17, < 5.10.249≥ 5.11, < 5.15.199+5 more2026-02-04
CVE-2026-23103 [MEDIUM] CWE-667 CVE-2026-23103: In the Linux kernel, the following vulnerability has been resolved:
ipvlan: Make the addrs_lock be
In the Linux kernel, the following vulnerability has been resolved:
ipvlan: Make the addrs_lock be per port
Make the addrs_lock be per port, not per ipvlan dev.
Initial code seems to be written in the assumption,
that any address change must occur under RTNL.
But it is not so for the case of IPv6. So
1) Introduce per-port addrs_lock.
2) It was n
nvdosv
CVE-2026-23065MEDIUMCVSS 5.5≥ 6.8, < 6.12.68≥ 6.13, < 6.18.8+1 more2026-02-04
CVE-2026-23065 [MEDIUM] CWE-401 CVE-2026-23065: In the Linux kernel, the following vulnerability has been resolved:
platform/x86/amd: Fix memory le
In the Linux kernel, the following vulnerability has been resolved:
platform/x86/amd: Fix memory leak in wbrf_record()
The tmp buffer is allocated using kcalloc() but is not freed if
acpi_evaluate_dsm() fails. This causes a memory leak in the error path.
Fix this by explicitly freeing the tmp buffer in the error handling
path of acpi_evaluate_dsm
nvdosv