CVE-2026-98937

UNRATEDCVSS · not yet scoredElevated

Also known asEUVD-2026-108909 (ENISA EUVD) · GHSA-5cg4-h7ff-5xr5 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictPlan a fixWithin your standard update timelines — no confirmed exploitation yet.
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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

perf/core: Check kernel access when kernel callchains are requested

perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel.

However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it.

Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested.

This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
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)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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 BOD 26-04 block below.

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

October 23, 2026

Last Modified

October 26, 2026

References (4)

Vendor Advisories for CVE-2026-98937(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 20× 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.

  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-26 07:26 UTCGHSA enrichmentGHSA-5cg4-h7ff-5xr5
  11. 2026-10-26 07:25 UTCNVD update
  12. 2026-10-26 07:11 UTCEG score recompute
  13. 2026-10-26 07:11 UTCGHSA enrichmentGHSA-5cg4-h7ff-5xr5
  14. 2026-10-26 07:10 UTCMITRE cvelistV5
  15. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-25 13:46 UTCEG score recompute
  17. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-23 13:25 UTCNVD update
  19. 2026-10-23 12:25 UTCEG score recompute
  20. 2026-10-23 12:24 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

Frequently asked(4)

What is CVE-2026-98937?
CVE-2026-98937 is a vulnerability whose severity is not yet rated; its CVE record was published on October 23, 2026. In the Linux kernel, the following vulnerability has been resolved: perf/core: Check kernel access when kernel callchains are requested perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel. However, users can still request kernel callchain collection with…
When was the CVE record for CVE-2026-98937 published?
The CVE record for CVE-2026-98937 was published on October 23, 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-98937 actively exploited?
CVE-2026-98937 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).
How do I remediate CVE-2026-98937?
A fix for CVE-2026-98937 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98937 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-98937

Explore →

Is Your Infrastructure Affected by CVE-2026-98937?

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

Book a Demo →Browse All CVEs