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 430 of 632
CVE-2025-38145P4MEDIUMCVSS 5.5fixed in linux 6.1.147-1 (bookworm)2025
CVE-2025-38145 [MEDIUM] CVE-2025-38145: linux - In the Linux kernel, the following vulnerability has been resolved: soc: aspeed...
In the Linux kernel, the following vulnerability has been resolved: soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop() devm_kasprintf() returns NULL when memory allocation fails. Currently, aspeed_lpc_enable_snoop() does not check for this case, which results in a NULL pointer dereference. Add NULL check after devm_kasprintf() to prevent this issue. [arj: Fix
debian
CVE-2025-22128P4LOWCVSS 5.5fixed in linux 6.12.35-1 (forky)2025
CVE-2025-22128 [MEDIUM] CVE-2025-22128: 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: Clear affinity hint before calling ath12k_pci_free_irq() in error path If a shared IRQ is used by the driver due to platform limitation, then the IRQ affinity hint is set right after the allocation of IRQ vectors in ath12k_pci_msi_alloc(). This does no harm unless one of the functions
debian
CVE-2025-23135P4LOWCVSS 5.5fixed in linux 6.16.3-1 (forky)2025
CVE-2025-23135 [MEDIUM] CVE-2025-23135: linux - In the Linux kernel, the following vulnerability has been resolved: RISC-V: KVM...
In the Linux kernel, the following vulnerability has been resolved: RISC-V: KVM: Teardown riscv specific bits after kvm_exit During a module removal, kvm_exit invokes arch specific disable call which disables AIA. However, we invoke aia_exit before kvm_exit resulting in the following warning. KVM kernel module can't be inserted afterwards due to inconsistent state o
debian
CVE-2024-46678P4MEDIUMCVSS 5.5fixed in linux 6.10.9-1 (forky)2024
CVE-2024-46678 [MEDIUM] CVE-2024-46678: linux - In the Linux kernel, the following vulnerability has been resolved: bonding: ch...
In the Linux kernel, the following vulnerability has been resolved: bonding: change ipsec_lock from spin lock to mutex In the cited commit, bond->ipsec_lock is added to protect ipsec_list, hence xdo_dev_state_add and xdo_dev_state_delete are called inside this lock. As ipsec_lock is a spin lock and such xfrmdev ops may sleep, "scheduling while atomic" will be trigge
debian
CVE-2023-53144P4MEDIUMCVSS 5.5fixed in linux 6.1.20-1 (bookworm)2023
CVE-2023-53144 [MEDIUM] CVE-2023-53144: linux - In the Linux kernel, the following vulnerability has been resolved: erofs: fix ...
In the Linux kernel, the following vulnerability has been resolved: erofs: fix wrong kunmap when using LZMA on HIGHMEM platforms As the call trace shown, the root cause is kunmap incorrect pages: BUG: kernel NULL pointer dereference, address: 00000000 CPU: 1 PID: 40 Comm: kworker/u5:0 Not tainted 6.2.0-rc5 #4 Workqueue: erofs_worker z_erofs_decompressqueue_work EIP:
debian
CVE-2023-52595P4MEDIUMCVSS 5.5fixed in linux 6.1.82-1 (bookworm)2023
CVE-2023-52595 [MEDIUM] CVE-2023-52595: linux - In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x0...
In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x00: restart beacon queue when hardware reset When a hardware reset is triggered, all registers are reset, so all queues are forced to stop in hardware interface. However, mac80211 will not automatically stop the queue. If we don't manually stop the beacon queue, the queue will be deadlocke
debian
CVE-2025-21949P4MEDIUMCVSS 5.5fixed in linux 6.16.3-1 (forky)2025
CVE-2025-21949 [MEDIUM] CVE-2025-21949: linux - In the Linux kernel, the following vulnerability has been resolved: LoongArch: ...
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Set hugetlb mmap base address aligned with pmd size With ltp test case "testcases/bin/hugefork02", there is a dmesg error report message such as: kernel BUG at mm/hugetlb.c:5550! Oops - BUG[#1]: CPU: 0 UID: 0 PID: 1517 Comm: hugefork02 Not tainted 6.14.0-rc2+ #241 Hardware name: QEMU QEMU
debian
CVE-2025-21674P4LOWCVSS 5.5fixed in linux 6.12.11-1 (forky)2025
CVE-2025-21674 [MEDIUM] CVE-2025-21674: linux - In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: ...
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel Attempt to enable IPsec packet offload in tunnel mode in debug kernel generates the following kernel panic, which is happening due to two issues: 1. In SA add section, the should be _bh() variant when marking SA mode. 2. There i
debian
CVE-2024-35784P4MEDIUMCVSS 5.5fixed in linux 6.7.12-1 (forky)2024
CVE-2024-35784 [MEDIUM] CVE-2024-35784: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: fix ...
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock with fiemap and extent locking While working on the patchset to remove extent locking I got a lockdep splat with fiemap and pagefaulting with my new extent lock replacement lock. This deadlock exists with our normal code, we just don't have lockdep annotations with the extent loc
debian
CVE-2024-27003P4MEDIUMCVSS 5.5fixed in linux 6.1.90-1 (bookworm)2024
CVE-2024-27003 [MEDIUM] CVE-2024-27003: linux - In the Linux kernel, the following vulnerability has been resolved: clk: Get ru...
In the Linux kernel, the following vulnerability has been resolved: clk: Get runtime PM before walking tree for clk_summary Similar to the previous commit, we should make sure that all devices are runtime resumed before printing the clk_summary through debugfs. Failure to do so would result in a deadlock if the thread is resuming a device to print clk state and that
debian
CVE-2024-46733P4MEDIUMCVSS 5.5fixed in linux 6.1.135-1 (bookworm)2024
CVE-2024-46733 [MEDIUM] CVE-2024-46733: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: fix ...
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve leaks in cow_file_range In the buffered write path, the dirty page owns the qgroup reserve until it creates an ordered_extent. Therefore, any errors that occur before the ordered_extent is created must free that reservation, or else the space is leaked. The fstest generic/4
debian
CVE-2024-47143P4MEDIUMCVSS 5.5fixed in linux 6.1.123-1 (bookworm)2024
CVE-2024-47143 [MEDIUM] CVE-2024-47143: linux - In the Linux kernel, the following vulnerability has been resolved: dma-debug: ...
In the Linux kernel, the following vulnerability has been resolved: dma-debug: fix a possible deadlock on radix_lock radix_lock() shouldn't be held while holding dma_hash_entry[idx].lock otherwise, there's a possible deadlock scenario when dma debug API is called holding rq_lock(): CPU0 CPU1 CPU2 dma_free_attrs() check_unmap() add_dma_entry() __schedule() //out (A)
debian
CVE-2024-26781P4MEDIUMCVSS 5.5fixed in linux 6.1.82-1 (bookworm)2024
CVE-2024-26781 [MEDIUM] CVE-2024-26781: linux - In the Linux kernel, the following vulnerability has been resolved: mptcp: fix ...
In the Linux kernel, the following vulnerability has been resolved: mptcp: fix possible deadlock in subflow diag Syzbot and Eric reported a lockdep splat in the subflow diag: WARNING: possible circular locking dependency detected 6.8.0-rc4-syzkaller-00212-g40b9385dd8e6 #0 Not tainted syz-executor.2/24141 is trying to acquire lock: ffff888045870130 (k-sk_lock-AF_INET
debian
CVE-2024-45029P4MEDIUMCVSS 5.5fixed in linux 6.1.112-1 (bookworm)2024
CVE-2024-45029 [MEDIUM] CVE-2024-45029: linux - In the Linux kernel, the following vulnerability has been resolved: i2c: tegra:...
In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: Do not mark ACPI devices as irq safe On ACPI machines, the tegra i2c module encounters an issue due to a mutex being called inside a spinlock. This leads to the following bug: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:585 ... Call trace: __might_sleep _
debian
CVE-2024-56612P4LOWCVSS 5.5fixed in linux 6.12.5-1 (forky)2024
CVE-2024-56612 [MEDIUM] CVE-2024-56612: linux - In the Linux kernel, the following vulnerability has been resolved: mm/gup: han...
In the Linux kernel, the following vulnerability has been resolved: mm/gup: handle NULL pages in unpin_user_pages() The recent addition of "pofs" (pages or folios) handling to gup has a flaw: it assumes that unpin_user_pages() handles NULL pages in the pages** array. That's not the case, as I discovered when I ran on a new configuration on my test machine. Fix this
debian
CVE-2024-56618P4LOWCVSS 5.5fixed in linux 6.12.5-1 (forky)2024
CVE-2024-56618 [MEDIUM] CVE-2024-56618: linux - In the Linux kernel, the following vulnerability has been resolved: pmdomain: i...
In the Linux kernel, the following vulnerability has been resolved: pmdomain: imx: gpcv2: Adjust delay after power up handshake The udelay(5) is not enough, sometimes below kernel panic still be triggered: [ 4.012973] Kernel panic - not syncing: Asynchronous SError Interrupt [ 4.012976] CPU: 2 UID: 0 PID: 186 Comm: (udev-worker) Not tainted 6.12.0-rc2-0.0.0-devel-00
debian
CVE-2025-38732P4MEDIUMCVSS 5.5fixed in linux 6.1.153-1 (bookworm)2025
CVE-2025-38732 [MEDIUM] CVE-2025-38732: linux - In the Linux kernel, the following vulnerability has been resolved: netfilter: ...
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_reject: don't leak dst refcount for loopback packets recent patches to add a WARN() when replacing skb dst entry found an old bug: WARNING: include/linux/skbuff.h:1165 skb_dst_check_unset include/linux/skbuff.h:1164 [inline] WARNING: include/linux/skbuff.h:1165 skb_dst_set include/linu
debian
CVE-2025-38700P4MEDIUMCVSS 5.5fixed in linux 6.1.153-1 (bookworm)2025
CVE-2025-38700 [MEDIUM] CVE-2025-38700: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: libis...
In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated In case of an ib_fast_reg_mr allocation failure during iSER setup, the machine hits a panic because iscsi_conn->dd_data is initialized unconditionally, even when no memory is allocated (dd_size == 0). This leads invalid point
debian
CVE-2025-21657P4LOWCVSS 5.5fixed in linux 6.12.10-1 (forky)2025
CVE-2025-21657 [MEDIUM] CVE-2025-21657: linux - In the Linux kernel, the following vulnerability has been resolved: sched_ext: ...
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Replace rq_lock() to raw_spin_rq_lock() in scx_ops_bypass() scx_ops_bypass() iterates all CPUs to re-enqueue all the scx tasks. For each CPU, it acquires a lock using rq_lock() regardless of whether a CPU is offline or the CPU is currently running a task in a higher scheduler class (e.g.,
debian
CVE-2025-21641P4LOWCVSS 5.5fixed in linux 6.12.10-1 (forky)2025
CVE-2025-21641 [MEDIUM] CVE-2025-21641: linux - In the Linux kernel, the following vulnerability has been resolved: mptcp: sysc...
In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy As mentioned in the previous commit, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can
debian