Debian Linux vulnerabilities
12,638 known vulnerabilities affecting debian/linux.
Total CVEs
12,638
CISA KEV
32
actively exploited
Public exploits
142
Exploited in wild
51
Severity breakdown
CRITICAL70HIGH2664MEDIUM6236LOW2442UNKNOWN1226
Vulnerabilities
Page 19 of 632
CVE-2024-26936P3HIGHCVSS 7.8fixed in linux 6.1.90-1 (bookworm)2024
CVE-2024-26936 [HIGH] CVE-2024-26936: linux - In the Linux kernel, the following vulnerability has been resolved: ksmbd: vali...
In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate request buffer size in smb2_allocate_rsp_buf() The response buffer should be allocated in smb2_allocate_rsp_buf before validating request. But the fields in payload as well as smb2 header is used in smb2_allocate_rsp_buf(). This patch add simple buffer size validation to avoid potencia
debian
CVE-2021-47137P3HIGHCVSS 7.8fixed in linux 5.14.6-1 (bookworm)2021
CVE-2021-47137 [HIGH] CVE-2021-47137: linux - In the Linux kernel, the following vulnerability has been resolved: net: lantiq...
In the Linux kernel, the following vulnerability has been resolved: net: lantiq: fix memory corruption in RX ring In a situation where memory allocation or dma mapping fails, an invalid address is programmed into the descriptor. This can lead to memory corruption. If the memory allocation fails, DMA should reuse the previous skb and mapping and drop the packet. This p
debian
CVE-2021-3489P3HIGHCVSS 7.8fixed in linux 5.10.38-1 (bookworm)2021
CVE-2021-3489 [HIGH] CVE-2021-3489: linux - The eBPF RINGBUF bpf_ringbuf_reserve() function in the Linux kernel did not chec...
The eBPF RINGBUF bpf_ringbuf_reserve() function in the Linux kernel did not check that the allocated size was smaller than the ringbuf size, allowing an attacker to perform out-of-bounds writes within the kernel and therefore, arbitrary code execution. This issue was fixed via commit 4b81ccebaeee ("bpf, ringbuf: Deny reserve of buffers larger than ringbuf") (v5.13-rc4)
debian
CVE-2022-49328P3HIGHCVSS 7.8fixed in linux 5.18.5-1 (bookworm)2022
CVE-2022-49328 [HIGH] CVE-2022-49328: linux - In the Linux kernel, the following vulnerability has been resolved: mt76: fix u...
In the Linux kernel, the following vulnerability has been resolved: mt76: fix use-after-free by removing a non-RCU wcid pointer Fixes an issue caught by KASAN about use-after-free in mt76_txq_schedule by protecting mtxq->wcid with rcu_lock between mt76_txq_schedule and sta_info_[alloc, free]. [18853.876689] =============================================================
debian
CVE-2018-1000028P3HIGHCVSS 7.4fixed in linux 4.14.17-1 (bookworm)2018
CVE-2018-1000028 [HIGH] CVE-2018-1000028: linux - Linux kernel version after commit bdcf0a423ea1 - 4.15-rc4+, 4.14.8+, 4.9.76+, 4....
Linux kernel version after commit bdcf0a423ea1 - 4.15-rc4+, 4.14.8+, 4.9.76+, 4.4.111+ contains a Incorrect Access Control vulnerability in NFS server (nfsd) that can result in remote users reading or writing files they should not be able to via NFS. This attack appear to be exploitable via NFS server must export a filesystem with the "rootsquash" options enabled.
debian
CVE-2021-3483P3HIGHCVSS 7.8fixed in linux 5.10.28-1 (bookworm)2021
CVE-2021-3483 [HIGH] CVE-2021-3483: linux - A flaw was found in the Nosy driver in the Linux kernel. This issue allows a dev...
A flaw was found in the Nosy driver in the Linux kernel. This issue allows a device to be inserted twice into a doubly-linked list, leading to a use-after-free when one of these devices is removed. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. Versions before kernel 5.12-rc6 are affected
Scope: local
bookwor
debian
CVE-2022-49114P3HIGHCVSS 7.8fixed in linux 5.17.3-1 (bookworm)2022
CVE-2022-49114 [HIGH] CVE-2022-49114: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: libfc...
In the Linux kernel, the following vulnerability has been resolved: scsi: libfc: Fix use after free in fc_exch_abts_resp() fc_exch_release(ep) will decrease the ep's reference count. When the reference count reaches zero, it is freed. But ep is still used in the following code, which will lead to a use after free. Return after the fc_exch_release() call to avoid use a
debian
CVE-2022-49111P3HIGHCVSS 7.8fixed in linux 5.17.3-1 (bookworm)2022
CVE-2022-49111 [HIGH] CVE-2022-49111: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ...
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use after free in hci_send_acl This fixes the following trace caused by receiving HCI_EV_DISCONN_PHY_LINK_COMPLETE which does call hci_conn_del without first checking if conn->type is in fact AMP_LINK and in case it is do properly cleanup upper layers with hci_disconn_cfm: =============
debian
CVE-2022-49416P3HIGHCVSS 7.8fixed in linux 5.18.5-1 (bookworm)2022
CVE-2022-49416 [HIGH] CVE-2022-49416: linux - In the Linux kernel, the following vulnerability has been resolved: wifi: mac80...
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix use-after-free in chanctx code In ieee80211_vif_use_reserved_context(), when we have an old context and the new context's replace_state is set to IEEE80211_CHANCTX_REPLACE_NONE, we free the old context in ieee80211_vif_use_reserved_reassign(). Therefore, we cannot check the old_ctx
debian
CVE-2022-49470P3HIGHCVSS 7.8fixed in linux 5.18.5-1 (bookworm)2022
CVE-2022-49470 [HIGH] CVE-2022-49470: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ...
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event We should not access skb buffer data anymore after hci_recv_frame was called. [ 39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0 [ 39.634855] Read of size 1 at addr ffffff80cf28a60d by task kworker [ 39.634962] Call tr
debian
CVE-2023-3611P3HIGHCVSS 7.8fixed in linux 6.1.52-1 (bookworm)2023
CVE-2023-3611 [HIGH] CVE-2023-3611: linux - An out-of-bounds write vulnerability in the Linux kernel's net/sched: sch_qfq co...
An out-of-bounds write vulnerability in the Linux kernel's net/sched: sch_qfq component can be exploited to achieve local privilege escalation. The qfq_change_agg() function in net/sched/sch_qfq.c allows an out-of-bounds write because lmax is updated according to packet sizes without bounds checks. We recommend upgrading past commit 3e337087c3b5805fe0b8a46ba622a962880b5
debian
CVE-2022-48980P3HIGHCVSS 7.8fixed in linux 6.1.4-1 (bookworm)2022
CVE-2022-48980 [HIGH] CVE-2022-48980: linux - In the Linux kernel, the following vulnerability has been resolved: net: dsa: s...
In the Linux kernel, the following vulnerability has been resolved: net: dsa: sja1105: avoid out of bounds access in sja1105_init_l2_policing() The SJA1105 family has 45 L2 policing table entries (SJA1105_MAX_L2_POLICING_COUNT) and SJA1110 has 110 (SJA1110_MAX_L2_POLICING_COUNT). Keeping the table structure but accounting for the difference in port count (5 in SJA1105
debian
CVE-2025-38585P3HIGHCVSS 7.8fixed in linux 6.16.3-1 (forky)2025
CVE-2025-38585 [HIGH] CVE-2025-38585: linux - In the Linux kernel, the following vulnerability has been resolved: staging: me...
In the Linux kernel, the following vulnerability has been resolved: staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int() When gmin_get_config_var() calls efi.get_variable() and the EFI variable is larger than the expected buffer size, two behaviors combine to create a stack buffer overflow: 1. gmin_get_config_var() does not return the proper error
debian
CVE-2026-23092P3LOWCVSS 7.8fixed in linux 6.18.8-1 (forky)2026
CVE-2026-23092 [HIGH] CVE-2026-23092: linux - In the Linux kernel, the following vulnerability has been resolved: iio: dac: a...
In the Linux kernel, the following vulnerability has been resolved: iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source When simple_write_to_buffer() succeeds, it returns the number of bytes actually copied to the buffer. The code incorrectly uses 'count' as the index for null termination instead of the actual bytes copied. If count exceeds th
debian
CVE-2026-23178P3HIGHCVSS 7.8fixed in linux 6.1.164-1 (bookworm)2026
CVE-2026-23178 [HIGH] CVE-2026-23178: linux - In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hi...
In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() `i2c_hid_xfer` is used to read `recv_len + sizeof(__le16)` bytes of data into `ihid->rawbuf`. The former can come from the userspace in the hidraw driver and is only bounded by HID_MAX_BUFFER_SIZE(16384) by default (unless we also set
debian
CVE-2026-23208P3HIGHCVSS 7.8fixed in linux 6.18.10-1 (forky)2026
CVE-2026-23208 [HIGH] CVE-2026-23208: linux - In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-a...
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Prevent excessive number of frames In this case, the user constructed the parameters with maxpacksize 40 for rate 22050 / pps 1000, and packsize[0] 22 packsize[1] 23. The buffer size for each data URB is maxpacksize * packets, which in this example is 40 * 6 = 240; When the user perfo
debian
CVE-2021-47378P3CRITICALCVSS 9.8fixed in linux 5.14.9-1 (bookworm)2021
CVE-2021-47378 [CRITICAL] CVE-2021-47378: linux - In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: ...
In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: destroy cm id before destroy qp to avoid use after free We should always destroy cm_id before destroy qp to avoid to get cma event after qp was destroyed, which may lead to use after free. In RDMA connection establishment error flow, don't destroy qp in cm event handler.Just report cm_e
debian
CVE-2025-71089P3HIGHCVSS 7.8fixed in linux 6.1.164-1 (bookworm)2025
CVE-2025-71089 [HIGH] CVE-2025-71089: linux - In the Linux kernel, the following vulnerability has been resolved: iommu: disa...
In the Linux kernel, the following vulnerability has been resolved: iommu: disable SVA when CONFIG_X86 is set Patch series "Fix stale IOTLB entries for kernel address space", v7. This proposes a fix for a security vulnerability related to IOMMU Shared Virtual Addressing (SVA). In an SVA context, an IOMMU can cache kernel page table entries. When a kernel page table pa
debian
CVE-2023-52442P3MEDIUMCVSS 5.5fixed in linux 6.1.55-1 (bookworm)2023
CVE-2023-52442 [MEDIUM] CVE-2023-52442: linux - In the Linux kernel, the following vulnerability has been resolved: ksmbd: vali...
In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate session id and tree id in compound request `smb2_get_msg()` in smb2_get_ksmbd_tcon() and smb2_check_user_session() will always return the first request smb2 header in a compound request. if `SMB2_TREE_CONNECT_HE` is the first command in compound request, will return 0, i.e. The tree
debian
CVE-2021-47274P3CRITICALCVSS 9.8fixed in linux 5.10.46-1 (bookworm)2021
CVE-2021-47274 [CRITICAL] CVE-2021-47274: linux - In the Linux kernel, the following vulnerability has been resolved: tracing: Co...
In the Linux kernel, the following vulnerability has been resolved: tracing: Correct the length check which causes memory corruption We've suffered from severe kernel crashes due to memory corruption on our production environment, like, Call Trace: [1640542.554277] general protection fault: 0000 [#1] SMP PTI [1640542.554856] CPU: 17 PID: 26996 Comm: python Kdump:
debian