cbcvebase.

Debian Linux vulnerabilities

12,638 known vulnerabilities affecting debian/linux.

Total CVEs
12,638
CISA KEV
29
actively exploited
Public exploits
140
Exploited in wild
47
Severity breakdown
CRITICAL70HIGH2664MEDIUM6236LOW2442UNKNOWN1226

Vulnerabilities

Page 292 of 632
CVE-2023-53761P4UNKNOWNfixed in linux 6.1.37-1 (bookworm)2023
CVE-2023-53761 CVE-2023-53761: linux - In the Linux kernel, the following vulnerability has been resolved: USB: usbtmc... In the Linux kernel, the following vulnerability has been resolved: USB: usbtmc: Fix direction for 0-length ioctl control messages The syzbot fuzzer found a problem in the usbtmc driver: When a user submits an ioctl for a 0-length control transfer, the driver does not check that the direction is set to OUT: ------------[ cut here ]------------ usb 3-1: BOGUS control dir, pip
debian
CVE-2025-68778P4UNKNOWNfixed in linux 6.1.162-1 (bookworm)2025
CVE-2025-68778 CVE-2025-68778: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: don'... In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current transaction, as this can result an attempt to have a directory with two hard links durin
debian
CVE-2025-68371P4UNKNOWNfixed in linux 6.1.162-1 (bookworm)2025
CVE-2025-68371 CVE-2025-68371: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: smart... In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix device resources accessed after device removal Correct possible race conditions during device removal. Previously, a scheduled work item to reset a LUN could still execute after the device was removed, leading to use-after-free and other resource access issues. This race condition occurs
debian
CVE-2023-54039P4UNKNOWNfixed in linux 6.1.25-1 (bookworm)2023
CVE-2023-54039 CVE-2023-54039: linux - In the Linux kernel, the following vulnerability has been resolved: can: j1939:... In the Linux kernel, the following vulnerability has been resolved: can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access In the j1939_tp_tx_dat_new() function, an out-of-bounds memory access could occur during the memcpy() operation if the size of skb->cb is larger than the size of struct j1939_sk_buff_cb. This is because the memcpy() operation uses the size of
debian
CVE-2025-68231P4UNKNOWNfixed in linux 6.1.159-1 (bookworm)2025
CVE-2025-68231 CVE-2025-68231: linux - In the Linux kernel, the following vulnerability has been resolved: mm/mempool:... In the Linux kernel, the following vulnerability has been resolved: mm/mempool: fix poisoning order>0 pages with HIGHMEM The kernel test has reported: BUG: unable to handle page fault for address: fffba000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page *pde = 03171067 *pte = 00000000 Oops: Oops: 0002 [#1] CPU: 0 UID: 0 PID: 1 Comm: swa
debian
CVE-2025-68262P4LOWfixed in linux 6.17.12-1 (forky)2025
CVE-2025-68262 [LOW] CVE-2025-68262: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: zst... In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstd_streams (per-CPU contexts) are freed in zstd_exit() during every tfm destruction, rather than being managed at the
debian
CVE-2025-68322P4UNKNOWNfixed in linux 6.17.8-1 (forky)2025
CVE-2025-68322 CVE-2025-68322: linux - In the Linux kernel, the following vulnerability has been resolved: parisc: Avo... In the Linux kernel, the following vulnerability has been resolved: parisc: Avoid crash due to unaligned access in unwinder Guenter Roeck reported this kernel crash on his emulated B160L machine: Starting network: udhcpc: started, v1.36.1 Backtrace: [] unwind_once+0x1c/0x5c [] walk_stackframe.isra.0+0x74/0xb8 [] arch_stack_walk+0x28/0x38 [] stack_trace_save+0x48/0x5c [] set_
debian
CVE-2025-68376P4LOWfixed in linux 6.17.13-1 (forky)2025
CVE-2025-68376 [LOW] CVE-2025-68376: linux - In the Linux kernel, the following vulnerability has been resolved: coresight: ... In the Linux kernel, the following vulnerability has been resolved: coresight: ETR: Fix ETR buffer use-after-free issue When ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed and enabled again, currently sysfs_buf will point to the newly allocated memory(buf_new) and free the old memory(buf_old). But the etr_buf that is being used by the ETR remains pointe
debian
CVE-2025-68760P4LOWfixed in linux 6.17.13-1 (forky)2025
CVE-2025-68760 [LOW] CVE-2025-68760: linux - In the Linux kernel, the following vulnerability has been resolved: iommu/amd: ... In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix potential out-of-bounds read in iommu_mmio_show In iommu_mmio_write(), it validates the user-provided offset with the check: `iommu->dbg_mmio_offset > iommu->mmio_phys_end - 4`. This assumes a 4-byte access. However, the corresponding show handler, iommu_mmio_show(), uses readq() to perf
debian
CVE-2023-54027P4UNKNOWNfixed in linux 6.1.52-1 (bookworm)2023
CVE-2023-54027 CVE-2023-54027: linux - In the Linux kernel, the following vulnerability has been resolved: iio: core: ... In the Linux kernel, the following vulnerability has been resolved: iio: core: Prevent invalid memory access when there is no parent Commit 813665564b3d ("iio: core: Convert to use firmware node handle instead of OF node") switched the kind of nodes to use for label retrieval in device registration. Probably an unwanted change in that commit was that if the device has no par
debian
CVE-2026-23042P4LOWfixed in linux 6.18.8-1 (forky)2026
CVE-2026-23042 [LOW] CVE-2026-23042: linux - In the Linux kernel, the following vulnerability has been resolved: idpf: fix a... In the Linux kernel, the following vulnerability has been resolved: idpf: fix aux device unplugging when rdma is not supported by vport If vport flags do not contain VIRTCHNL2_VPORT_ENABLE_RDMA, driver does not allocate vdev_info for this vport. This leads to kernel NULL pointer dereference in idpf_idc_vport_dev_down(), which references vdev_info for every vport regard
debian
CVE-2026-23474P4UNKNOWNfixed in linux 6.19.10-1 (forky)2026
CVE-2026-23474 CVE-2026-23474: linux - In the Linux kernel, the following vulnerability has been resolved: mtd: Avoid ... In the Linux kernel, the following vulnerability has been resolved: mtd: Avoid boot crash in RedBoot partition table parser Given CONFIG_FORTIFY_SOURCE=y and a recent compiler, commit 439a1bcac648 ("fortify: Use __builtin_dynamic_object_size() when available") produces the warning below and an oops. Searching for RedBoot partition table in 50000000.flash at offset 0x7e0000 -
debian
CVE-2017-16911P4MEDIUMCVSS 4.7fixed in linux 4.14.12-1 (bookworm)2017
CVE-2017-16911 [MEDIUM] CVE-2017-16911: linux - The vhci_hcd driver in the Linux Kernel before version 4.14.8 and 4.4.114 allows... The vhci_hcd driver in the Linux Kernel before version 4.14.8 and 4.4.114 allows allows local attackers to disclose kernel memory addresses. Successful exploitation requires that a USB device is attached over IP. Scope: local bookworm: resolved (fixed in 4.14.12-1) bullseye: resolved (fixed in 4.14.12-1) forky: resolved (fixed in 4.14.12-1) sid: resolved (fixed in 4
debian
CVE-2026-23468P4UNKNOWNfixed in linux 6.19.10-1 (forky)2026
CVE-2026-23468 CVE-2026-23468: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu:... In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion Userspace can pass an arbitrary number of BO list entries via the bo_number field. Although the previous multiplication overflow check prevents out-of-bounds allocation, a large number of entries could still cause excessive memory allocatio
debian
CVE-2026-23307P4UNKNOWNfixed in linux 6.19.8-1 (forky)2026
CVE-2026-23307 CVE-2026-23307: linux - In the Linux kernel, the following vulnerability has been resolved: can: ems_us... In the Linux kernel, the following vulnerability has been resolved: can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message When looking at the data in a USB urb, the actual_length is the size of the buffer passed to the driver, not the transfer_buffer_length which is set by the driver as the max size of the buffer. When parsing the messages in ems_u
debian
CVE-2026-23355P4LOWfixed in linux 6.19.8-1 (forky)2026
CVE-2026-23355 [LOW] CVE-2026-23355: linux - In the Linux kernel, the following vulnerability has been resolved: ata: libata... In the Linux kernel, the following vulnerability has been resolved: ata: libata: cancel pending work after clearing deferred_qc Syzbot reported a WARN_ON() in ata_scsi_deferred_qc_work(), caused by ap->ops->qc_defer() returning non-zero before issuing the deferred qc. ata_scsi_schedule_deferred_qc() is called during each command completion. This function will check if
debian
CVE-2025-71267P4UNKNOWNfixed in linux 6.19.6-1 (forky)2025
CVE-2025-71267 CVE-2025-71267: linux - In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: ... In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST We found an infinite loop bug in the ntfs3 file system that can lead to a Denial-of-Service (DoS) condition. A malformed NTFS image can cause an infinite loop when an ATTR_LIST attribute indicates a zero data size while the driver allocates memor
debian
CVE-2026-23377P4LOWfixed in linux 6.19.8-1 (forky)2026
CVE-2026-23377 [LOW] CVE-2026-23377: linux - In the Linux kernel, the following vulnerability has been resolved: ice: change... In the Linux kernel, the following vulnerability has been resolved: ice: change XDP RxQ frag_size from DMA write length to xdp.frame_sz The only user of frag_size field in XDP RxQ info is bpf_xdp_frags_increase_tail(). It clearly expects whole buff size instead of DMA write size. Different assumptions in ice driver configuration lead to negative tailroom. This allows t
debian
CVE-2019-3901P4MEDIUMCVSS 4.7fixed in linux 4.6.1-1 (bookworm)2019
CVE-2019-3901 [MEDIUM] CVE-2019-3901: linux - A race condition in perf_event_open() allows local attackers to leak sensitive d... A race condition in perf_event_open() allows local attackers to leak sensitive data from setuid programs. As no relevant locks (in particular the cred_guard_mutex) are held during the ptrace_may_access() call, it is possible for the specified target task to perform an execve() syscall with setuid execution before perf_event_alloc() actually attaches to it, allowing an
debian
CVE-2023-0160P4MEDIUMCVSS 4.7fixed in linux 6.1.85-1 (bookworm)2023
CVE-2023-0160 [MEDIUM] CVE-2023-0160: linux - A deadlock flaw was found in the Linux kernel’s BPF subsystem. This flaw allows ... A deadlock flaw was found in the Linux kernel’s BPF subsystem. This flaw allows a local user to potentially crash the system. Scope: local bookworm: resolved (fixed in 6.1.85-1) bullseye: resolved (fixed in 5.10.216-1) forky: resolved (fixed in 6.8.9-1) sid: resolved (fixed in 6.8.9-1) trixie: resolved (fixed in 6.8.9-1)
debian
Debian Linux vulnerabilities | cvebase