CVE-2026-74513

In the Linux kernel, the following vulnerability has been resolved: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister dibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb() look up the dmb_node under dmb_ht_lock, drop the lock and only then operate on the node's refcount. Nothing keeps the node alive across that window: __dibs_lo_unregister_dmb() removes the node from the hash table under the write lock and immediately frees it. A concurrent final put can therefore free the node between the lookup and the refcount operation: CPU0 (attach) CPU1 (owner unregisters) read_lock_bh(&dmb_ht_lock) find dmb_node (refcnt == 1) read_unlock_bh(&dmb_ht_lock) refcount_dec_and_test() 1 -> 0 write_lock_bh(&dmb_ht_lock) hash_del(&dmb_node->list) write_unlock_bh(&dmb_ht_lock) kfree(dmb_node) refcount_inc_not_zero(&dmb_node->refcnt) <-- use-after-free The same window exists for the refcount_dec_and_test() calls in the detach and unregister paths. Close the race structurally by making hash table membership and the refcount transitions atomic with respect to each other: - Perform the final refcount_dec_and_test() and hash_del() in a single dmb_ht_lock write-side critical section, in both the unregister and the detach path. Freeing the node still happens after the lock is dropped, which is safe because a node whose refcount reached zero has left the hash table and can no longer be found. - This establishes the invariant that any node found in the hash table holds at least one reference, and that the final reference can only be dropped under the write lock. dibs_lo_attach_dmb() can thus take its reference with a plain refcount_inc() while still holding the read lock; refcount_inc_not_zero() is no longer needed. __dibs_lo_unregister_dmb() no longer touches the hash table and is renamed to dibs_lo_free_dmb() accordingly. Note: commit cc21191b584c ("dibs: Move data path to dibs layer") moved the code to its current location; the race was introduced earlier by commit c3a910f2380f ("net/smc: implement DMB-merged operations of loopback-ism"). Tested SMC-D via ISM and dibs loopback.

• https://git.kernel.org/stable/c/48c073f88c93707089a4214f21cb4c3de5aea6e4
• https://git.kernel.org/stable/c/a10ea943356b9d70c5616a0a06f6fa97cfdaccb1
• https://git.kernel.org/stable/c/c0837aeace96152d14b17fdd19d70102b6631a7d

Published

Aug 15, 2026

Last Modified

Aug 17, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-74508In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-74509In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-7451A maliciously crafted TIF file, when parsed through Autodesk…7.8
• CVE-2026-74510In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74511Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2026-74512In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74514In the Linux kernel, the following vulnerability has been re…
• CVE-2026-74515In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-74516In the Linux kernel, the following vulnerability has been re…8.2
• CVE-2026-74517In the Linux kernel, the following vulnerability has been re…9.3
• CVE-2026-74518In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74519In the Linux kernel, the following vulnerability has been re…7.8