CVE-2026-43016

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

bpf: sockmap: Fix use-after-free of sk->sk_socket in sk_psock_verdict_data_ready().

syzbot reported use-after-free of AF_UNIX socket's sk->sk_socket in sk_psock_verdict_data_ready(). [0]

In unix_stream_sendmsg(), the peer socket's ->sk_data_ready() is called after dropping its unix_state_lock().

Although the sender socket holds the peer's refcount, it does not prevent the peer's sock_orphan(), and the peer's sk_socket might be freed after one RCU grace period.

Let's fetch the peer's sk->sk_socket and sk->sk_socket->ops under RCU in sk_psock_verdict_data_ready().

[0]: BUG: KASAN: slab-use-after-free in sk_psock_verdict_data_ready+0xec/0x590 net/core/skmsg.c:1278 Read of size 8 at addr ffff8880594da860 by task syz.4.1842/11013

CPU: 1 UID: 0 PID: 11013 Comm: syz.4.1842 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xba/0x230 mm/kasan/report.c:482 kasan_report+0x117/0x150 mm/kasan/report.c:595 sk_psock_verdict_data_ready+0xec/0x590 net/core/skmsg.c:1278 unix_stream_sendmsg+0x8a3/0xe80 net/unix/af_unix.c:2482 sock_sendmsg_nosec net/socket.c:721 [inline] __sock_sendmsg net/socket.c:736 [inline] ____sys_sendmsg+0x972/0x9f0 net/socket.c:2585 ___sys_sendmsg+0x2a5/0x360 net/socket.c:2639 __sys_sendmsg net/socket.c:2671 [inline] __do_sys_sendmsg net/socket.c:2676 [inline] __se_sys_sendmsg net/socket.c:2674 [inline] __x64_sys_sendmsg+0x1bd/0x2a0 net/socket.c:2674 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7facf899c819 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007facf9827028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007facf8c15fa0 RCX: 00007facf899c819 RDX: 0000000000000000 RSI: 0000200000000500 RDI: 0000000000000004 RBP: 00007facf8a32c91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007facf8c16038 R14: 00007facf8c15fa0 R15: 00007ffd41b01c78

Allocated by task 11013: kasan_save_stack mm/kasan/common.c:57 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:78 unpoison_slab_object mm/kasan/common.c:340 [inline] __kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:366 kasan_slab_alloc include/linux/kasan.h:253 [inline] slab_post_alloc_hook mm/slub.c:4538 [inline] slab_alloc_node mm/slub.c:4866 [inline] kmem_cache_alloc_lru_noprof+0x2b8/0x640 mm/slub.c:4885 sock_alloc_inode+0x28/0xc0 net/socket.c:316 alloc_inode+0x6a/0x1b0 fs/inode.c:347 new_inode_pseudo include/linux/fs.h:3003 [inline] sock_alloc net/socket.c:631 [inline] __sock_create+0x12d/0x9d0 net/socket.c:1562 sock_create net/socket.c:1656 [inline] __sys_socketpair+0x1c4/0x560 net/socket.c:1803 __do_sys_socketpair net/socket.c:1856 [inline] __se_sys_socketpair net/socket.c:1853 [inline] __x64_sys_socketpair+0x9b/0xb0 net/socket.c:1853 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 15: kasan_save_stack mm/kasan/common.c:57 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:78 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:584 poison_slab_object mm/kasan/common.c:253 [inline] __kasan_slab_free+0x5c/0x80 mm/kasan/common.c:285 kasan_slab_free include/linux/kasan.h:235 [inline] slab_free_hook mm/slub.c:2685 [inline] slab_free mm/slub.c:6165 [inline] kmem_cache_free+0x187/0x630 mm/slub.c:6295 rcu_do_batch kernel/rcu/tree.c: ---truncated---

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

May 1, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

bpf: sockmap: Fix use-after-free of sk->sk_socket in sk_psock_verdict_data_ready(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: sockmap: Fix use-after-free of sk->sk_socket in sk_psock_verdict_data_ready(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: sockmap: Fix use-after-free of sk->sk_socket in sk_psock_verdict_data_ready(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d597e3e74027900ffa81b8ff47ab51999a3e110
generic

bpf: sockmap: Fix use-after-free of sk->sk_socket in sk_psock_verdict_data_ready(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68187f18a89be4b6237d28ae1313b5adf76238c6
generic

bpf: sockmap: Fix use-after-free of sk->sk_socket in sk_psock_verdict_data_ready(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18861f87a043e78b1f901cae4237e755ed7ef095

Patch Availability(15)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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 202 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43016?
CVE-2026-43016 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: sockmap: Fix use-after-free of sk->sksocket in skpsockverdictdata_ready(). syzbot reported use-after-free of AFUNIX socket's sk->sksocket in skpsockverdictdataready(). [0] In unixstreamsendmsg(), the peer socket's…
When was CVE-2026-43016 disclosed?
CVE-2026-43016 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43016 actively exploited?
CVE-2026-43016 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-43016?
CVE-2026-43016 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43016, 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-43016

Explore →

Is Your Infrastructure Affected by CVE-2026-43016?

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