Debian Linux vulnerabilities

13,286 known vulnerabilities affecting debian/linux.

Total CVEs
13,286
CISA KEV
28
actively exploited
Public exploits
137
Exploited in wild
29
Severity breakdown
CRITICAL70HIGH2670MEDIUM6247LOW3072UNKNOWN1227

Vulnerabilities

Page 11 of 665
CVE-2026-23036LOWfixed in linux 6.18.8-1 (forky)2026
CVE-2026-23036 [LOW] CVE-2026-23036: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: rele... In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before iget_failed() in btrfs_read_locked_inode() In btrfs_read_locked_inode() if we fail to lookup the inode, we jump to the 'out' label with a path that has a read locked leaf and then we call iget_failed(). This can result in a ABBA deadlock, since iget_failed() triggers inode ev
debian
CVE-2026-23233LOWCVSS 7.8fixed in linux 6.18.13-1 (forky)2026
CVE-2026-23233 [HIGH] CVE-2026-23233: 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 avoid mapping wrong physical block for swapfile Xiaolong Guo reported a f2fs bug in bugzilla [1] [1] https://bugzilla.kernel.org/show_bug.cgi?id=220951 Quoted: "When using stress-ng's swap stress test on F2FS filesystem with kernel 6.6+, the system experiences data corruption leading to e
debian
CVE-2026-23355LOWfixed 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-2026-23467LOWfixed in linux 6.19.10-1 (forky)2026
CVE-2026-23467 [LOW] CVE-2026-23467: linux - In the Linux kernel, the following vulnerability has been resolved: drm/i915/dm... In the Linux kernel, the following vulnerability has been resolved: drm/i915/dmc: Fix an unlikely NULL pointer deference at probe intel_dmc_update_dc6_allowed_count() oopses when DMC hasn't been initialized, and dmc is thus NULL. That would be the case when the call path is intel_power_domains_init_hw() -> {skl,bxt,icl}_display_core_init() -> gen9_set_dc_state() -> int
debian
CVE-2026-23350LOWCVSS 7.8fixed in linux 6.19.8-1 (forky)2026
CVE-2026-23350 [HIGH] CVE-2026-23350: linux - In the Linux kernel, the following vulnerability has been resolved: drm/xe/queu... In the Linux kernel, the following vulnerability has been resolved: drm/xe/queue: Call fini on exec queue creation fail Every call to queue init should have a corresponding fini call. Skipping this would mean skipping removal of the queue from GuC list (which is part of guc_id allocation). A damaged queue stored in exec_queue_lookup list would lead to invalid memory r
debian
CVE-2026-23316LOWfixed in linux 6.19.8-1 (forky)2026
CVE-2026-23316 [LOW] CVE-2026-23316: linux - In the Linux kernel, the following vulnerability has been resolved: net: ipv4: ... In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix ARM64 alignment fault in multipath hash seed `struct sysctl_fib_multipath_hash_seed` contains two u32 fields (user_seed and mp_seed), making it an 8-byte structure with a 4-byte alignment requirement. In `fib_multipath_hash_from_keys()`, the code evaluates the entire struct atomically vi
debian
CVE-2026-23354LOWfixed in linux 6.19.8-1 (forky)2026
CVE-2026-23354 [LOW] CVE-2026-23354: linux - In the Linux kernel, the following vulnerability has been resolved: x86/fred: C... In the Linux kernel, the following vulnerability has been resolved: x86/fred: Correct speculative safety in fred_extint() array_index_nospec() is no use if the result gets spilled to the stack, as it makes the believed safe-under-speculation value subject to memory predictions. For all practical purposes, this means array_index_nospec() must be used in the expression t
debian
CVE-2026-23308LOWfixed in linux 6.19.8-1 (forky)2026
CVE-2026-23308 [LOW] CVE-2026-23308: linux - In the Linux kernel, the following vulnerability has been resolved: pinctrl: eq... In the Linux kernel, the following vulnerability has been resolved: pinctrl: equilibrium: fix warning trace on load The callback functions 'eqbr_irq_mask()' and 'eqbr_irq_ack()' are also called in the callback function 'eqbr_irq_mask_ack()'. This is done to avoid source code duplication. The problem, is that in the function 'eqbr_irq_mask()' also calles the gpiolib fun
debian
CVE-2026-23081LOWCVSS 5.5fixed in linux 6.18.8-1 (forky)2026
CVE-2026-23081 [MEDIUM] CVE-2026-23081: linux - In the Linux kernel, the following vulnerability has been resolved: net: phy: i... In the Linux kernel, the following vulnerability has been resolved: net: phy: intel-xway: fix OF node refcount leakage Automated review spotted am OF node reference count leakage when checking if the 'leds' child node exists. Call of_put_node() to correctly maintain the refcount. Scope: local bookworm: resolved bullseye: resolved forky: resolved (fixed in 6.18.8-1)
debian
CVE-2026-23106LOWCVSS 5.5fixed in linux 6.18.8-1 (forky)2026
CVE-2026-23106 [MEDIUM] CVE-2026-23106: linux - In the Linux kernel, the following vulnerability has been resolved: timekeeping... In the Linux kernel, the following vulnerability has been resolved: timekeeping: Adjust the leap state for the correct auxiliary timekeeper When __do_ajdtimex() was introduced to handle adjtimex for any timekeeper, this reference to tk_core was not updated. When called on an auxiliary timekeeper, the core timekeeper would be updated incorrectly. This gets caught by
debian
CVE-2026-23461LOWfixed in linux 6.19.10-1 (forky)2026
CVE-2026-23461 [LOW] CVE-2026-23461: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ... In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user After commit ab4eedb790ca ("Bluetooth: L2CAP: Fix corrupted list in hci_chan_del"), l2cap_conn_del() uses conn->lock to protect access to conn->users. However, l2cap_register_user() and l2cap_unregister_user() don't use conn->lock, creating
debian
CVE-2026-23175LOWCVSS 7.0fixed in linux 6.18.10-1 (forky)2026
CVE-2026-23175 [HIGH] CVE-2026-23175: linux - In the Linux kernel, the following vulnerability has been resolved: net: cpsw: ... In the Linux kernel, the following vulnerability has been resolved: net: cpsw: 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 my Be
debian
CVE-2026-22986LOWCVSS 4.7fixed in linux 6.18.8-1 (forky)2026
CVE-2026-22986 [MEDIUM] CVE-2026-22986: linux - In the Linux kernel, the following vulnerability has been resolved: gpiolib: fi... In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix race condition for gdev->srcu If two drivers were calling gpiochip_add_data_with_key(), one may be traversing the srcu-protected list in gpio_name_to_desc(), meanwhile other has just added its gdev in gpiodev_add_to_list_unlocked(). This creates a non-mutexed and non-protected timeframe
debian
CVE-2026-22988LOWCVSS 5.5fixed in linux 6.18.8-1 (forky)2026
CVE-2026-22988 [MEDIUM] CVE-2026-22988: linux - In the Linux kernel, the following vulnerability has been resolved: arp: do not... In the Linux kernel, the following vulnerability has been resolved: arp: do not assume dev_hard_header() does not change skb->head arp_create() is the only dev_hard_header() caller making assumption about skb->head being unchanged. A recent commit broke this assumption. Initialize @arp pointer after dev_hard_header() call. Scope: local bookworm: resolved bullseye: r
debian
CVE-2026-23173LOWCVSS 5.5fixed in linux 6.18.9-1 (forky)2026
CVE-2026-23173 [MEDIUM] CVE-2026-23173: 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: TC, delete flows only for existing peers When deleting TC steering flows, iterate only over actual devcom peers instead of assuming all possible ports exist. This avoids touching non-existent peers and ensures cleanup is limited to devices the driver is currently connected to. BUG: kernel
debian
CVE-2026-31401LOWfixed in linux 6.19.10-1 (forky)2026
CVE-2026-31401 [LOW] CVE-2026-31401: linux - In the Linux kernel, the following vulnerability has been resolved: HID: bpf: p... In the Linux kernel, the following vulnerability has been resolved: HID: bpf: prevent buffer overflow in hid_hw_request right now the returned value is considered to be always valid. However, when playing with HID-BPF, the return value can be arbitrary big, because it's the return value of dispatch_hid_bpf_raw_requests(), which calls the struct_ops and we have no guara
debian
CVE-2026-23161LOWCVSS 7.3fixed in linux 6.18.9-1 (forky)2026
CVE-2026-23161 [HIGH] CVE-2026-23161: linux - In the Linux kernel, the following vulnerability has been resolved: mm/shmem, s... In the Linux kernel, the following vulnerability has been resolved: mm/shmem, swap: fix race of truncate and swap entry split The helper for shmem swap freeing is not handling the order of swap entries correctly. It uses xa_cmpxchg_irq to erase the swap entry, but it gets the entry order before that using xa_get_order without lock protection, and it may get an outdate
debian
CVE-2026-22981LOWCVSS 5.5fixed in linux 6.18.8-1 (forky)2026
CVE-2026-22981 [MEDIUM] CVE-2026-22981: linux - In the Linux kernel, the following vulnerability has been resolved: idpf: detac... In the Linux kernel, the following vulnerability has been resolved: idpf: detach and close netdevs while handling a reset Protect the reset path from callbacks by setting the netdevs to detached state and close any netdevs in UP state until the reset handling has completed. During a reset, the driver will de-allocate resources for the vport, and there is no guarante
debian
CVE-2026-23225LOWCVSS 7.82026
CVE-2026-23225 [HIGH] CVE-2026-23225: linux - In the Linux kernel, the following vulnerability has been resolved: sched/mmcid... In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't assume CID is CPU owned on mode switch Shinichiro reported a KASAN UAF, which is actually an out of bounds access in the MMCID management code. CPU0 CPU1 T1 runs in userspace T0: fork(T4) -> Switch to per CPU CID mode fixup() set MM_CID_TRANSIT on T1/CPU1 T4 exit() T3 exit() T2 exit
debian
CVE-2026-23192LOWCVSS 7.8fixed in linux 6.18.10-1 (forky)2026
CVE-2026-23192 [HIGH] CVE-2026-23192: linux - In the Linux kernel, the following vulnerability has been resolved: linkwatch: ... In the Linux kernel, the following vulnerability has been resolved: linkwatch: use __dev_put() in callers to prevent UAF After linkwatch_do_dev() calls __dev_put() to release the linkwatch reference, the device refcount may drop to 1. At this point, netdev_run_todo() can proceed (since linkwatch_sync_dev() sees an empty list and returns without blocking), wait for the
debian
Debian Linux vulnerabilities | cvebase