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 368 of 632
CVE-2025-71081P4MEDIUMCVSS 5.5fixed in linux 6.1.162-1 (bookworm)2025
CVE-2025-71081 [MEDIUM] CVE-2025-71081: linux - In the Linux kernel, the following vulnerability has been resolved: ASoC: stm32...
In the Linux kernel, the following vulnerability has been resolved: ASoC: stm32: sai: fix OF node leak on probe The reference taken to the sync provider OF node when probing the platform device is currently only dropped if the set_sync() callback fails during DAI probe. Make sure to drop the reference on platform probe failures (e.g. probe deferral) and on driver un
debian
CVE-2025-38373P4LOWCVSS 5.5fixed in linux 6.12.37-1 (forky)2025
CVE-2025-38373 [MEDIUM] CVE-2025-38373: linux - In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fi...
In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix potential deadlock in MR deregistration The issue arises when kzalloc() is invoked while holding umem_mutex or any other lock acquired under umem_mutex. This is problematic because kzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke mmu_notifier_invalidate_range_start
debian
CVE-2025-71115P4LOWCVSS 5.5fixed in linux 6.18.3-1 (forky)2025
CVE-2025-71115 [MEDIUM] CVE-2025-71115: linux - In the Linux kernel, the following vulnerability has been resolved: um: init cp...
In the Linux kernel, the following vulnerability has been resolved: um: init cpu_tasks[] earlier This is currently done in uml_finishsetup(), but e.g. with KCOV enabled we'll crash because some init code can call into e.g. memparse(), which has coverage annotations, and then the checks in check_kcov_mode() crash because current is NULL. Simply initialize the cpu_tas
debian
CVE-2025-39767P4MEDIUMCVSS 5.5fixed in linux 6.16.5-1 (forky)2025
CVE-2025-39767 [MEDIUM] CVE-2025-39767: linux - In the Linux kernel, the following vulnerability has been resolved: LoongArch: ...
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Optimize module load time by optimizing PLT/GOT counting When enabling CONFIG_KASAN, CONFIG_PREEMPT_VOLUNTARY_BUILD and CONFIG_PREEMPT_VOLUNTARY at the same time, there will be soft deadlock, the relevant logs are as follows: rcu: INFO: rcu_sched self-detected stall on CPU ... Call Trace:
debian
CVE-2026-23127P4LOWCVSS 5.5fixed in linux 6.18.8-1 (forky)2026
CVE-2026-23127 [MEDIUM] CVE-2026-23127: linux - In the Linux kernel, the following vulnerability has been resolved: perf: Fix r...
In the Linux kernel, the following vulnerability has been resolved: perf: Fix refcount warning on event->mmap_count increment When calling refcount_inc(&event->mmap_count) inside perf_mmap_rb(), the following warning is triggered: refcount_t: addition on 0; use-after-free. WARNING: lib/refcount.c:25 PoC: struct perf_event_attr attr = {0}; int fd = syscall(__NR_perf_
debian
CVE-2025-39712P4LOWCVSS 5.5fixed in linux 6.16.5-1 (forky)2025
CVE-2025-39712 [MEDIUM] CVE-2025-39712: linux - In the Linux kernel, the following vulnerability has been resolved: media: mt9m...
In the Linux kernel, the following vulnerability has been resolved: media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval Getting / Setting the frame interval using the V4L2 subdev pad ops get_frame_interval/set_frame_interval causes a deadlock, as the subdev state is locked in the [1] but also in the driver itself. In [2] it's described that the cal
debian
CVE-2025-71139P4LOWCVSS 5.5fixed in linux 6.18.5-1 (forky)2025
CVE-2025-71139 [MEDIUM] CVE-2025-71139: linux - In the Linux kernel, the following vulnerability has been resolved: kernel/kexe...
In the Linux kernel, the following vulnerability has been resolved: kernel/kexec: fix IMA when allocation happens in CMA area *** Bug description *** When I tested kexec with the latest kernel, I ran into the following warning: [ 40.712410] ------------[ cut here ]------------ [ 40.712576] WARNING: CPU: 2 PID: 1562 at kernel/kexec_core.c:1001 kimage_map_segment+0x14
debian
CVE-2025-71181P4LOWCVSS 5.5fixed in linux 6.18.8-1 (forky)2025
CVE-2025-71181 [MEDIUM] CVE-2025-71181: linux - In the Linux kernel, the following vulnerability has been resolved: rust_binder...
In the Linux kernel, the following vulnerability has been resolved: rust_binder: remove spin_lock() in rust_shrink_free_page() When forward-porting Rust Binder to 6.18, I neglected to take commit fb56fdf8b9a2 ("mm/list_lru: split the lock to per-cgroup scope") into account, and apparently I did not end up running the shrinker callback when I sanity tested the driver
debian
CVE-2022-50341P4MEDIUMCVSS 5.5fixed in linux 6.1.4-1 (bookworm)2022
CVE-2022-50341 [MEDIUM] CVE-2022-50341: linux - In the Linux kernel, the following vulnerability has been resolved: cifs: fix o...
In the Linux kernel, the following vulnerability has been resolved: cifs: fix oops during encryption When running xfstests against Azure the following oops occurred on an arm64 system Unable to handle kernel write to read-only memory at virtual address ffff0001221cf000 Mem abort info: ESR = 0x9600004f EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA =
debian
CVE-2026-23203P4LOWCVSS 5.5fixed in linux 6.18.10-1 (forky)2026
CVE-2026-23203 [MEDIUM] CVE-2026-23203: linux - In the Linux kernel, the following vulnerability has been resolved: net: cpsw_n...
In the Linux kernel, the following vulnerability has been resolved: net: cpsw_new: Execute ndo_set_rx_mode callback in a work queue Commit 1767bb2d47b7 ("ipv6: mcast: Don't hold RTNL for IPV6_ADD_MEMBERSHIP and MCAST_JOIN_GROUP.") removed the RTNL lock for IPV6_ADD_MEMBERSHIP and MCAST_JOIN_GROUP operations. However, this change triggered the following call trace on
debian
CVE-2026-23152P4LOWCVSS 5.5fixed in linux 6.18.9-1 (forky)2026
CVE-2026-23152 [MEDIUM] CVE-2026-23152: 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: correctly decode TTLM with default link map TID-To-Link Mapping (TTLM) elements do not contain any link mapping presence indicator if a default mapping is used and parsing needs to be skipped. Note that access points should not explicitly report an advertised TTLM with a default mapp
debian
CVE-2025-39910P4MEDIUMCVSS 5.5fixed in linux 6.16.8-1 (forky)2025
CVE-2025-39910 [MEDIUM] CVE-2025-39910: linux - In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc,...
In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc() kasan_populate_vmalloc() and its helpers ignore the caller's gfp_mask and always allocate memory using the hardcoded GFP_KERNEL flag. This makes them inconsistent with vmalloc(), which was recently extended to support GFP_NOFS and GF
debian
CVE-2025-39769P4LOWCVSS 5.5fixed in linux 6.16.5-1 (forky)2025
CVE-2025-39769 [MEDIUM] CVE-2025-39769: linux - In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fi...
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix lockdep warning during rmmod The commit under the Fixes tag added a netdev_assert_locked() in bnxt_free_ntp_fltrs(). The lock should be held during normal run-time but the assert will be triggered (see below) during bnxt_remove_one() which should not need the lock. The netdev is already
debian
CVE-2025-39915P4LOWCVSS 5.5fixed in linux 6.16.8-1 (forky)2025
CVE-2025-39915 [MEDIUM] CVE-2025-39915: linux - In the Linux kernel, the following vulnerability has been resolved: net: phy: t...
In the Linux kernel, the following vulnerability has been resolved: net: phy: transfer phy_config_inband() locking responsibility to phylink Problem description =================== Lockdep reports a possible circular locking dependency (AB/BA) between &pl->state_mutex and &phy->lock, as follows. phylink_resolve() // acquires &pl->state_mutex -> phylink_major_config(
debian
CVE-2026-23188P4LOWCVSS 5.5fixed in linux 6.18.10-1 (forky)2026
CVE-2026-23188 [MEDIUM] CVE-2026-23188: linux - In the Linux kernel, the following vulnerability has been resolved: net: usb: r...
In the Linux kernel, the following vulnerability has been resolved: net: usb: r8152: fix resume reset deadlock rtl8152 can trigger device reset during reset which potentially can result in a deadlock: **** DPM device timeout after 10 seconds; 15 seconds until panic **** Call Trace: schedule+0x483/0x1370 schedule_preempt_disabled+0x15/0x30 __mutex_lock_common+0x1fd/0
debian
CVE-2025-38223P4LOWCVSS 5.5fixed in linux 6.12.35-1 (forky)2025
CVE-2025-38223 [MEDIUM] CVE-2025-38223: linux - In the Linux kernel, the following vulnerability has been resolved: ceph: avoid...
In the Linux kernel, the following vulnerability has been resolved: ceph: avoid kernel BUG for encrypted inode with unaligned file size The generic/397 test hits a BUG_ON for the case of encrypted inode with unaligned file size (for example, 33K or 1K): [ 877.737811] run fstests generic/397 at 2025-01-03 12:34:40 [ 877.875761] libceph: mon0 (2)127.0.0.1:40674 sessio
debian
CVE-2026-23186P4LOWCVSS 5.5fixed in linux 6.18.10-1 (forky)2026
CVE-2026-23186 [MEDIUM] CVE-2026-23186: linux - In the Linux kernel, the following vulnerability has been resolved: hwmon: (acp...
In the Linux kernel, the following vulnerability has been resolved: hwmon: (acpi_power_meter) Fix deadlocks related to acpi_power_meter_notify() The acpi_power_meter driver's .notify() callback function, acpi_power_meter_notify(), calls hwmon_device_unregister() under a lock that is also acquired by callbacks in sysfs attributes of the device being unregistered whic
debian
CVE-2026-23130P4LOWCVSS 5.5fixed in linux 6.18.8-1 (forky)2026
CVE-2026-23130 [MEDIUM] CVE-2026-23130: 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 dead lock while flushing management frames Commit [1] converted the management transmission work item into a wiphy work. Since a wiphy work can only run under wiphy lock protection, a race condition happens in below scenario: 1. a management frame is queued for transmission. 2. ath
debian
CVE-2012-2119P4MEDIUMCVSS 5.2fixed in linux 3.2.20-1 (bookworm)2012
CVE-2012-2119 [MEDIUM] CVE-2012-2119: linux - Buffer overflow in the macvtap device driver in the Linux kernel before 3.4.5, w...
Buffer overflow in the macvtap device driver in the Linux kernel before 3.4.5, when running in certain configurations, allows privileged KVM guest users to cause a denial of service (crash) via a long descriptor with a long vector length.
Scope: local
bookworm: resolved (fixed in 3.2.20-1)
bullseye: resolved (fixed in 3.2.20-1)
forky: resolved (fixed in 3.2.20-1)
sid:
debian
CVE-2026-23222P4HIGHCVSS 7.8fixed in linux 6.1.164-1 (bookworm)2026
CVE-2026-23222 [HIGH] CVE-2026-23222: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: oma...
In the Linux kernel, the following vulnerability has been resolved: crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly The existing allocation of scatterlists in omap_crypto_copy_sg_lists() was allocating an array of scatterlist pointers, not scatterlist objects, resulting in a 4x too small allocation. Use sizeof(*new_sg) to get the correct object s
debian