CVE-2026-98060

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-86713 (ENISA EUVD) · GHSA-5qvg-w7qr-xhvh (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:

bpf: Reject resilient lock operations in rbtree callbacks

__bpf_rbtree_add() keeps parent and link pointers live across calls to the program-supplied comparison callback. The verifier therefore requires the root's lock to remain held throughout the callback.

The helper path enforces this rule for bpf_spin_lock() and bpf_spin_unlock(), but the resilient lock kfunc argument path does not. Since resilient locks may protect BPF rbtree roots, a callback can release the root lock and let another CPU remove and free the node referenced by the in-progress tree walk. The walk then resumes using freed pointers.

Reject resilient lock kfuncs in an rbtree comparison callback, matching the existing policy for the spin lock helpers. Resilient-lock-protected trees remain valid when their comparison callbacks leave lock state alone.

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 (3)

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

bpf: Reject resilient lock operations in rbtree callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Reject resilient lock operations in rbtree callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b7b8b5960102566bd625ae829d1f330c5b5d104
Web page

bpf: Reject resilient lock operations in rbtree callbacks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71930202a0a0c49f0a3b45b41907a074cb780266

Vendor Advisories for CVE-2026-98060(2)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute2026-11-18ubuntu
ubuntulinux-tools-realtime-hwe-26.04-edge (7.0.0-43.43.1) @ resolute2026-11-18ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1023.23) @ resolute2026-11-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1017.17) @ resolute2026-11-18ubuntu
linuxKernel @ 6.18.53 (fixes >=6.15.0)—osv

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

Affected Packages

(1 across 1 ecosystem)
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

(5)

Data Freshness Timeline

(refreshed 11× in last 7d / 35× 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 85 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% · 9th percentile
  5. 2026-11-18 13:28 UTCEchelonGraph re-scoredFirst assessed: 7.8 HIGH
  6. 2026-11-18 13:28 UTCVendor advisory
  7. 2026-11-18 13:28 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  8. 2026-11-18 13:27 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  9. 2026-11-17 21:38 UTCEchelonGraph re-scored
  10. 2026-11-17 21:38 UTCVendor advisory
  11. 2026-11-17 21:38 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  12. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 59 more
  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-28 09:25 UTCOSV refresh
  9. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-25 13:47 UTCEchelonGraph re-scored
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-19 10:37 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  20. 2026-10-19 10:25 UTCNVD update
  21. 2026-10-19 09:52 UTCEchelonGraph re-scored
  22. 2026-10-19 09:52 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  23. 2026-10-19 09:39 UTCMITRE cvelistV5
  24. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-18 02:56 UTCEchelonGraph re-scored
  26. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-10-12 14:39 UTCEchelonGraph re-scored
  33. 2026-10-11 19:10 UTCEchelonGraph re-scored
  34. 2026-10-11 16:25 UTCEchelonGraph re-scored
  35. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-10-11 13:37 UTCEchelonGraph re-scored
  37. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-10-09 18:22 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  40. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-10-06 16:57 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  42. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-10-03 15:47 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  46. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-09-30 14:35 UTCEchelonGraph re-scored
  51. 2026-09-30 14:35 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  52. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-09-28 12:42 UTCEchelonGraph re-scored
  54. 2026-09-28 12:42 UTCGHSA enrichmentGHSA-5qvg-w7qr-xhvh
  55. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  56. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-09-25 11:30 UTCNVD update
  58. 2026-09-25 10:29 UTCEchelonGraph re-scored
  59. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98060?
CVE-2026-98060 is a high-severity vulnerability; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Reject resilient lock operations in rbtree callbacks __bpf_rbtree_add() keeps parent and link pointers live across calls to the program-supplied comparison callback. The verifier therefore requires the root's lock to remain…
When was the CVE record for CVE-2026-98060 published?
The CVE record for CVE-2026-98060 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-98060 actively exploited?
CVE-2026-98060 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-98060?
CVE-2026-98060 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-98060?
A fix for CVE-2026-98060 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98060 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-98060

Explore →

Is Your Infrastructure Affected by CVE-2026-98060?

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