SECUFOCUSNOW
Home›CVE index›CVE-2026-53096
Review reviewHigh

CVE-2026-53096

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path The DEVMAP_HASH branch in dev_map_redirect_multi() uses hlist_for_each_entry_safe() to iterate hash buckets, but this function runs under RCU protection (called from xdp_do_generic_redirect_map() in softirq context). Concurrent writers (__dev_map_hash_update_elem, dev_map_hash_delete_elem) modify the list using RCU primitives (hlist_add_head_rcu, hlist_del_rcu). hlist_for_each_entry_safe() performs plain pointer dereferences without rcu_dereference(), missing...

CVSS
7.8
EPSS
0.13%
3.16% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path The DEVMAP_HASH branch in dev_map_redirect_multi() uses hlist_for_each_entry_safe() to iterate hash buckets, but this function runs under RCU protection (called from xdp_do_generic_redirect_map() in softirq context). Concurrent writers (__dev_map_hash_update_elem, dev_map_hash_delete_elem) modify the list using RCU primitives (hlist_add_head_rcu, hlist_del_rcu). hlist_for_each_entry_safe() performs plain pointer dereferences without rcu_dereference(), missing...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 < 4a3d0fe30b907ff324b1b49756f7e713d67f3645, >= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 < b089aa6e94d7a08e74d076a0fe274842dc9feccc, >= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 < 571a05ea1baaccc0dc1e0d227b2cbc978b96d392, >= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 < cb2c1f3cf65b855548e1b8d55a08bfbaa5a0901a, >= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 < d4c4bd231ebad70e6f30db429e9640bf378b2f52, >= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 < 7027e705062482a8cea43a1c13ede3c35653966f, >= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 < 8ed82f807bb09d2c8455aaa665f2c6cb17bc6a19, >= 5.14, >= 5.14 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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