CVE-2026-98076

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-86906 (ENISA EUVD) · GHSA-hv39-rmvr-p67c (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:

tracing/probes: Fix use-after-free on field name/type of events with multiple probes

The fields of a probe-based dynamic event (kprobe, uprobe, eprobe and fprobe events) are created in traceprobe_define_arg_fields() by handing the probe_arg name/type strings to trace_define_field(), which only stores the pointers without copying. Those strings are owned by the trace_probe and are freed when that probe is removed.

An event can have several probes attached. The field list is defined only once, by the first probe that registers the event, but it is kept alive by any surviving sibling probe. Deleting just that first probe by symbol -

# primary A: fields are defined from A's args echo 'p:kprobes/ev vfs_read a1=$arg1' > kprobe_events # append B: shares A's event call echo 'p:kprobes/ev vfs_write a1=$arg1' >> kprobe_events # delete only A (matched by symbol), B survives echo '-:kprobes/ev vfs_read' >> kprobe_events

frees A's args (trace_probe_cleanup() -> traceprobe_free_probe_arg()), but trace_probe_unlink() keeps the trace_probe_event because the probe list is not empty. The event call stays registered via B while its fields now reference freed memory. Any field lookup then reads it, e.g.

echo 'a1 == 1' > events/kprobes/ev/filter

BUG: KASAN: slab-use-after-free in strcmp+0xa7/0xb0 Call Trace: strcmp trace_find_event_field parse_pred process_preds create_filter apply_event_filter event_filter_write

field->name references parg->name (kstrdup'd, freed with the probe) and, for array arguments, field->type references parg->fmt (kmalloc'd, freed with the probe) - the scalar type otherwise points at the static fmttype rodata, which is safe.

Have traceprobe_define_arg_fields() duplicate the name and type strings and anchor the copies on the trace_probe_event, which embeds the event call and outlives every individual probe; trace_probe_event_free() releases them.

The reproducer above triggers reliably; the field lookup and the delete both run under event_mutex, so this is a dangling reference after removal rather than a race.

The issue was found by the autokbug dynamic kernel fuzzer at Tencent Yunding Lab.

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
5th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% 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 (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

September 25, 2026

Last Modified

November 18, 2026

Advisory Details (8)

Auto-updated Nov 18, 2026
Patch available.
Web page

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9379e193826f23876daccb3351fab89c87084ba3
Web page

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86b7a239ec6b14a7544200ede85474c6f5526049
Web page

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68ae584169c7a41fc9bc4677c1d368983cf44b21
Web page

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/411c9080a776577664531b4f7d3ee53b7a747ba8
Web page

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38305e1b8b1ec27eef8f2d4e461e3b6c8624d494
Web page

tracing/probes: Fix use-after-free on field name/type of events with multiple probes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/178ff2e011e21fbebdf57f5d58a408fe59136d82

Vendor Advisories for CVE-2026-98076(2)

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

Patch Availability(19)

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 9× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

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 93 is merged into the row it repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-11-18 13:12 UTCEchelonGraph re-scoredFirst assessed: 7.8 HIGH
  6. 2026-11-18 13:12 UTCVendor advisory
  7. 2026-11-18 13:11 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  8. 2026-11-18 13:07 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  9. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 67 more
  1. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-28 09:25 UTCOSV refresh
  5. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-25 13:47 UTCEchelonGraph re-scored
  9. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-19 10:37 UTCVendor advisory
  16. 2026-10-19 10:37 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  17. 2026-10-19 10:25 UTCNVD update
  18. 2026-10-19 09:52 UTCEchelonGraph re-scored
  19. 2026-10-19 09:52 UTCVendor advisory
  20. 2026-10-19 09:51 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  21. 2026-10-19 09:39 UTCMITRE cvelistV5
  22. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-18 02:56 UTCEchelonGraph re-scored
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-10-12 14:39 UTCEchelonGraph re-scored
  31. 2026-10-11 19:10 UTCEchelonGraph re-scored
  32. 2026-10-11 16:25 UTCEchelonGraph re-scored
  33. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  34. 2026-10-11 13:37 UTCEchelonGraph re-scored
  35. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  36. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  37. 2026-10-09 12:26 UTCVendor advisory
  38. 2026-10-09 12:26 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  39. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  40. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  42. 2026-10-06 10:56 UTCVendor advisory
  43. 2026-10-06 10:56 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  44. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  45. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  46. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  47. 2026-10-03 11:27 UTCVendor advisory
  48. 2026-10-03 11:27 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  49. 2026-10-03 11:26 UTCNVD update
  50. 2026-10-03 11:12 UTCVendor advisory
  51. 2026-10-03 11:12 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  52. 2026-10-03 11:10 UTCMITRE cvelistV5
  53. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  54. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  55. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-09-30 14:35 UTCEchelonGraph re-scored
  57. 2026-09-30 14:35 UTCVendor advisory
  58. 2026-09-30 14:35 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  59. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  60. 2026-09-28 11:01 UTCEchelonGraph re-scored
  61. 2026-09-28 11:01 UTCVendor advisory
  62. 2026-09-28 11:01 UTCGHSA enrichmentGHSA-hv39-rmvr-p67c
  63. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  64. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  65. 2026-09-25 11:30 UTCNVD update
  66. 2026-09-25 10:27 UTCEchelonGraph re-scored
  67. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98076?
CVE-2026-98076 is a high-severity vulnerability; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: tracing/probes: Fix use-after-free on field name/type of events with multiple probes The fields of a probe-based dynamic event (kprobe, uprobe, eprobe and fprobe events) are created in traceprobe_define_arg_fields() by handing the…
When was the CVE record for CVE-2026-98076 published?
The CVE record for CVE-2026-98076 was published on September 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 November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-98076 actively exploited?
CVE-2026-98076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98076?
CVE-2026-98076 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-98076?
A fix for CVE-2026-98076 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98076 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-98076

Explore →

Is Your Infrastructure Affected by CVE-2026-98076?

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