CVE-2026-43016

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-26615 (ENISA EUVD) · GHSA-52mq-7c45-jwp5 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 1, 2026

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated May 3, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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

Vendor Advisories for CVE-2026-43016(1)

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-136.136.2~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux (7.0.0-1) @ resolute2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1061.64~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-27ubuntu
linuxKernel @ 6.6.134 (fixes >=5.15.0)—osv

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 rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (126 versions)
  • every version up to 6.19.12-1: fixed in 6.19.12-1
—

Weakness Classification(1)

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

All Vendor Advisories

(15)

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 13× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 266 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 166 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43016?
CVE-2026-43016 is a high-severity vulnerability; its CVE record was published on May 1, 2026. 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…
When was the CVE record for CVE-2026-43016 published?
The CVE record for CVE-2026-43016 was published on May 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-43016 actively exploited?
CVE-2026-43016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-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?
A fix for CVE-2026-43016 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43016 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs