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 355 of 632
CVE-2023-53353P4MEDIUMCVSS 5.5fixed in linux 6.3.7-1 (forky)2023
CVE-2023-53353 [MEDIUM] CVE-2023-53353: linux - In the Linux kernel, the following vulnerability has been resolved: accel/haban... In the Linux kernel, the following vulnerability has been resolved: accel/habanalabs: postpone mem_mgr IDR destruction to hpriv_release() The memory manager IDR is currently destroyed when user releases the file descriptor. However, at this point the user context might be still held, and memory buffers might be still in use. Later on, calls to release those buffers
debian
CVE-2022-48800P4MEDIUMCVSS 5.5fixed in linux 5.16.10-1 (bookworm)2022
CVE-2022-48800 [MEDIUM] CVE-2022-48800: linux - In the Linux kernel, the following vulnerability has been resolved: mm: vmscan:... In the Linux kernel, the following vulnerability has been resolved: mm: vmscan: remove deadlock due to throttling failing to make progress A soft lockup bug in kcompactd was reported in a private bugzilla with the following visible in dmesg; watchdog: BUG: soft lockup - CPU#33 stuck for 26s! [kcompactd0:479] watchdog: BUG: soft lockup - CPU#33 stuck for 52s! [kcompa
debian
CVE-2025-38735P4MEDIUMCVSS 5.5fixed in linux 6.1.153-1 (bookworm)2025
CVE-2025-38735 [MEDIUM] CVE-2025-38735: linux - In the Linux kernel, the following vulnerability has been resolved: gve: preven... In the Linux kernel, the following vulnerability has been resolved: gve: prevent ethtool ops after shutdown A crash can occur if an ethtool operation is invoked after shutdown() is called. shutdown() is invoked during system shutdown to stop DMA operations without performing expensive deallocations. It is discouraged to unregister the netdev in this path, so the dev
debian
CVE-2025-37972P4MEDIUMCVSS 5.5fixed in linux 6.1.140-1 (bookworm)2025
CVE-2025-37972 [MEDIUM] CVE-2025-37972: linux - In the Linux kernel, the following vulnerability has been resolved: Input: mtk-... In the Linux kernel, the following vulnerability has been resolved: Input: mtk-pmic-keys - fix possible null pointer dereference In mtk_pmic_keys_probe, the regs parameter is only set if the button is parsed in the device tree. However, on hardware where the button is left floating, that node will most likely be removed not to enable that input. In that case the cod
debian
CVE-2025-37961P4MEDIUMCVSS 5.5fixed in linux 6.1.140-1 (bookworm)2025
CVE-2025-37961 [MEDIUM] CVE-2025-37961: linux - In the Linux kernel, the following vulnerability has been resolved: ipvs: fix u... In the Linux kernel, the following vulnerability has been resolved: ipvs: fix uninit-value for saddr in do_output_route4 syzbot reports for uninit-value for the saddr argument [1]. commit 4754957f04f5 ("ipvs: do not use random local source address for tunnels") already implies that the input value of saddr should be ignored but the code is still reading it which can
debian
CVE-2025-38597P4MEDIUMCVSS 5.5fixed in linux 6.16.3-1 (forky)2025
CVE-2025-38597 [MEDIUM] CVE-2025-38597: linux - In the Linux kernel, the following vulnerability has been resolved: drm/rockchi... In the Linux kernel, the following vulnerability has been resolved: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port Each window of a vop2 is usable by a specific set of video ports, so while binding the vop2, we look through the list of available windows trying to find one designated as primary-plane and usable by that specific port. The
debian
CVE-2025-38499P4MEDIUMCVSS 5.5fixed in linux 6.1.147-1 (bookworm)2025
CVE-2025-38499 [MEDIUM] CVE-2025-38499: linux - In the Linux kernel, the following vulnerability has been resolved: clone_priva... In the Linux kernel, the following vulnerability has been resolved: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking
debian
CVE-2025-38163P4MEDIUMCVSS 5.5fixed in linux 6.1.147-1 (bookworm)2025
CVE-2025-38163 [MEDIUM] CVE-2025-38163: linux - In the Linux kernel, the following vulnerability has been resolved: f2fs: fix t... In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on sbi->total_valid_block_count syzbot reported a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/f2fs.h:2521! RIP: 0010:dec_valid_block_count+0x3b2/0x3c0 fs/f2fs/f2fs.h:2521 Call Trace: f2fs_truncate_data_blocks_range+0xc8c/0x11a0 fs/f2fs/f
debian
CVE-2025-38355P4LOWCVSS 5.5fixed in linux 6.12.37-1 (forky)2025
CVE-2025-38355 [MEDIUM] CVE-2025-38355: linux - In the Linux kernel, the following vulnerability has been resolved: drm/xe: Pro... In the Linux kernel, the following vulnerability has been resolved: drm/xe: Process deferred GGTT node removals on device unwind While we are indirectly draining our dedicated workqueue ggtt->wq that we use to complete asynchronous removal of some GGTT nodes, this happends as part of the managed-drm unwinding (ggtt_fini_early), which could be later then manage-devic
debian
CVE-2025-37960P4LOWCVSS 5.5fixed in linux 6.12.29-1 (forky)2025
CVE-2025-37960 [MEDIUM] CVE-2025-37960: linux - In the Linux kernel, the following vulnerability has been resolved: memblock: A... In the Linux kernel, the following vulnerability has been resolved: memblock: Accept allocated memory before use in memblock_double_array() When increasing the array size in memblock_double_array() and the slab is not yet available, a call to memblock_find_in_range() is used to reserve/allocate memory. However, the range returned may not have been accepted, which ca
debian
CVE-2025-38414P4LOWCVSS 5.5fixed in linux 6.12.35-1 (forky)2025
CVE-2025-38414 [MEDIUM] CVE-2025-38414: linux - In the Linux kernel, the following vulnerability has been resolved: wifi: ath12... In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 GCC_GCC_PCIE_HOT_RST is wrongly defined for WCN7850, causing kernel crash on some specific platforms. Since this register is divergent for WCN7850 and QCN9274, move it to register table to allow different definitions. Then correct the reg
debian
CVE-2023-53545P4MEDIUMCVSS 5.5fixed in linux 6.4.13-1 (forky)2023
CVE-2023-53545 [MEDIUM] CVE-2023-53545: 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: unmap and remove csa_va properly Root PD BO should be reserved before unmap and remove a bo_va from VM otherwise lockdep will complain. v2: check fpriv->csa_va is not NULL instead of amdgpu_mcbp (christian) [14616.936827] WARNING: CPU: 6 PID: 1711 at drivers/gpu/drm/amd/amdgpu/amdgpu_vm.
debian
CVE-2023-2430P4MEDIUMCVSS 5.5fixed in linux 6.1.52-1 (bookworm)2023
CVE-2023-2430 [MEDIUM] CVE-2023-2430: linux - A vulnerability was found due to missing lock for IOPOLL flaw in io_cqring_event... A vulnerability was found due to missing lock for IOPOLL flaw in io_cqring_event_overflow() in io_uring.c in Linux Kernel. This flaw allows a local attacker with user privilege to trigger a Denial of Service threat. Scope: local bookworm: resolved (fixed in 6.1.52-1) bullseye: resolved forky: resolved (fixed in 6.3.7-1) sid: resolved (fixed in 6.3.7-1) trixie: resolve
debian
CVE-2022-49744P4MEDIUMCVSS 5.5fixed in linux 6.1.11-1 (bookworm)2022
CVE-2022-49744 [MEDIUM] CVE-2022-49744: linux - In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fi... In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fix pte marker when fork() without fork event Patch series "mm: Fixes on pte markers". Patch 1 resolves the syzkiller report from Pengfei. Patch 2 further harden pte markers when used with the recent swapin error markers. The major case is we should persist a swapin error marker after fork(
debian
CVE-2022-49936P4MEDIUMCVSS 5.5fixed in linux 5.19.11-1 (bookworm)2022
CVE-2022-49936 [MEDIUM] CVE-2022-49936: linux - In the Linux kernel, the following vulnerability has been resolved: USB: core: ... In the Linux kernel, the following vulnerability has been resolved: USB: core: Prevent nested device-reset calls Automatic kernel fuzzing revealed a recursive locking violation in usb-storage: ============================================ WARNING: possible recursive locking detected 5.18.0 #3 Not tainted -------------------------------------------- kworker/1:3/1205 i
debian
CVE-2025-38161P4MEDIUMCVSS 5.5fixed in linux 6.1.147-1 (bookworm)2025
CVE-2025-38161 [MEDIUM] CVE-2025-38161: linux - In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: ... In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction Upon RQ destruction if the firmware command fails which is the last resource to be destroyed some SW resources were already cleaned regardless of the failure. Now properly rollback the object to its original state upon such failure.
debian
CVE-2025-38710P4MEDIUMCVSS 5.5fixed in linux 6.16.3-1 (forky)2025
CVE-2025-38710 [MEDIUM] CVE-2025-38710: linux - In the Linux kernel, the following vulnerability has been resolved: gfs2: Valid... In the Linux kernel, the following vulnerability has been resolved: gfs2: Validate i_depth for exhash directories A fuzzer test introduced corruption that ends up with a depth of 0 in dir_e_read(), causing an undefined shift by 32 at: index = hash >> (32 - dip->i_depth); As calculated in an open-coded way in dir_make_exhash(), the minimum depth for an exhash directo
debian
CVE-2025-38372P4LOWCVSS 5.5fixed in linux 6.12.37-1 (forky)2025
CVE-2025-38372 [MEDIUM] CVE-2025-38372: linux - In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: ... In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix unsafe xarray access in implicit ODP handling __xa_store() and __xa_erase() were used without holding the proper lock, which led to a lockdep warning due to unsafe RCU usage. This patch replaces them with xa_store() and xa_erase(), which perform the necessary locking internally. =====
debian
CVE-2025-38453P4LOWCVSS 5.5fixed in linux 6.16.3-1 (forky)2025
CVE-2025-38453 [MEDIUM] CVE-2025-38453: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring/ms... In the Linux kernel, the following vulnerability has been resolved: io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU syzbot reports that defer/local task_work adding via msg_ring can hit a request that has been freed: CPU: 1 UID: 0 PID: 19356 Comm: iou-wrk-19354 Not tainted 6.16.0-rc4-syzkaller-00108-g17bbde2e1716 #0 PREEMPT(full) Hardware name: Google
debian
CVE-2023-53176P4MEDIUMCVSS 5.5fixed in linux 6.1.37-1 (bookworm)2023
CVE-2023-53176 [MEDIUM] CVE-2023-53176: linux - In the Linux kernel, the following vulnerability has been resolved: serial: 825... In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Reinit port->pm on port specific driver unbind When we unbind a serial port hardware specific 8250 driver, the generic serial8250 driver takes over the port. After that we see an oops about 10 seconds later. This can produce the following at least on some TI SoCs: Unhandled fault: impr
debian
Debian Linux vulnerabilities | cvebase