CVE-2026-43232

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 8.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-27795 (ENISA EUVD) · GHSA-84hg-9fjm-pcr7 (GitHub Security Advisories)Source: ENISA EUVD

8.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.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets

When the FarSync T-series card is being detached, the fst_card_info is deallocated in fst_remove_one(). However, the fst_tx_task or fst_int_task may still be running or pending, leading to use-after-free bugs when the already freed fst_card_info is accessed in fst_process_tx_work_q() or fst_process_int_work_q().

A typical race condition is depicted below:

CPU 0 (cleanup) | CPU 1 (tasklet) | fst_start_xmit() fst_remove_one() | tasklet_schedule() unregister_hdlc_device()| | fst_process_tx_work_q() //handler kfree(card) //free | do_bottom_half_tx() | card-> //use

The following KASAN trace was captured:

================================================================== BUG: KASAN: slab-use-after-free in do_bottom_half_tx+0xb88/0xd00 Read of size 4 at addr ffff88800aad101c by task ksoftirqd/3/32 ... Call Trace: dump_stack_lvl+0x55/0x70 print_report+0xcb/0x5d0 ? do_bottom_half_tx+0xb88/0xd00 kasan_report+0xb8/0xf0 ? do_bottom_half_tx+0xb88/0xd00 do_bottom_half_tx+0xb88/0xd00 ? _raw_spin_lock_irqsave+0x85/0xe0 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? __pfx___hrtimer_run_queues+0x10/0x10 fst_process_tx_work_q+0x67/0x90 tasklet_action_common+0x1fa/0x720 ? hrtimer_interrupt+0x31f/0x780 handle_softirqs+0x176/0x530 __irq_exit_rcu+0xab/0xe0 sysvec_apic_timer_interrupt+0x70/0x80 ...

Allocated by task 41 on cpu 3 at 72.330843s: kasan_save_stack+0x24/0x50 kasan_save_track+0x17/0x60 __kasan_kmalloc+0x7f/0x90 fst_add_one+0x1a5/0x1cd0 local_pci_probe+0xdd/0x190 pci_device_probe+0x341/0x480 really_probe+0x1c6/0x6a0 __driver_probe_device+0x248/0x310 driver_probe_device+0x48/0x210 __device_attach_driver+0x160/0x320 bus_for_each_drv+0x101/0x190 __device_attach+0x198/0x3a0 device_initial_probe+0x78/0xa0 pci_bus_add_device+0x81/0xc0 pci_bus_add_devices+0x7e/0x190 enable_slot+0x9b9/0x1130 acpiphp_check_bridge.part.0+0x2e1/0x460 acpiphp_hotplug_notify+0x36c/0x3c0 acpi_device_hotplug+0x203/0xb10 acpi_hotplug_work_fn+0x59/0x80 ...

Freed by task 41 on cpu 1 at 75.138639s: kasan_save_stack+0x24/0x50 kasan_save_track+0x17/0x60 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x43/0x70 kfree+0x135/0x410 fst_remove_one+0x2ca/0x540 pci_device_remove+0xa6/0x1d0 device_release_driver_internal+0x364/0x530 pci_stop_bus_device+0x105/0x150 pci_stop_and_remove_bus_device+0xd/0x20 disable_slot+0x116/0x260 acpiphp_disable_and_eject_slot+0x4b/0x190 acpiphp_hotplug_notify+0x230/0x3c0 acpi_device_hotplug+0x203/0xb10 acpi_hotplug_work_fn+0x59/0x80 ...

The buggy address belongs to the object at ffff88800aad1000 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 28 bytes inside of freed 1024-byte region The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xaad0 head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 flags: 0x100000000000040(head|node=0|zone=1) page_type: f5(slab) raw: 0100000000000040 ffff888007042dc0 dead000000000122 0000000000000000 raw: 0000000000000000 0000000080100010 00000000f5000000 0000000000000000 head: 0100000000000040 ffff888007042dc0 dead000000000122 0000000000000000 head: 0000000000000000 0000000080100010 00000000f5000000 0000000000000000 head: 0100000000000003 ffffea00002ab401 00000000ffffffff 00000000ffffffff head: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff88800aad0f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88800aad0f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff88800aad1000: fa fb ---truncated---

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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.4%
EPSS %ILE
32nd
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% 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 (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.

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

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/337d7b4112a47984ee319171b75b73bab47e7924
Web page

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21d341fe514fd07e345ed264c9eee21cb2061ca2
Web page

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/200bdb8d367ca9b478f9c56ebe56411604d55c81
Web page

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/086131807d119238cd464e5b0845e48d938dfd79
Web page

net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04edfdfdfcdefc02408ab670607261b0a0a9a02e

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-10-24ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-10-24ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-24ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-24ubuntu
linuxKernel @ 5.10.252 (fixes >=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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
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 (117 versions)
  • every version up to 6.19.6-1: fixed in 6.19.6-1
—

Weakness Classification(1)

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

All Vendor Advisories

(24)

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43232?
CVE-2026-43232 is a high-severity vulnerability; its CVE record was published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets When the FarSync T-series card is being detached, the fstcardinfo is deallocated in fstremoveone(). However, the fsttxtask or fstinttask may still be running…
When was the CVE record for CVE-2026-43232 published?
The CVE record for CVE-2026-43232 was published on May 6, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2026-43232 actively exploited?
CVE-2026-43232 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43232?
CVE-2026-43232 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-43232?
A fix for CVE-2026-43232 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43232

Explore →

Is Your Infrastructure Affected by CVE-2026-43232?

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

Book a Demo →Browse All CVEs