Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-68208bpf: account for current allocated stack depth in widen_imprecise_scalars()

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: account for current allocated stack depth in widen_imprecise_scalars() The usage pattern for widen_imprecise_scalars() looks as follows: prev_st = find_prev_entry(env, ...); queued_st = push_stack(...); widen_imprecise_scalars(env, prev_st, queued_st); Where prev_st is an ancestor of the queued_st in the explored states tree. This ancestor is not guaranteed to have same allocated stack depth as queued_st. E.g. in the following case: def main(): for i in 1..2: foo(i) // same callsite, differnt param def foo(i): if i == 1: use 128 bytes of stack iterator based loop Here, for a second 'foo' call prev_st->allocated_stack is 128, while queued_st->allocated_stack is much smaller. widen_imprecise_scalars() needs to take this into account and avoid accessing bpf_verifier_state->frame[*]->stack out of bounds.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-68208, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected ab470fefce2837e66b771c60858118d50bb5bb10 – < 64b12dca2b0abcb5fc0542887d18b926ea5cf711
    • affected 2793a8b015f7f1caadb9bce9c63dc659f7522676 – < 9944c7938cd5b3f37b0afec0481c7c015e4f1c58
    • affected 2793a8b015f7f1caadb9bce9c63dc659f7522676 – < 57e04e2ff56e32f923154f0f7bc476fcb596ffe7
    • affected 2793a8b015f7f1caadb9bce9c63dc659f7522676 – < b0c8e6d3d866b6a7f73877f71968dbffd27b7785
    • affected 6.6.15 – < 6.6.117
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 6.6.117 – ≤ 6.6.*
    • unaffected 6.12.59 – ≤ 6.12.*
    • unaffected 6.17.9 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68208 badge
[![CVE-2025-68208](https://cveledger.app/badge/CVE-2025-68208.svg)](https://cveledger.app/cve/CVE-2025-68208)

Record last updated .