Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53005: af_unix: Drop all SCM attributes for SOCKMAP.

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 301bdc558a5eb4057473204d35e2608e682aaafb, 48c41cd2e04af4b2cdef19e2d00994ae82952f14, 866e69a824b46e682b8fb923be321b585e634874; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 301bdc558a5eb4057473204d35e2608e682aaafb, 48c41cd2e04af4b2cdef19e2d00994ae82952f14, 866e69a824b46e682b8fb923be321b585e634874; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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)

Published
Jun 24, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53005

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.15affected
    • c63829182c37c2d6d0608976d15fa61ebebe9e6b and later · before 866e69a824b46e682b8fb923be321b585e634874affected · git
    • c63829182c37c2d6d0608976d15fa61ebebe9e6b and later · before 301bdc558a5eb4057473204d35e2608e682aaafbaffected · git
    • c63829182c37c2d6d0608976d15fa61ebebe9e6b and later · before 48c41cd2e04af4b2cdef19e2d00994ae82952f14affected · git
    • c63829182c37c2d6d0608976d15fa61ebebe9e6b and later · before e0a71cbf0c1906a2eccbe69dd7d7f36fd1511d66affected · git
    • c63829182c37c2d6d0608976d15fa61ebebe9e6b and later · before b34a1d83c74a124c968b5adb25c809db3e2eb86aaffected · git
    • c63829182c37c2d6d0608976d15fa61ebebe9e6b and later · before 965dc93481d1b80d341bdd16c27b16fe197175eeaffected · git
    • before 5.15not affected · semver
    • 6.1.189 and later · up to and including 6.1.*not affected · semver
    • 6.6.158 and later · up to and including 6.6.*not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15 and later · before 7.0.10

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53003Jun 24, 2026 · pppoe: drop PFC frames
    30Monitor
  • ← EarlierCVE-2026-53004Jun 24, 2026 · sctp: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks
    31Monitor
  • Later →CVE-2026-53006Jun 24, 2026 · ipv6: fix possible UAF in icmpv6_rcv()
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux301bdc558a5eb4057473204d35e2608e682aaafbVendor (CNA)
Linux Linux48c41cd2e04af4b2cdef19e2d00994ae82952f14Vendor (CNA)
Linux Linux866e69a824b46e682b8fb923be321b585e634874Vendor (CNA)
Linux Linux965dc93481d1b80d341bdd16c27b16fe197175eeVendor (CNA)
Linux Linuxb34a1d83c74a124c968b5adb25c809db3e2eb86aVendor (CNA)
Linux Linuxe0a71cbf0c1906a2eccbe69dd7d7f36fd1511d66Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-extra5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.100-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+6

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records