dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53005

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 7.0.10 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A use-after-free vulnerability exists in the Linux kernel's AF_UNIX socket garbage collection (GC) when SOCKMAP (BPF socket mapping) is used. SOCKMAP can hide inflight file descriptors from both old and new AF_UNIX GC by queuing skbs with SCM credentials into psock->ingress_skb, which the GC cannot inspect. This causes hidden skbs to leak inflight sockets and breaks the Tarjan-based GC's assumption that unix_edge.successor is always alive, resulting in use-after-free in unix_del_edges. Additionally, SOCKMAP doesn't call scm_stat_del() properly, causing incorrect fd counts in unix_show_fdinfo().

MitigationApply the upstream kernel patch to drop all SCM attributes before passing skb to the SOCKMAP layer, then rebuild and deploy the patched kernel. Organizations using SOCKMAP/BPF should prioritize this patch given the use-after-free and potential local privilege escalation risk.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.15, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run 'uname -r' to get the running kernel version
    Affected if Kernel version is >= 5.15 and < 7.0.10
  2. Verify BPF sockmap support is built into the kernel
    Check /boot/config-$(uname -r) or /proc/config.gz for CONFIG_BPF_SYSCALL and CONFIG_SOCKMAP options
    Affected if BPF and SOCKMAP are enabled in kernel config
  3. Detect active SOCKMAP or SOCKHASH attachments
    Use 'bpftool map show' and 'bpftool prog show' to list BPF maps and programs, looking for map types sockmap or sockhash
    Affected if Any SOCKMAP or SOCKHASH BPF maps are currently attached
  4. Check for SCM_RIGHTS file descriptor passing over AF_UNIX sockets
    Monitor socket activity via 'ss -x' (unix domain sockets) or audit logs for SCM_RIGHTS messages, or inspect application usage of unix sockets with file descriptor passing
    Affected if Applications are passing file descriptors via SCM_RIGHTS over AF_UNIX sockets while using SOCKMAP
  5. Inspect for potential fdinfo inconsistencies
    Check /proc/net/unix for unix socket entries and compare with 'ls /proc/<pid>/fd' for processes using unix domain sockets with SOCKMAP
    Affected if Discrepancies found between reported fd counts and actual file descriptors, indicating the scm_stat_del() issue

User is affected if running a kernel between 5.15 and 7.0.10 with BPF SOCKMAP enabled and actively passing SCM_RIGHTS file descriptors over AF_UNIX sockets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.10 or later
Fixed in 7.0.10
Interim mitigation

Apply the upstream kernel patch to drop all SCM attributes before passing skb to the SOCKMAP layer, then rebuild and deploy the patched kernel. Organizations using SOCKMAP/BPF should prioritize this patch given the use-after-free and potential local privilege escalation risk.

Recommended fix High confidence

Linux Kernel 7.0.10 or later

  1. Identify the current running Linux kernel version using `uname -r`
  2. Confirm the kernel version is >= 5.15 and < 7.0.10 by checking `/proc/version` or the boot loader configuration
  3. Plan a kernel upgrade to version 7.0.10 or later
  4. Back up all critical data and verify backups before proceeding
  5. Schedule a maintenance window for the system reboot
  6. Upgrade the Linux kernel package using the distribution's package manager (e.g., `apt-get dist-upgrade`, `yum update`, or equivalent)
  7. Reboot the system to load the new kernel
  8. Verify the new kernel version is running with `uname -r` and confirms it is >= 7.0.10
Caveat Kernel upgrades may require rebooting and could have compatibility implications with third-party kernel modules. Ensure all proprietary drivers are compatible with the target kernel version before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53005 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data