CVE-2026-53005

Analyzed Analyzed - Analysis Complete

Use-After-Free in Linux Kernel SOCKMAP

Publication date: 2026-06-24

Last updated on: 2026-07-14

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: af_unix: Drop all SCM attributes for SOCKMAP. SOCKMAP can hide inflight fd from AF_UNIX GC. When a socket in SOCKMAP receives skb with inflight fd, sk_psock_verdict_data_ready() looks up the mapped socket and enqueue skb to its psock->ingress_skb. Since neither the old nor the new GC can inspect the psock queue, the hidden skb leaks the inflight sockets. Note that this cannot be detected via kmemleak because inflight sockets are linked to a global list. In addition, SOCKMAP redirect breaks the Tarjan-based GC's assumption that unix_edge.successor is always alive, which is no longer true once skb is redirected, resulting in use-after-free below. [0] Moreover, SOCKMAP does not call scm_stat_del() properly, so unix_show_fdinfo() could report an incorrect fd count. sk_msg_recvmsg() does not support any SCM attributes in the first place. Let's drop all SCM attributes before passing skb to the SOCKMAP layer. [0]: BUG: KASAN: slab-use-after-free in unix_del_edges (net/unix/garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c:251) Read of size 8 at addr ffff888125362670 by task kworker/56:1/496 CPU: 56 UID: 0 PID: 496 Comm: kworker/56:1 Not tainted 7.0.0-rc7-00263-gb9d8b856689d #3 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 Workqueue: events sk_psock_backlog Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:122) print_report (mm/kasan/report.c:379) kasan_report (mm/kasan/report.c:597) unix_del_edges (net/unix/garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c:251) unix_destroy_fpl (net/unix/garbage.c:317) unix_destruct_scm (./include/net/scm.h:80 ./include/net/scm.h:86 net/unix/af_unix.c:1976) sk_psock_backlog (./include/linux/skbuff.h:?) process_scheduled_works (kernel/workqueue.c:?) worker_thread (kernel/workqueue.c:?) kthread (kernel/kthread.c:438) ret_from_fork (arch/x86/kernel/process.c:164) ret_from_fork_asm (arch/x86/entry/entry_64.S:258) </TASK> Allocated by task 955: kasan_save_track (mm/kasan/common.c:58 mm/kasan/common.c:78) __kasan_slab_alloc (mm/kasan/common.c:369) kmem_cache_alloc_noprof (mm/slub.c:4539) sk_prot_alloc (net/core/sock.c:2240) sk_alloc (net/core/sock.c:2301) unix_create1 (net/unix/af_unix.c:1099) unix_create (net/unix/af_unix.c:1169) __sock_create (net/socket.c:1606) __sys_socketpair (net/socket.c:1811) __x64_sys_socketpair (net/socket.c:1863 net/socket.c:1860 net/socket.c:1860) do_syscall_64 (arch/x86/entry/syscall_64.c:?) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Freed by task 496: kasan_save_track (mm/kasan/common.c:58 mm/kasan/common.c:78) kasan_save_free_info (mm/kasan/generic.c:587) __kasan_slab_free (mm/kasan/common.c:287) kmem_cache_free (mm/slub.c:6165) __sk_destruct (net/core/sock.c:2282 net/core/sock.c:2384) sk_psock_destroy (./include/net/sock.h:?) process_scheduled_works (kernel/workqueue.c:?) worker_thread (kernel/workqueue.c:?) kthread (kernel/kthread.c:438) ret_from_fork (arch/x86/kernel/process.c:164) ret_from_fork_asm (arch/x86/entry/entry_64.S:258)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-24

Last Modified

2026-07-14

Generated

2026-07-15

AI Q&A

2026-06-24

EPSS Evaluated

2026-07-13

NVD

CVE-2026-53005

EUVD

EUVD-2026-38873

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 5.15 (inc) to 7.0.10 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Detection Guidance

This vulnerability involves hidden inflight file descriptors in SOCKMAP sockets and use-after-free errors in the Linux kernel's AF_UNIX subsystem. Detection is challenging because the inflight sockets are linked to a global list and cannot be detected via kmemleak.

No specific detection commands or methods are provided in the available information.

Executive Summary

This vulnerability exists in the Linux kernel's AF_UNIX socket implementation involving SOCKMAP. SOCKMAP can hide inflight file descriptors (fd) from the AF_UNIX garbage collector (GC). When a socket in SOCKMAP receives a socket buffer (skb) containing inflight file descriptors, the skb is enqueued to a psock's ingress queue, which the garbage collector cannot inspect. This causes a leak of inflight sockets that cannot be detected by memory leak detection tools like kmemleak.

Additionally, the SOCKMAP redirect breaks assumptions in the Tarjan-based garbage collector, leading to a use-after-free bug. SOCKMAP also fails to properly call scm_stat_del(), causing incorrect file descriptor counts to be reported by unix_show_fdinfo(). The vulnerability is mitigated by dropping all SCM attributes before passing skb to the SOCKMAP layer.

Impact Analysis

This vulnerability can lead to resource leaks where inflight sockets are not properly garbage collected, potentially exhausting system resources. The use-after-free bug can cause kernel crashes or instability, which may lead to denial of service conditions. Incorrect file descriptor counts can mislead system monitoring and debugging efforts.

Mitigation Strategies

The vulnerability has been resolved by dropping all SCM attributes before passing skb to the SOCKMAP layer, preventing hidden inflight file descriptors and use-after-free conditions.

Immediate mitigation steps would typically include updating the Linux kernel to a version that includes this fix.

No additional mitigation commands or workarounds are provided in the available information.

Hi! I’m here to help you understand CVE-2026-53005. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70