CVE-2026-23010

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-01-25. 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-4626 (ENISA EUVD) · GHSA-3c7w-pf2p-jwm8 (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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ipv6: Fix use-after-free in inet6_addr_del().

syzbot reported use-after-free of inet6_ifaddr in inet6_addr_del(). [0]

The cited commit accidentally moved ipv6_del_addr() for mngtmpaddr before reading its ifp->flags for temporary addresses in inet6_addr_del().

Let's move ipv6_del_addr() down to fix the UAF.

[0]: BUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117 Read of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593

CPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117 addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181 inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582 sock_do_ioctl+0x118/0x280 net/socket.c:1254 sock_ioctl+0x227/0x6b0 net/socket.c:1375 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f164cf8f749 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749 RDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003 RBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288

Allocated by task 9593: kasan_save_stack+0x33/0x60 mm/kasan/common.c:56 kasan_save_track+0x14/0x30 mm/kasan/common.c:77 poison_kmalloc_redzone mm/kasan/common.c:397 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120 inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050 addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160 inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580 sock_do_ioctl+0x118/0x280 net/socket.c:1254 sock_ioctl+0x227/0x6b0 net/socket.c:1375 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 6099: kasan_save_stack+0x33/0x60 mm/kasan/common.c:56 kasan_save_track+0x14/0x30 mm/kasan/common.c:77 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584 poison_slab_object mm/kasan/common.c:252 [inline] __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284 kasan_slab_free include/linux/kasan.h:234 [inline] slab_free_hook mm/slub.c:2540 [inline] slab_free_freelist_hook mm/slub.c:2569 [inline] slab_free_bulk mm/slub.c:6696 [inline] kmem_cache_free_bulk mm/slub.c:7383 [inline] kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362 kfree_bulk include/linux/slab.h:830 [inline] kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523 kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline] kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801 process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257 process_scheduled_works kernel/workqu ---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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.2%
EPSS %ILE
9th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

January 25, 2026

Last Modified

October 15, 2026

Advisory Details (6)

Auto-updated Jul 14, 2026
Patch available.
Web page

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

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

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

https://git.kernel.org/stable/c/9356b69d03d0f50cce91cebdabd33dda023fbd64
Web page

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

https://git.kernel.org/stable/c/8b6dcb565e419846bd521e31d5e1f98e4d0e1179
Web page

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

https://git.kernel.org/stable/c/6e89d60b4f03014f7d412ce64b17a840840d490e
Web page

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

https://git.kernel.org/stable/c/2684610a9c9c53f262fd864fa5c407e79f304804

Vendor Advisories for CVE-2026-23010(2)

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

Patch Availability(17)

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 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (97 versions)
  • every version up to 6.18.8-1: fixed in 6.18.8-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 10× in last 7d / 45× 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 99 of 239 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-23010?
CVE-2026-23010 is a high-severity vulnerability; its CVE record was published on January 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix use-after-free in inet6_addr_del(). syzbot reported use-after-free of inet6_ifaddr in inet6_addr_del(). [0] The cited commit accidentally moved ipv6_del_addr() for mngtmpaddr before reading its ifp->flags for temporary…
When was the CVE record for CVE-2026-23010 published?
The CVE record for CVE-2026-23010 was published on January 25, 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-23010 actively exploited?
CVE-2026-23010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23010?
CVE-2026-23010 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23010?
A fix for CVE-2026-23010 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23010 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-23010

Explore →

Is Your Infrastructure Affected by CVE-2026-23010?

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