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 628 of 632
CVE-2024-50092P4LOWCVSS 3.3fixed in linux 6.11.4-1 (forky)2024
CVE-2024-50092 [LOW] CVE-2024-50092: linux - In the Linux kernel, the following vulnerability has been resolved: net: netcon...
In the Linux kernel, the following vulnerability has been resolved: net: netconsole: fix wrong warning A warning is triggered when there is insufficient space in the buffer for userdata. However, this is not an issue since userdata will be sent in the next iteration. Current warning message: ------------[ cut here ]------------ WARNING: CPU: 13 PID: 3013042 at drivers/
debian
CVE-2022-48937P4LOWCVSS 3.3fixed in linux 5.16.12-1 (bookworm)2022
CVE-2022-48937 [LOW] CVE-2022-48937: linux - In the Linux kernel, the following vulnerability has been resolved: io_uring: a...
In the Linux kernel, the following vulnerability has been resolved: io_uring: add a schedule point in io_add_buffers() Looping ~65535 times doing kmalloc() calls can trigger soft lockups, especially with DEBUG features (like KASAN). [ 253.536212] watchdog: BUG: soft lockup - CPU#64 stuck for 26s! [b219417889:12575] [ 253.544433] Modules linked in: vfat fat i2c_mux_pca9
debian
CVE-2026-22978P4LOWCVSS 3.3fixed in linux 6.1.162-1 (bookworm)2026
CVE-2026-22978 [LOW] CVE-2026-22978: linux - In the Linux kernel, the following vulnerability has been resolved: wifi: avoid...
In the Linux kernel, the following vulnerability has been resolved: wifi: avoid kernel-infoleak from struct iw_point struct iw_point has a 32bit hole on 64bit arches. struct iw_point { void __user *pointer; /* Pointer to the data (in user space) */ __u16 length; /* number of fields or size in bytes */ __u16 flags; /* Optional params */ }; Make sure to zero the structur
debian
CVE-2024-36331P4LOWCVSS 3.2fixed in linux 6.1.148-1 (bookworm)2024
CVE-2024-36331 [LOW] CVE-2024-36331: linux - Improper initialization of CPU cache memory could allow a privileged attacker wi...
Improper initialization of CPU cache memory could allow a privileged attacker with hypervisor access to overwrite SEV-SNP guest memory resulting in loss of data integrity.
Scope: local
bookworm: resolved (fixed in 6.1.148-1)
bullseye: open
forky: resolved (fixed in 6.16.3-1)
sid: resolved (fixed in 6.16.3-1)
trixie: resolved (fixed in 6.12.43-1)
debian
CVE-2014-0181P4LOWCVSS 2.1fixed in linux 3.14.9-1 (bookworm)2014
CVE-2014-0181 [LOW] CVE-2014-0181: linux - The Netlink implementation in the Linux kernel through 3.14.1 does not provide a...
The Netlink implementation in the Linux kernel through 3.14.1 does not provide a mechanism for authorizing socket operations based on the opener of a socket, which allows local users to bypass intended access restrictions and modify network configurations by using a Netlink socket for the (1) stdout or (2) stderr of a setuid program.
Scope: local
bookworm: resolved (fixe
debian
CVE-2012-2313P4LOWCVSS 1.2fixed in linux 3.2.19-1 (bookworm)2012
CVE-2012-2313 [LOW] CVE-2012-2313: linux - The rio_ioctl function in drivers/net/ethernet/dlink/dl2k.c in the Linux kernel ...
The rio_ioctl function in drivers/net/ethernet/dlink/dl2k.c in the Linux kernel before 3.3.7 does not restrict access to the SIOCSMIIREG command, which allows local users to write data to an Ethernet adapter via an ioctl call.
Scope: local
bookworm: resolved (fixed in 3.2.19-1)
bullseye: resolved (fixed in 3.2.19-1)
forky: resolved (fixed in 3.2.19-1)
sid: resolved (fixe
debian
CVE-2013-2929P4LOWCVSS 3.3fixed in linux 3.11.10-1 (bookworm)2013
CVE-2013-2929 [LOW] CVE-2013-2929: linux - The Linux kernel before 3.12.2 does not properly use the get_dumpable function, ...
The Linux kernel before 3.12.2 does not properly use the get_dumpable function, which allows local users to bypass intended ptrace restrictions or obtain sensitive information from IA64 scratch registers via a crafted application, related to kernel/ptrace.c and arch/ia64/include/asm/processor.h.
Scope: local
bookworm: resolved (fixed in 3.11.10-1)
bullseye: resolved (fix
debian
CVE-2014-3917P4LOWCVSS 3.3fixed in linux 3.14.7-1 (bookworm)2014
CVE-2014-3917 [LOW] CVE-2014-3917: linux - kernel/auditsc.c in the Linux kernel through 3.14.5, when CONFIG_AUDITSYSCALL is...
kernel/auditsc.c in the Linux kernel through 3.14.5, when CONFIG_AUDITSYSCALL is enabled with certain syscall rules, allows local users to obtain potentially sensitive single-bit values from kernel memory or cause a denial of service (OOPS) via a large value of a syscall number.
Scope: local
bookworm: resolved (fixed in 3.14.7-1)
bullseye: resolved (fixed in 3.14.7-1)
fo
debian
CVE-2024-41027P4LOWCVSS 3.3fixed in linux 6.1.106-1 (bookworm)2024
CVE-2024-41027 [LOW] CVE-2024-41027: linux - In the Linux kernel, the following vulnerability has been resolved: Fix userfau...
In the Linux kernel, the following vulnerability has been resolved: Fix userfaultfd_api to return EINVAL as expected Currently if we request a feature that is not set in the Kernel config we fail silently and return all the available features. However, the man page indicates we should return an EINVAL. We need to fix this issue since we can end up with a Kernel warning
debian
CVE-2024-47738P4LOWCVSS 3.3fixed in linux 6.1.115-1 (bookworm)2024
CVE-2024-47738 [LOW] CVE-2024-47738: 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: don't use rate mask for offchannel TX either Like the commit ab9177d83c04 ("wifi: mac80211: don't use rate mask for scanning"), ignore incorrect settings to avoid no supported rate warning reported by syzbot. The syzbot did bisect and found cause is commit 9df66d5b9f45 ("cfg80211: fix d
debian
CVE-2024-35935P4LOWCVSS 3.3fixed in linux 6.1.90-1 (bookworm)2024
CVE-2024-35935 [LOW] CVE-2024-35935: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: send...
In the Linux kernel, the following vulnerability has been resolved: btrfs: send: handle path ref underflow in header iterate_inode_ref() Change BUG_ON to proper error handling if building the path buffer fails. The pointers are not printed so we don't accidentally leak kernel addresses.
Scope: local
bookworm: resolved (fixed in 6.1.90-1)
bullseye: resolved (fixed in 5.
debian
CVE-2024-50057P4LOWCVSS 3.3fixed in linux 6.11.4-1 (forky)2024
CVE-2024-50057 [LOW] CVE-2024-50057: linux - In the Linux kernel, the following vulnerability has been resolved: usb: typec:...
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tipd: Free IRQ only if it was requested before In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client->irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_i
debian
CVE-2022-48852P4LOWCVSS 3.3fixed in linux 5.16.18-1 (bookworm)2022
CVE-2022-48852 [LOW] CVE-2022-48852: linux - In the Linux kernel, the following vulnerability has been resolved: drm/vc4: hd...
In the Linux kernel, the following vulnerability has been resolved: drm/vc4: hdmi: Unregister codec device on unbind On bind we will register the HDMI codec device but we don't unregister it on unbind, leading to a device leakage. Unregister our device at unbind.
Scope: local
bookworm: resolved (fixed in 5.16.18-1)
bullseye: resolved
forky: resolved (fixed in 5.16.18-1
debian
CVE-2022-48668P4LOWCVSS 3.3fixed in linux 6.0.2-1 (bookworm)2022
CVE-2022-48668 [LOW] CVE-2022-48668: linux - In the Linux kernel, the following vulnerability has been resolved: smb3: fix t...
In the Linux kernel, the following vulnerability has been resolved: smb3: fix temporary data corruption in collapse range collapse range doesn't discard the affected cached region so can risk temporarily corrupting the file data. This fixes xfstest generic/031 I also decided to merge a minor cleanup to this into the same patch (avoiding rereading inode size repeatedly
debian
CVE-2022-48667P4LOWCVSS 3.3fixed in linux 6.0.2-1 (bookworm)2022
CVE-2022-48667 [LOW] CVE-2022-48667: linux - In the Linux kernel, the following vulnerability has been resolved: smb3: fix t...
In the Linux kernel, the following vulnerability has been resolved: smb3: fix temporary data corruption in insert range insert range doesn't discard the affected cached region so can risk temporarily corrupting file data. Also includes some minor cleanup (avoiding rereading inode size repeatedly unnecessarily) to make it clearer.
Scope: local
bookworm: resolved (fixed
debian
CVE-2024-42249P4LOWCVSS 3.3fixed in linux 6.9.10-1 (forky)2024
CVE-2024-42249 [LOW] CVE-2024-42249: linux - In the Linux kernel, the following vulnerability has been resolved: spi: don't ...
In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message() in spi_async() is wrong because the message is likely to be in the queue and not transferred yet. This can corrupt the message while it is being used by the controller driver. spi_maybe_unoptimize_message() is already c
debian
CVE-2024-42233P4LOWCVSS 3.3fixed in linux 6.9.10-1 (forky)2024
CVE-2024-42233 [LOW] CVE-2024-42233: linux - In the Linux kernel, the following vulnerability has been resolved: filemap: re...
In the Linux kernel, the following vulnerability has been resolved: filemap: replace pte_offset_map() with pte_offset_map_nolock() The vmf->ptl in filemap_fault_recheck_pte_none() is still set from handle_pte_fault(). But at the same time, we did a pte_unmap(vmf->pte). After a pte_unmap(vmf->pte) unmap and rcu_read_unlock(), the page table may be racily changed and vmf
debian
CVE-2021-47089P4LOWCVSS 3.3fixed in linux 5.15.15-1 (bookworm)2021
CVE-2021-47089 [LOW] CVE-2021-47089: linux - In the Linux kernel, the following vulnerability has been resolved: kfence: fix...
In the Linux kernel, the following vulnerability has been resolved: kfence: fix memory leak when cat kfence objects Hulk robot reported a kmemleak problem: unreferenced object 0xffff93d1d8cc02e8 (size 248): comm "cat", pid 23327, jiffies 4624670141 (age 495992.217s) hex dump (first 32 bytes): 00 40 85 19 d4 93 ff ff 00 10 00 00 00 00 00 00 .@.............. 00 00 00 00
debian
CVE-2024-50044P4LOWCVSS 3.3fixed in linux 6.1.115-1 (bookworm)2024
CVE-2024-50044 [LOW] CVE-2024-50044: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ...
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change rfcomm_sk_state_change attempts to use sock_lock so it must never be called with it locked but rfcomm_sock_ioctl always attempt to lock it causing the following trace: ====================================================== WARNING: poss
debian
CVE-2024-57898P4LOWCVSS 3.3fixed in linux 6.12.9-1 (forky)2024
CVE-2024-57898 [LOW] CVE-2024-57898: linux - In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80...
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: clear link ID from bitmap during link delete after clean up Currently, during link deletion, the link ID is first removed from the valid_links bitmap before performing any clean-up operations. However, some functions require the link ID to remain in the valid_links bitmap. One such exam
debian