Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-74513

kernel: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister

Overview

Published
15 Aug 2026
Modified
21 Oct 2026
High CVE
0 Registry packages
115 OS packages
7 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

7.8 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 35 fixes

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2026-74513
ReleasePackageFixed in
5.0 bpftool +10 6.12.114-1.ph5

SUSE Linux Enterprise 2 releases · 5 packages

fixed 7
kernel-livepatch-6-4-0-150700-7-78-rt kernel-livepatch-6-4-0-150700-53-84-default cluster-md-kmp-default kernel-default-base kernel-64kb
SUSE Linux Enterprise fixes for CVE-2026-74513
ReleasePackageFixed inAdvisory
15.7 kernel-livepatch-6-4-0-150700-7-78-rt 1-150700.1.3.1 SUSE-SU-2026:4640-1
15.7 kernel-livepatch-6-4-0-150700-53-84-default 1-150700.15.3.1 SUSE-SU-2026:4706-1
15.7 cluster-md-kmp-default +20 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1
15.7 kernel-default-base 6.4.0-150700.53.84.1.150700.17.47.1 SUSE-SU-2026:4706-1
16.0 cluster-md-kmp-default +2 6.12.0-160000.38.1 SUSE-SU-2026:23897-1
16.0 kernel-64kb +23 6.12.0-160000.38.1 SUSE-SU-2026:23902-1

1 more row

SUSE Linux Enterprise Micro 1 release · 2 packages

fixed 2
kernel-64kb kernel-default-base
SUSE Linux Enterprise Micro fixes for CVE-2026-74513
ReleasePackageFixed inAdvisory
6.2 kernel-64kb +11 6.12.0-160000.38.1 SUSE-SU-2026:23887-1
6.2 kernel-default-base 6.12.0-160000.38.1.160000.2.23 SUSE-SU-2026:23887-1

debian 3 releases · 2 packages

fixed 3
linux-6-12 linux
debian fixes for CVE-2026-74513
ReleasePackageFixed in
12 linux-6-12 6.12.115-2~deb12u1
13 linux 6.12.115-2
14 linux 7.1.8-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2026-74513
ReleasePackageFixed in
linux 6.12.115-2

openSUSE Leap 1 release · 2 packages

fixed 2
cluster-md-kmp-64kb kernel-default-base
openSUSE Leap fixes for CVE-2026-74513
ReleasePackageFixed inAdvisory
16.0 cluster-md-kmp-64kb +74 6.12.0-160000.38.1 openSUSE-SU-2026:21910-1
16.0 kernel-default-base 6.12.0-160000.38.1.160000.2.22 openSUSE-SU-2026:21910-1

ubuntu 2 releases · 19 packages

affected 2 fixed 17
linux-azure-7-0 linux-oracle-7-0 linux-aws-7-0 linux-gcp-7-0 linux-azure-fde-7-0 linux-riscv-7-0 +13
ubuntu fixes for CVE-2026-74513
ReleasePackageFixed in
24.04 linux-azure-7-0 +1 affected
24.04 linux-oracle-7-0 7.0.0-1016.18~24.04.1
24.04 linux-aws-7-0 7.0.0-1017.18~24.04.1
24.04 linux-gcp-7-0 7.0.0-1017.19~24.04.1
24.04 linux-azure-fde-7-0 7.0.0-1019.19~24.04.1
24.04 linux-riscv-7-0 7.0.0-42.42.1~24.04.1

13 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.