CVE-2026-98150

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

bpf: Fix BPF_F_CPU validation for sparse CPU IDs

BPF_F_CPU stores the target CPU ID in the upper 32 bits of the map operation flags. bpf_map_check_op_flags() currently compares that ID with num_possible_cpus(), which is the number of possible CPUs rather than a bound on CPU IDs.

On an arm64 QEMU guest with a CPU device-tree hole, the possible CPU mask was 0,2-3. A userspace program using raw bpf() syscalls creates a BPF_MAP_TYPE_PERCPU_ARRAY and performs update and lookup operations for each CPU by setting BPF_F_CPU and the CPU ID in the flags.

With the old check, CPU 1 is incorrectly accepted while valid CPU 3 is rejected with -ERANGE. The CPU 1 update then reaches the per-CPU map access path and triggers:

Unable to handle kernel paging request at virtual address ... pc : __pi_memcpy_generic+0x5c/0x22c lr : bpf_percpu_array_update+0x2dc/0x2e8 Call trace: __pi_memcpy_generic bpf_map_update_value map_update_elem __sys_bpf

Check the CPU ID against nr_cpu_ids and cpu_possible() instead. This rejects CPU IDs outside the valid range and CPUs absent from the possible mask, while allowing valid sparse CPU IDs.

CVSS v3
7.0
EG Score
7.0HIGHhigh confidence
EG Risk
36
EG Risk 36/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

bpf: Fix BPF_F_CPU validation for sparse CPU IDs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed54bf564ac52699cf4def3d0c2125d493e756f9
generic

bpf: Fix BPF_F_CPU validation for sparse CPU IDs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bdc5941f6eeef90b76a07fd8ca38ac1933ba2195

Vendor Advisories for CVE-2026-98150(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 24× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-05 01:56 UTCEG score recompute
  2. 2026-10-05 01:56 UTCGHSA enrichment
  3. 2026-10-04 23:23 UTCEPSS rescore
  4. 2026-10-04 14:02 UTCGHSA enrichment
  5. 2026-10-04 02:07 UTCEG score recompute
  6. 2026-10-04 02:07 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 14:13 UTCGHSA enrichment
  9. 2026-10-03 02:18 UTCGHSA enrichment
  10. 2026-10-02 14:20 UTCGHSA enrichment
  11. 2026-10-02 02:23 UTCEG score recompute
  12. 2026-10-02 02:23 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 14:22 UTCGHSA enrichment
  15. 2026-10-01 02:26 UTCEG score recompute
  16. 2026-10-01 02:26 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 14:32 UTCGHSA enrichment
  19. 2026-09-30 02:40 UTCEG score recompute
  20. 2026-09-30 02:40 UTCGHSA enrichment
  21. 2026-09-29 14:46 UTCGHSA enrichment
  22. 2026-09-29 02:49 UTCEG score recompute
  23. 2026-09-29 02:49 UTCGHSA enrichment
  24. 2026-09-28 14:54 UTCGHSA enrichment
  25. 2026-09-28 02:59 UTCGHSA enrichment
Show 17 more
  1. 2026-09-27 15:04 UTCEG score recompute
  2. 2026-09-27 15:04 UTCGHSA enrichment
  3. 2026-09-27 13:49 UTCEPSS rescore
  4. 2026-09-27 03:09 UTCEG score recompute
  5. 2026-09-27 03:08 UTCGHSA enrichment
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-26 15:13 UTCGHSA enrichment
  8. 2026-09-26 03:19 UTCEG score recompute
  9. 2026-09-26 03:19 UTCGHSA enrichment
  10. 2026-09-25 15:23 UTCEG score recompute
  11. 2026-09-25 15:23 UTCGHSA enrichment
  12. 2026-09-25 14:51 UTCEG score recompute▲ 7.00
  13. 2026-09-25 14:51 UTCGHSA enrichment
  14. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  15. 2026-09-25 11:30 UTCNVD update
  16. 2026-09-25 10:48 UTCEG score recompute
  17. 2026-09-25 10:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98150?
CVE-2026-98150 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix BPFFCPU validation for sparse CPU IDs BPFFCPU stores the target CPU ID in the upper 32 bits of the map operation flags. bpfmapcheckopflags() currently compares that ID with numpossiblecpus(), which is the number of…
When was CVE-2026-98150 disclosed?
CVE-2026-98150 was first published on September 25, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98150 actively exploited?
CVE-2026-98150 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98150?
CVE-2026-98150 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98150?
No fix for CVE-2026-98150 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-98150 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-98150

Explore →

Is Your Infrastructure Affected by CVE-2026-98150?

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

Book a Demo →Browse All CVEs