SECUFOCUSNOW
Home›CVE index›CVE-2025-68208
Review reviewHigh

CVE-2025-68208

Linux

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 ==...

CVSS
7.8
EPSS
0.13%
3.30% percentile
CISA KEV
Not listed
Published
2025.12.16
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.8

Vulnerability overview

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 ==...

Affected product and versions

Product
Linux
Affected versions
>= ab470fefce2837e66b771c60858118d50bb5bb10 < 64b12dca2b0abcb5fc0542887d18b926ea5cf711, >= 2793a8b015f7f1caadb9bce9c63dc659f7522676 < 9944c7938cd5b3f37b0afec0481c7c015e4f1c58, >= 2793a8b015f7f1caadb9bce9c63dc659f7522676 < 57e04e2ff56e32f923154f0f7bc476fcb596ffe7, >= 2793a8b015f7f1caadb9bce9c63dc659f7522676 < b0c8e6d3d866b6a7f73877f71968dbffd27b7785, >= 6.6.15 < 6.6.117, >= 6.7
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available