CVE-2026-31413

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-12. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

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

bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR

maybe_fork_scalars() is called for both BPF_AND and BPF_OR when the source operand is a constant. When dst has signed range [-1, 0], it forks the verifier state: the pushed path gets dst = 0, the current path gets dst = -1.

For BPF_AND this is correct: 0 & K == 0. For BPF_OR this is wrong: 0 | K == K, not 0.

The pushed path therefore tracks dst as 0 when the runtime value is K, producing an exploitable verifier/runtime divergence that allows out-of-bounds map access.

Fix this by passing env->insn_idx (instead of env->insn_idx + 1) to push_stack(), so the pushed path re-executes the ALU instruction with dst = 0 and naturally computes the correct result for any opcode.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

April 12, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58bd87d0e69204dbd739e4387a1edb0c4b1644e7
generic

bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/342aa1ee995ef5bbf876096dc3a5e51218d76fa4

Vendor Advisories for CVE-2026-31413(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.80—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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1—

Weakness Classification(1)

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

All Vendor Advisories

(9)

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 5× in last 7d / 29× 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.

Showing the most recent 100 of 212 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31413?
CVE-2026-31413 is a high vulnerability published on April 12, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix unsound scalar forking in maybeforkscalars() for BPF_OR maybeforkscalars() is called for both BPFAND and BPFOR when the source operand is a constant. When dst has signed range [-1, 0], it forks the verifier state: the…
When was CVE-2026-31413 disclosed?
CVE-2026-31413 was first published in the National Vulnerability Database on April 12, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31413 actively exploited?
CVE-2026-31413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31413?
CVE-2026-31413 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31413?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31413, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-31413?

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

Start Free Scan →Browse All CVEs