CVE-2026-23171

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-02-14. 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-5867 (ENISA EUVD) · GHSA-5r72-p4cv-h344 (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:

bonding: fix use-after-free due to enslave fail after slave array update

Fix a use-after-free which happens due to enslave failure after the new slave has been added to the array. Since the new slave can be used for Tx immediately, we can use it after it has been freed by the enslave error cleanup path which frees the allocated slave memory. Slave update array is supposed to be called last when further enslave failures are not expected. Move it after xdp setup to avoid any problems.

It is very easy to reproduce the problem with a simple xdp_pass prog: ip l add bond1 type bond mode balance-xor ip l set bond1 up ip l set dev bond1 xdp object xdp_pass.o sec xdp_pass ip l add dumdum type dummy

Then run in parallel: while :; do ip l set dumdum master bond1 1>/dev/null 2>&1; done; mausezahn bond1 -a own -b rand -A rand -B 1.1.1.1 -c 0 -t tcp "dp=1-1023, flags=syn"

The crash happens almost immediately: [ 605.602850] Oops: general protection fault, probably for non-canonical address 0xe0e6fc2460000137: 0000 [#1] SMP KASAN NOPTI [ 605.602916] KASAN: maybe wild-memory-access in range [0x07380123000009b8-0x07380123000009bf] [ 605.602946] CPU: 0 UID: 0 PID: 2445 Comm: mausezahn Kdump: loaded Tainted: G B 6.19.0-rc6+ #21 PREEMPT(voluntary) [ 605.602979] Tainted: [B]=BAD_PAGE [ 605.602998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 605.603032] RIP: 0010:netdev_core_pick_tx+0xcd/0x210 [ 605.603063] Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3e 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 6b 08 49 8d 7d 30 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 25 01 00 00 49 8b 45 30 4c 89 e2 48 89 ee 48 89 [ 605.603111] RSP: 0018:ffff88817b9af348 EFLAGS: 00010213 [ 605.603145] RAX: dffffc0000000000 RBX: ffff88817d28b420 RCX: 0000000000000000 [ 605.603172] RDX: 00e7002460000137 RSI: 0000000000000008 RDI: 07380123000009be [ 605.603199] RBP: ffff88817b541a00 R08: 0000000000000001 R09: fffffbfff3ed8c0c [ 605.603226] R10: ffffffff9f6c6067 R11: 0000000000000001 R12: 0000000000000000 [ 605.603253] R13: 073801230000098e R14: ffff88817d28b448 R15: ffff88817b541a84 [ 605.603286] FS: 00007f6570ef67c0(0000) GS:ffff888221dfa000(0000) knlGS:0000000000000000 [ 605.603319] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 605.603343] CR2: 00007f65712fae40 CR3: 000000011371b000 CR4: 0000000000350ef0 [ 605.603373] Call Trace: [ 605.603392] [ 605.603410] __dev_queue_xmit+0x448/0x32a0 [ 605.603434] ? __pfx_vprintk_emit+0x10/0x10 [ 605.603461] ? __pfx_vprintk_emit+0x10/0x10 [ 605.603484] ? __pfx___dev_queue_xmit+0x10/0x10 [ 605.603507] ? bond_start_xmit+0xbfb/0xc20 [bonding] [ 605.603546] ? _printk+0xcb/0x100 [ 605.603566] ? __pfx__printk+0x10/0x10 [ 605.603589] ? bond_start_xmit+0xbfb/0xc20 [bonding] [ 605.603627] ? add_taint+0x5e/0x70 [ 605.603648] ? add_taint+0x2a/0x70 [ 605.603670] ? end_report.cold+0x51/0x75 [ 605.603693] ? bond_start_xmit+0xbfb/0xc20 [bonding] [ 605.603731] bond_start_xmit+0x623/0xc20 [bonding]

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.2%
EPSS %ILE
6th
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-29). 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

February 14, 2026

Last Modified

October 30, 2026

Advisory Details (4)

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

bonding: fix use-after-free due to enslave fail after slave array update - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: fix use-after-free due to enslave fail after slave array update - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: fix use-after-free due to enslave fail after slave array update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2889d92c5f728351c9930c7996d22fe6e906e785
Web page

bonding: fix use-after-free due to enslave fail after slave array update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/172dcb67dd35b162357df229d7806acc724cd469

Vendor Advisories for CVE-2026-23171(9)

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

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-27ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-27ubuntu
redhatkernel-0:5.14.0-427.121.1.el9_42026-04-23redhat
redhatkernel-0:5.14.0-284.166.1.el9_22026-04-22redhat
redhatkernel-rt-0:5.14.0-284.166.1.rt14.451.el9_22026-04-22redhat
redhatkernel-0:5.14.0-570.108.1.el9_62026-04-20redhat
redhatkernel-0:6.12.0-55.68.1.el10_02026-04-15redhat
redhatkernel-0:6.12.0-124.49.1.el10_12026-04-06redhat
redhatkernel-0:5.14.0-611.45.1.el9_72026-03-30redhat
linuxKernel @ 6.6.140 (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.90-1~bpo12+1 (23 versions)
  • every version up to 6.12.90-1: fixed in 6.12.90-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)
  • every version up to 6.18.9-1: fixed in 6.18.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(17)

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 16× in last 7d / 51× 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 259 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 160 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23171?
CVE-2026-23171 is a high-severity vulnerability; its CVE record was published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: bonding: fix use-after-free due to enslave fail after slave array update Fix a use-after-free which happens due to enslave failure after the new slave has been added to the array. Since the new slave can be used for Tx immediately,…
When was the CVE record for CVE-2026-23171 published?
The CVE record for CVE-2026-23171 was published on February 14, 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-23171 actively exploited?
CVE-2026-23171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23171?
CVE-2026-23171 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23171?
A fix for CVE-2026-23171 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23171 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-23171

Explore →

Is Your Infrastructure Affected by CVE-2026-23171?

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

Book a Demo →Browse All CVEs