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 600 of 632
CVE-2024-56540P4LOWCVSS 4.7fixed in linux 6.12.3-1 (forky)2024
CVE-2024-56540 [MEDIUM] CVE-2024-56540: linux - In the Linux kernel, the following vulnerability has been resolved: accel/ivpu:...
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Prevent recovery invocation during probe and resume Refactor IPC send and receive functions to allow correct handling of operations that should not trigger a recovery process. Expose ivpu_send_receive_internal(), which is now utilized by the D0i3 entry, DCT initialization, and HWS initia
debian
CVE-2023-52505P4MEDIUMCVSS 4.7fixed in linux 6.1.64-1 (bookworm)2023
CVE-2023-52505 [MEDIUM] CVE-2023-52505: linux - In the Linux kernel, the following vulnerability has been resolved: phy: lynx-2...
In the Linux kernel, the following vulnerability has been resolved: phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers The protocol converter configuration registers PCC8, PCCC, PCCD (implemented by the driver), as well as others, control protocol converters from multiple lanes (each represented as a different struct phy). So, if there
debian
CVE-2022-48921P4MEDIUMCVSS 4.7fixed in linux 5.16.14-1 (bookworm)2022
CVE-2022-48921 [MEDIUM] CVE-2022-48921: linux - In the Linux kernel, the following vulnerability has been resolved: sched/fair:...
In the Linux kernel, the following vulnerability has been resolved: sched/fair: Fix fault in reweight_entity Syzbot found a GPF in reweight_entity. This has been bisected to commit 4ef0c5c6b5ba ("kernel/sched: Fix sched_fork() access an invalid sched_task_group") There is a race between sched_post_fork() and setpriority(PRIO_PGRP) within a thread group that causes a
debian
CVE-2025-21701P4MEDIUMCVSS 4.7fixed in linux 6.1.129-1 (bookworm)2025
CVE-2025-21701 [MEDIUM] CVE-2025-21701: linux - In the Linux kernel, the following vulnerability has been resolved: net: avoid ...
In the Linux kernel, the following vulnerability has been resolved: net: avoid race between device unregistration and ethnl ops The following trace can be seen if a device is being unregistered while its number of channels are being modified. DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 3 PID: 3754 at kernel/locking/mutex.c:564 __mutex_lock+0xc8a/0x1120 CP
debian
CVE-2024-36927P4MEDIUMCVSS 4.7fixed in linux 6.1.140-1 (bookworm)2024
CVE-2024-36927 [MEDIUM] CVE-2024-36927: linux - In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix u...
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix uninit-value access in __ip_make_skb() KMSAN reported uninit-value access in __ip_make_skb() [1]. __ip_make_skb() tests HDRINCL to know if the skb has icmphdr. However, HDRINCL can cause a race condition. If calling setsockopt(2) with IP_HDRINCL changes HDRINCL while __ip_make_skb() is run
debian
CVE-2024-39296P4LOWCVSS 4.7fixed in linux 6.9.7-1 (forky)2024
CVE-2024-39296 [MEDIUM] CVE-2024-39296: linux - In the Linux kernel, the following vulnerability has been resolved: bonding: fi...
In the Linux kernel, the following vulnerability has been resolved: bonding: fix oops during rmmod "rmmod bonding" causes an oops ever since commit cc317ea3d927 ("bonding: remove redundant NULL check in debugfs function"). Here are the relevant functions being called: bonding_exit() bond_destroy_debugfs() debugfs_remove_recursive(bonding_debug_root); bonding_debug_r
debian
CVE-2024-50135P4MEDIUMCVSS 4.7fixed in linux 6.11.6-1 (forky)2024
CVE-2024-50135 [MEDIUM] CVE-2024-50135: linux - In the Linux kernel, the following vulnerability has been resolved: nvme-pci: f...
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61
debian
CVE-2024-56568P4MEDIUMCVSS 4.7fixed in linux 6.1.123-1 (bookworm)2024
CVE-2024-56568 [MEDIUM] CVE-2024-56568: linux - In the Linux kernel, the following vulnerability has been resolved: iommu/arm-s...
In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu: Defer probe of clients after smmu device bound Null pointer dereference occurs due to a race between smmu driver probe and client driver probe, when of_dma_configure() for client is called after the iommu_device_register() for smmu driver probe has executed but before the driver_boun
debian
CVE-2024-47660P4MEDIUMCVSS 4.7fixed in linux 6.1.112-1 (bookworm)2024
CVE-2024-47660 [MEDIUM] CVE-2024-47660: linux - In the Linux kernel, the following vulnerability has been resolved: fsnotify: c...
In the Linux kernel, the following vulnerability has been resolved: fsnotify: clear PARENT_WATCHED flags lazily In some setups directories can have many (usually negative) dentries. Hence __fsnotify_update_child_dentry_flags() function can take a significant amount of time. Since the bulk of this function happens under inode->i_lock this causes a significant content
debian
CVE-2024-36024P4MEDIUMCVSS 4.7fixed in linux 6.8.9-1 (forky)2024
CVE-2024-36024 [MEDIUM] CVE-2024-36024: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amd/dis...
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Disable idle reallow as part of command/gpint execution [Why] Workaroud for a race condition where DMCUB is in the process of committing to IPS1 during the handshake causing us to miss the transition into IPS2 and touch the INBOX1 RPTR causing a HW hang. [How] Disable the reallow to
debian
CVE-2022-49814P4MEDIUMCVSS 4.7fixed in linux 6.0.10-1 (bookworm)2022
CVE-2022-49814 [MEDIUM] CVE-2022-49814: linux - In the Linux kernel, the following vulnerability has been resolved: kcm: close ...
In the Linux kernel, the following vulnerability has been resolved: kcm: close race conditions on sk_receive_queue sk->sk_receive_queue is protected by skb queue lock, but for KCM sockets its RX path takes mux->rx_lock to protect more than just skb queue. However, kcm_recvmsg() still only grabs the skb queue lock, so race conditions still exist. We can teach kcm_rec
debian
CVE-2022-48989P4MEDIUMCVSS 4.7fixed in linux 6.1.4-1 (bookworm)2022
CVE-2022-48989 [MEDIUM] CVE-2022-48989: linux - In the Linux kernel, the following vulnerability has been resolved: fscache: Fi...
In the Linux kernel, the following vulnerability has been resolved: fscache: Fix oops due to race with cookie_lru and use_cookie If a cookie expires from the LRU and the LRU_DISCARD flag is set, but the state machine has not run yet, it's possible another thread can call fscache_use_cookie and begin to use it. When the cookie_worker finally runs, it will see the LRU
debian
CVE-2024-42107P4MEDIUMCVSS 4.7fixed in linux 6.9.9-1 (forky)2024
CVE-2024-42107 [MEDIUM] CVE-2024-42107: linux - In the Linux kernel, the following vulnerability has been resolved: ice: Don't ...
In the Linux kernel, the following vulnerability has been resolved: ice: Don't process extts if PTP is disabled The ice_ptp_extts_event() function can race with ice_ptp_release() and result in a NULL pointer dereference which leads to a kernel panic. Panic occurs because the ice_ptp_extts_event() function calls ptp_clock_event() with a NULL pointer. The ice driver h
debian
CVE-2022-49733P4MEDIUMCVSS 4.7fixed in linux 5.19.11-1 (bookworm)2022
CVE-2022-49733 [MEDIUM] CVE-2022-49733: linux - In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: ...
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC There is a small race window at snd_pcm_oss_sync() that is called from OSS PCM SNDCTL_DSP_SYNC ioctl; namely the function calls snd_pcm_oss_make_ready() at first, then takes the params_lock mutex for the rest. When the stream is set up again by another thr
debian
CVE-2025-38515P4MEDIUMCVSS 4.7fixed in linux 6.1.147-1 (bookworm)2025
CVE-2025-38515 [MEDIUM] CVE-2025-38515: linux - In the Linux kernel, the following vulnerability has been resolved: drm/sched: ...
In the Linux kernel, the following vulnerability has been resolved: drm/sched: Increment job count before swapping tail spsc queue A small race exists between spsc_queue_push and the run-job worker, in which spsc_queue_push may return not-first while the run-job worker has already idled due to the job count being zero. If this race occurs, job scheduling stops, lead
debian
CVE-2025-39697P4MEDIUMCVSS 4.7fixed in linux 6.1.153-1 (bookworm)2025
CVE-2025-39697 [MEDIUM] CVE-2025-39697: linux - In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a ...
In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a race when updating an existing write After nfs_lock_and_join_requests() tests for whether the request is still attached to the mapping, nothing prevents a call to nfs_inode_remove_request() from succeeding until we actually lock the page group. The reason is that whoever called nfs_inode_
debian
CVE-2021-47577P4MEDIUMCVSS 4.7fixed in linux 5.15.15-1 (bookworm)2021
CVE-2021-47577 [MEDIUM] CVE-2021-47577: linux - In the Linux kernel, the following vulnerability has been resolved: io-wq: chec...
In the Linux kernel, the following vulnerability has been resolved: io-wq: check for wq exit after adding new worker task_work We check IO_WQ_BIT_EXIT before attempting to create a new worker, and wq exit cancels pending work if we have any. But it's possible to have a race between the two, where creation checks exit finding it not set, but we're in the process of e
debian
CVE-2025-21943P4MEDIUMCVSS 4.7fixed in linux 6.1.133-1 (bookworm)2025
CVE-2025-21943 [MEDIUM] CVE-2025-21943: linux - In the Linux kernel, the following vulnerability has been resolved: gpio: aggre...
In the Linux kernel, the following vulnerability has been resolved: gpio: aggregator: protect driver attr handlers against module unload Both new_device_store and delete_device_store touch module global resources (e.g. gpio_aggregator_lock). To prevent race conditions with module unload, a reference needs to be held. Add try_module_get() in these handlers. For new_d
debian
CVE-2024-38306P4LOWCVSS 4.7fixed in linux 6.9.7-1 (forky)2024
CVE-2024-38306 [MEDIUM] CVE-2024-38306: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: prot...
In the Linux kernel, the following vulnerability has been resolved: btrfs: protect folio::private when attaching extent buffer folios [BUG] Since v6.8 there are rare kernel crashes reported by various people, the common factor is bad page status error messages like this: BUG: Bad page state in process kswapd0 pfn:d6e840 page: refcount:0 mapcount:0 mapping:0000000075
debian
CVE-2022-49655P4MEDIUMCVSS 4.7fixed in linux 5.18.14-1 (bookworm)2022
CVE-2022-49655 [MEDIUM] CVE-2022-49655: linux - In the Linux kernel, the following vulnerability has been resolved: fscache: Fi...
In the Linux kernel, the following vulnerability has been resolved: fscache: Fix invalidation/lookup race If an NFS file is opened for writing and closed, fscache_invalidate() will be asked to invalidate the file - however, if the cookie is in the LOOKING_UP state (or the CREATING state), then request to invalidate doesn't get recorded for fscache_cookie_state_machi
debian