CVE-2026-53005

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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: 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)

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 v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

af_unix: Drop all SCM attributes for SOCKMAP. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b34a1d83c74a124c968b5adb25c809db3e2eb86a
generic

af_unix: Drop all SCM attributes for SOCKMAP. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/965dc93481d1b80d341bdd16c27b16fe197175ee

Vendor Advisories for CVE-2026-53005(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 84× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 259 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-30 20:09 UTCEG score recompute
  10. 2026-08-30 20:09 UTCVendor advisory
  11. 2026-08-30 20:09 UTCGHSA enrichment
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-28 04:46 UTCEG score recompute
  16. 2026-08-28 04:46 UTCVendor advisory
  17. 2026-08-28 04:45 UTCGHSA enrichment
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 01:14 UTCEG score recompute
  22. 2026-08-25 01:14 UTCVendor advisory
  23. 2026-08-25 01:13 UTCGHSA enrichment
  24. 2026-08-24 13:42 UTCEG score recompute
  25. 2026-08-24 13:42 UTCVendor advisory
Show 75 more
  1. 2026-08-24 13:42 UTCGHSA enrichment
  2. 2026-08-23 23:58 UTCVendor advisory
  3. 2026-08-23 23:58 UTCGHSA enrichment
  4. 2026-08-23 12:27 UTCVendor advisory
  5. 2026-08-23 12:27 UTCGHSA enrichment
  6. 2026-08-23 00:55 UTCVendor advisory
  7. 2026-08-23 00:55 UTCGHSA enrichment
  8. 2026-08-22 13:05 UTCEG score recompute
  9. 2026-08-22 13:05 UTCVendor advisory
  10. 2026-08-22 13:04 UTCGHSA enrichment
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 18:09 UTCVendor advisory
  13. 2026-08-21 18:09 UTCGHSA enrichment
  14. 2026-08-21 06:32 UTCEG score recompute
  15. 2026-08-21 06:32 UTCVendor advisory
  16. 2026-08-21 06:32 UTCGHSA enrichment
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 19:00 UTCVendor advisory
  19. 2026-08-20 19:00 UTCGHSA enrichment
  20. 2026-08-20 07:28 UTCEG score recompute
  21. 2026-08-20 07:28 UTCVendor advisory
  22. 2026-08-20 07:28 UTCGHSA enrichment
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 13:43 UTCVendor advisory
  25. 2026-08-19 13:43 UTCGHSA enrichment
  26. 2026-08-19 02:10 UTCEG score recompute
  27. 2026-08-19 02:10 UTCVendor advisory
  28. 2026-08-19 02:10 UTCGHSA enrichment
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-17 07:39 UTCVendor advisory
  32. 2026-08-17 07:39 UTCGHSA enrichment
  33. 2026-08-16 20:08 UTCEG score recompute
  34. 2026-08-16 20:08 UTCVendor advisory
  35. 2026-08-16 20:08 UTCGHSA enrichment
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 08:14 UTCEG score recompute
  38. 2026-08-16 08:14 UTCVendor advisory
  39. 2026-08-16 08:14 UTCGHSA enrichment
  40. 2026-08-16 02:14 UTCEPSS rescore
  41. 2026-08-15 20:43 UTCVendor advisory
  42. 2026-08-15 20:43 UTCGHSA enrichment
  43. 2026-08-15 08:40 UTCEG score recompute
  44. 2026-08-15 08:40 UTCVendor advisory
  45. 2026-08-15 08:40 UTCGHSA enrichment
  46. 2026-08-15 01:30 UTCEPSS rescore
  47. 2026-08-14 20:38 UTCVendor advisory
  48. 2026-08-14 20:38 UTCGHSA enrichment
  49. 2026-08-14 09:07 UTCEG score recompute
  50. 2026-08-14 09:07 UTCVendor advisory
  51. 2026-08-14 09:07 UTCGHSA enrichment
  52. 2026-08-13 22:00 UTCEPSS rescore
  53. 2026-08-13 21:35 UTCVendor advisory
  54. 2026-08-13 21:35 UTCGHSA enrichment
  55. 2026-08-13 09:44 UTCVendor advisory
  56. 2026-08-13 09:44 UTCGHSA enrichment
  57. 2026-08-12 22:13 UTCEG score recompute
  58. 2026-08-12 22:13 UTCVendor advisory
  59. 2026-08-12 22:13 UTCGHSA enrichment
  60. 2026-08-12 13:51 UTCEPSS rescore
  61. 2026-08-12 10:42 UTCVendor advisory
  62. 2026-08-12 10:42 UTCGHSA enrichment
  63. 2026-08-11 23:10 UTCVendor advisory
  64. 2026-08-11 23:10 UTCGHSA enrichment
  65. 2026-08-11 11:39 UTCVendor advisory
  66. 2026-08-11 11:39 UTCGHSA enrichment
  67. 2026-08-11 00:07 UTCEG score recompute
  68. 2026-08-11 00:07 UTCVendor advisory
  69. 2026-08-11 00:07 UTCGHSA enrichment
  70. 2026-08-11 00:00 UTCEPSS rescore
  71. 2026-08-10 12:36 UTCVendor advisory
  72. 2026-08-10 12:36 UTCGHSA enrichment
  73. 2026-08-10 01:05 UTCEG score recompute
  74. 2026-08-10 01:05 UTCVendor advisory
  75. 2026-08-10 01:05 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53005?
CVE-2026-53005 is a high vulnerability published on June 24, 2026. 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, skpsockverdictdataready() looks up the mapped socket and enqueue skb to its…
When was CVE-2026-53005 disclosed?
CVE-2026-53005 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53005 actively exploited?
CVE-2026-53005 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53005?
CVE-2026-53005 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53005, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53005

Explore →

Is Your Infrastructure Affected by CVE-2026-53005?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs