CVE-20XX-?
agent?

Denial of service CVEs.

Published CVEs classified as denial of service, ranked by exploit odds.

61 CVEs · updated 2026-11-19 11:54 UTC

Reset all
  1. CVE-2026-93666

    The Bluetooth Classic SDP client built its outgoing request PDUs with bt_sdp_create_pdu(), which allocates from the sdp_pool net-buf pool with a K_FOREVER timeout and no failure handling, in sdp_client_ss_search(), sdp_client_sa_search() and sdp_client_ssa_search() in subsys/bluetooth/host/classic/sdp.c. All of these run on the Bluetooth workqueue bt_workq (via sdp_client_work_handler(), the L2CAP sdp_client_connected() callback, or the continuation-state follow-up from a received response), which is the same single thread that dispatches incoming HCI ACL and event traffic, drives L2CAP, and performs connection and channel teardown. sdp_pool holds only CONFIG_BT_MAX_CONN buffers (one by default) and is shared with the SDP server role. An unauthenticated peer within BR/EDR range can drive both halves of the trigger. The SDP L2CAP server is registered at BT_SECURITY_L0, so any inbound SDP request makes the device allocate the pool's buffer for a response, which is held until the controller has transmitted it. The same peer can then cause a client request to be issued while the pool is empty: in-tree profiles start SDP discovery from inbound connection callbacks (for example hfp_hf_accept() calls bt_sdp_discover() through hfp_hf_create(), and hfp_ag.c mirrors this), and a peer acting as an SDP server can force repeated client requests by answering with partial responses carrying continuation state. With the pool empty, the allocation blocks uninterruptibly and freezes the entire Bluetooth host. The stall becomes permanent when the release of the outstanding buffer itself depends on the blocked workqueue: if the link carrying the queued PDU is dropped or stalls, hci_disconn_complete() and the L2CAP channel cleanup that purges the channel TX queue are themselves bt_workq work items, so the buffer is never returned. The result is an unrecoverable denial of service of all Bluetooth functionality until reboot; there is no memory-safety, confidentiality or integrity impact. The fix allocates client PDUs with K_NO_WAIT via a new sdp_client_create_pdu(), propagates -ENOBUFS, parks the session on a new SDP_CLIENT_FLAG_WAIT_FOR_TX_BUF flag, and adds an sdp_pool destructor that re-submits the SDP client worker when a buffer becomes available. Note that the SDP server role still allocated from the same pool with K_FOREVER at this commit; that path was addressed separately.

    Denial of service Device

    5.3 MEDIUM 0.1% exploit odds Fix listed
  2. CVE-2026-101173

    DoS vulnerability in the DSoftBus module. Impact: Successful exploitation of this vulnerability may affect availability.

    Denial of service Device

    6.5 MEDIUM 0.1% exploit odds No fix listed
  3. CVE-2026-68990

    In the Samsung Exynos H-Arx DRM plugin, improper input validation during buffer operations can cause memory corruption, potentially leading to denial of service or privilege escalation.

    Denial of service Device

    7.8 HIGH 0.1% exploit odds No fix listed
  4. CVE-2026-48175

    Processing a malformed RRC message leads to an out-of-bounds read, resulting in a denial-of-service condition.

    Denial of service Device

    5.5 MEDIUM 0.1% exploit odds No fix listed
  5. CVE-2026-108838

    IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a local attacker to cause a denial of service due to uncontrolled resource consumption.

    Denial of service Device IBM Agentics

    3.3 LOW 0.1% exploit odds Fix listed
  6. CVE-2026-59047

    In multiple locations, there is a possible denial of service due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  7. CVE-2026-59021

    In multiple locations, there is a possible denial of service due to improper input validation. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  8. CVE-2026-59031

    In InputDispatcher::flushSensor of InputDispatcher.cpp, there is a possible denial of service due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  9. CVE-2026-59008

    In setApplicationRestrictions of DevicePolicyManagerService.java, there is a possible denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  10. CVE-2026-59020

    In removeUserData of DevicePolicyManagerService.java, there is a possible denial of service due to a race condition. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    5.9 MEDIUM 0.1% exploit odds Fix listed
  11. CVE-2026-130659

    ImageMagick before 7.1.2-35 contains a policy bypass vulnerability in various coders that allows attackers to allocate excessive memory by supplying images with many profiles. Attackers can craft images containing a high number of embedded profiles to exhaust memory and cause denial of service, bypassing security policy limits.

    Denial of service Device ImageMagick

    6.9 MEDIUM Fix listed

A list of CVEs whose flaw type is denial of service, sorted by how likely they are to be exploited (EPSS). Classification uses the CWE weakness id where present, and a small local model otherwise.