CVE-2023-53626
In the Linux kernel, the following vulnerability has been resolved: ext4: fix possible double unlock when moving a directory
CVSS
7.8
Alto
EPSS
0.2%
p10
KEV
—
Exploit Today
3
0-100
Publicado: 7 oct 2025 · Última mod.: 4 ago 2026 · CWE-415
0.2%EPSS · 30 días0.2%
2026-07-152026-08-12
In the Linux kernel, the following vulnerability has been resolved: ext4: fix possible double unlock when moving a directory
- git.kernel.orghttps://git.kernel.org/stable/c/020166bc6669ca9fb267ebd96bd88c4fb64a5d46
- git.kernel.orghttps://git.kernel.org/stable/c/1c93c42c7bb23057bde8a0a2ab834927ff64d20c
- git.kernel.orghttps://git.kernel.org/stable/c/43ce288ab5d7274a4a141d7f5e3ed2ab7b41f8a2
- git.kernel.orghttps://git.kernel.org/stable/c/70e42feab2e20618ddd0cbfc4ab4b08628236ecd
- git.kernel.orghttps://git.kernel.org/stable/c/c16cbd8233d6c58fc488545393e49b5d55729990
- git.kernel.orghttps://git.kernel.org/stable/c/e71eb4dca41f0f36823724ced0406bb2dbdd5506
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-186635.9 MED32.7%
——10A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function frees the parsed controls array on the Session Tracking critical-control rejection path without clearing the SLAPI_REQCONTROLS pblock slot. Operation teardown then frees the same pointer again, causing a double-free. An unauthenticated remote attacker can trigger this with a single BIND request carrying a critical Session Tracking control, resulting in heap corruption and potential denial of service.1dCVE-2026-657807.0 ALT10.6%
——3Double free in Windows Autopilot allows an authorized attacker to elevate privileges locally.23hCVE-2026-628898.1 ALT44.3%
——13Double free in Windows Secure Socket Tunneling Protocol (SSTP) allows an unauthorized attacker to execute code over a network.23hCVE-2026-627667.0 ALT69.4%
——21Double free in Windows Kerberos allows an authorized attacker to elevate privileges locally.23hCVE-2026-613667.0 ALT16.7%
——5Double free in Windows Network Connection Broker allows an authorized attacker to elevate privileges locally.2dCVE-2026-118945.9 MED6.7%
——2The Realtek BEE Bluetooth HCI driver's send callback, bt_hci_bee_send() in drivers/bluetooth/hci/hci_bee.c, violated the bt_hci_driver_api buffer-ownership contract. That contract requires the driver to consume (unref) the transmit net_buf only on success; on an error return the host caller retains ownership and unrefs the buffer itself. The pre-fix code routed all error paths through a shared cleanup label that unconditionally called net_buf_unref(buf) before returning the error code.
Because the host TX paths (in subsys/bluetooth/host/hci_core.c) unref the buffer again after send() returns an error, the buffer is freed twice: the driver returns it to its net_buf pool and the host then unrefs the already-freed buffer, corrupting the shared pool / underflowing the reference count (CWE-415). The same error branch additionally dereferenced buf->len inside a LOG_ERR call after the buffer had already been unref'd, a read of freed memory (CWE-416) that is compiled in at the default error log level.
The failing edges are reached when the controller's host-to-controller buffer allocation fails or the controller send fails (resource-exhaustion / IO conditions). A remote Bluetooth peer can push the device toward these conditions indirectly by driving heavy host transmit activity, at which point the double-free corrupts the host net_buf pool and most likely crashes the device, with residual potential for further memory corruption. The impact is confined to builds using this specific Realtek BEE HCI driver.
The fix returns early from each error path without unreffing and unrefs the buffer only on the success path, restoring the ownership contract and eliminating both the double-free and the use-after-free read.2d