Answer in brief
CVE-2026-53035 records a Medium severity (CVSS 5.5) vulnerability in bpf, sockmap: Fix af_unix iter deadlock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2c860a43dd77f969bb959336a2f743d7103a8f63 <bd3592129f24243713673a07225cf1f15a9bb835 || >=2c860a43dd77f969bb959336a2f743d7103a8f63 <3cef33b9813b78f227942572fb317afcd5c9ac94 || >=2c860a43dd77f969bb959336a2f743d7103a8f63 <87828b380956d4986f59f2c086e0b09b3e6cdaae || >=2c860a43dd77f969bb959336a2f743d7103a8f63 <527057ebe8076dfbcaef51195ff1b7508646be2c || >=2c860a43dd77f969bb959336a2f743d7103a8f63 <66d9fab4565eafe1afe7ba0581f79b76073b60fa || >=2c860a43dd77f969bb959336a2f743d7103a8f63 <4d328dd695383224aa750ddee6b4ad40c0f8d205 | bd3592129f24243713673a07225cf1f15a9bb835, 3cef33b9813b78f227942572fb317afcd5c9ac94, 87828b380956d4986f59f2c086e0b09b3e6cdaae, 527057ebe8076dfbcaef51195ff1b7508646be2c, 66d9fab4565eafe1afe7ba0581f79b76073b60fa, 4d328dd695383224aa750ddee6b4ad40c0f8d205 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix af_unix iter deadlock bpf_iter_unix_seq_show() may deadlock when lock_sock_fast() takes the fast path and the iter prog attempts to update a sockmap. Which ends up spinning at sock_map_update_elem()'s bh_lock_sock(): WARNING: possible recursive locking detected test_progs/1393 is trying to acquire lock: ffff88811ec25f58 (slock-AF_UNIX){+...}-{3:3}, at: sock_map_update_elem+0xdb/0x1f0 but task is already holding lock: ffff88811ec25f58 (slock-AF_UNIX){+...}-{3:3}, at: __lock_sock_fast+0x37/0xe0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(slock-AF_UNIX); lock(slock-AF_UNIX); *** DEADLOCK *** May be due to missing lock nesting notation 4 locks held by test_progs/1393: #0: ffff88814b59c790 (&p->lock){+.+.}-{4:4}, at: bpf_seq_read+0x59/0x10d0 #1: ffff88811ec25fd8 (sk_lock-AF_UNIX){+.+.}-{0:0}, at: bpf_seq_read+0x42c/0x10d0 #2: ffff88811ec25f58 (slock-AF_UNIX){+...}-{3:3}, at: __lock_sock_fast+0x37/0xe0 #3: ffffffff85a6a7c0 (rcu_read_lock){....}-{1:3}, at: bpf_iter_run_prog+0x51d/0xb00 Call Trace: dump_stack_lvl+0x5d/0x80 print_deadlock_bug.cold+0xc0/0xce __lock_acquire+0x130f/0x2590 lock_acquire+0x14e/0x2b0 _raw_spin_lock+0x30/0x40 sock_map_update_elem+0xdb/0x1f0 bpf_prog_2d0075e5d9b721cd_dump_unix+0x55/0x4f4 bpf_iter_run_prog+0x5b9/0xb00 bpf_iter_unix_seq_show+0x1f7/0x2e0 bpf_seq_read+0x42c/0x10d0 vfs_read+0x171/0xb20 ksys_read+0xff/0x200 do_syscall_64+0x6b/0x3a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e
Quoted source text, attributed separately from HOL analysis.