CVE-2026-74257

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
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:

sockmap: Fix use-after-free in udp_bpf_recvmsg()

syzbot reported use-after-free of struct sk_msg in sk_msg_recvmsg(). [0]

sk_msg_recvmsg() peeks sk_msg from psock->ingress_msg under a lock, but its processing is lockless.

Thus, sk_msg_recvmsg() must be serialised by callers, otherwise multiple threads could touch the same sk_msg.

For example, TCP uses lock_sock(), and AF_UNIX uses unix_sk(sk)->iolock.

Initially, udp_bpf_recvmsg() had used lock_sock(), but the cited commit removed it.

Let's serialise sk_msg_recvmsg() with lock_sock() in udp_bpf_recvmsg().

Note that holding spin_lock_bh(&sk->sk_receive_queue.lock) is not an option due to copy_page_to_iter() in sk_msg_recvmsg().

[0]: BUG: KASAN: slab-use-after-free in sk_msg_recvmsg+0xb54/0xc30 net/core/skmsg.c:428 Read of size 4 at addr ffff88814cdcf000 by task syz.0.24/6020

CPU: 1 UID: 0 PID: 6020 Comm: syz.0.24 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 01/13/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_msg_recvmsg+0xb54/0xc30 net/core/skmsg.c:428 udp_bpf_recvmsg+0x4bd/0xe00 net/ipv4/udp_bpf.c:84 inet_recvmsg+0x260/0x270 net/ipv4/af_inet.c:891 sock_recvmsg_nosec net/socket.c:1078 [inline] sock_recvmsg+0x1a8/0x270 net/socket.c:1100 ____sys_recvmsg+0x1e6/0x4a0 net/socket.c:2812 ___sys_recvmsg+0x215/0x590 net/socket.c:2854 do_recvmmsg+0x334/0x800 net/socket.c:2949 __sys_recvmmsg net/socket.c:3023 [inline] __do_sys_recvmmsg net/socket.c:3046 [inline] __se_sys_recvmmsg net/socket.c:3039 [inline] __x64_sys_recvmmsg+0x198/0x250 net/socket.c:3039 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb319f9aeb9 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:00007fb31ad97028 EFLAGS: 00000246 ORIG_RAX: 000000000000012b RAX: ffffffffffffffda RBX: 00007fb31a216090 RCX: 00007fb319f9aeb9 RDX: 0000000000000001 RSI: 0000200000000400 RDI: 0000000000000004 RBP: 00007fb31a008c1f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000040000021 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fb31a216128 R14: 00007fb31a216090 R15: 00007ffe21dd0a98

Allocated by task 6019: kasan_save_stack mm/kasan/common.c:57 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:78 poison_kmalloc_redzone mm/kasan/common.c:398 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 [inline] __kmalloc_cache_noprof+0x3d1/0x6e0 mm/slub.c:5780 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] alloc_sk_msg net/core/skmsg.c:510 [inline] sk_psock_skb_ingress_self+0x60/0x350 net/core/skmsg.c:612 sk_psock_verdict_apply net/core/skmsg.c:1038 [inline] sk_psock_verdict_recv+0x7d9/0x8d0 net/core/skmsg.c:1236 udp_read_skb+0x73e/0x7e0 net/ipv4/udp.c:2045 sk_psock_verdict_data_ready+0x12d/0x550 net/core/skmsg.c:1257 __udp_enqueue_schedule_skb+0xc54/0x10b0 net/ipv4/udp.c:1789 __udp_queue_rcv_skb net/ipv4/udp.c:2346 [inline] udp_queue_rcv_one_skb+0xac5/0x19c0 net/ipv4/udp.c:2475 __udp4_lib_mcast_deliver+0xc06/0xcf0 net/ipv4/udp.c:2585 __udp4_lib_rcv+0x10f6/0x2620 net/ipv4/udp.c:2724 ip_protocol_deliver_rcu+0x282/0x440 net/ipv4/ip_input.c:207 ip_local_deliver_finish+0x3bb/0x6f0 net/ipv4/ip_input.c:241 NF_HOOK+0x336/0x3c0 include/linux/netfilter.h:318 dst_input include/net/dst.h:474 [inline] ip_sublist_rcv_finish+0x221/0x2a0 net/ipv4/ip_input.c:584 ip_list_rcv_finish net/ipv4/ip_inp ---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.2% × 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
1st
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: 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.

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

August 15, 2026

Last Modified

October 16, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
Patch available.
Web page

sockmap: Fix use-after-free in udp_bpf_recvmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c010995b29c8939c6aa69e3cb26f8dbee163d156
Web page

sockmap: Fix use-after-free in udp_bpf_recvmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81567d2b3f4dc4fc32f8b61433738bce2cafd4a1
Web page

sockmap: Fix use-after-free in udp_bpf_recvmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39d44ed6904bfa9a1c6d0538672dd50c7b85520e

Vendor Advisories for CVE-2026-74257(2)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-16ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-16ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-16ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-16ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-16ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-16ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-16ubuntu

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.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 14× in last 7d / 96× 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 224 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 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74257?
CVE-2026-74257 is a high-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: sockmap: Fix use-after-free in udpbpfrecvmsg() syzbot reported use-after-free of struct skmsg in skmsg_recvmsg(). [0] skmsgrecvmsg() peeks skmsg from psock->ingressmsg under a lock, but its processing is lockless. Thus,…
When was the CVE record for CVE-2026-74257 published?
The CVE record for CVE-2026-74257 was published on August 15, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-74257 actively exploited?
CVE-2026-74257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74257?
CVE-2026-74257 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74257?
A fix for CVE-2026-74257 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74257 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-74257

Explore →

Is Your Infrastructure Affected by CVE-2026-74257?

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

Book a Demo →Browse All CVEs