Skip to main content
VulnerabilityPublished Updated

CVE-2025-68378: Linux kernel · bpf: Fix stackmap overflow check in __bpf_get_stackid()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in d6028caa0ee39dccd005468adfa3223b92bd3ad3 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d6028caa0ee39dccd005468adfa3223b92bd3ad3, d1f424a77b6bd27b361737ed73df49a0158f1590, 4669a8db976c8cbd5427fe9945f12c5fa5168ff3 +6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.10.110 <5.11
  • >=5.15.33 <5.16
  • >=5.16.19 <5.17
  • >=5.17.2 <5.18
Fixed in
  • d6028caa0ee39dccd005468adfa3223b92bd3ad3
  • d1f424a77b6bd27b361737ed73df49a0158f1590
  • 4669a8db976c8cbd5427fe9945f12c5fa5168ff3
  • 23f852daa4bab4d579110e034e4d513f7d490846
  • 5.18
  • 5.17
  • 5.16
  • 5.11
  • 2a008f6de163279deffd488c1deab081bce5667c
LinuxLinuxAffected
  • =5.18
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stackmap overflow check in __bpf_get_stackid() Syzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid() when copying stack trace data. The issue occurs when the perf trace contains more stack entries than the stack map bucket can hold, leading to an out-of-bounds write in the bucket's data array.

References

Community reviews

Loading reviews…