CVE-2025-68378: bpf: Fix stackmap overflow check in __bpf_get_stackid()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 03fe4c886667b3a09b9d6afc03bbc68afb35c82b, 23f852daa4bab4d579110e034e4d513f7d490846, 2a008f6de163279deffd488c1deab081bce5667c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 03fe4c886667b3a09b9d6afc03bbc68afb35c82b, 23f852daa4bab4d579110e034e4d513f7d490846, 2a008f6de163279deffd488c1deab081bce5667c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 24, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 90805175a206f784b6a77f16f07b07f6803e286b, 398ac11f4425d1e52aaf0d05d4fc90524e1a5b5e, e750f78c4ed7cefbcefb9769b3b9e08033db39da, 6c4f243b58f5362e983386488b2d563764c567af, 5.18affected
- ee2a098851bfbe8bcdd964c0121f4246f00ff41e and later · before 03fe4c886667b3a09b9d6afc03bbc68afb35c82baffected · git
- ee2a098851bfbe8bcdd964c0121f4246f00ff41e and later · before d6028caa0ee39dccd005468adfa3223b92bd3ad3affected · git
- ee2a098851bfbe8bcdd964c0121f4246f00ff41e and later · before d1f424a77b6bd27b361737ed73df49a0158f1590affected · git
- ee2a098851bfbe8bcdd964c0121f4246f00ff41e and later · before 2a008f6de163279deffd488c1deab081bce5667caffected · git
- ee2a098851bfbe8bcdd964c0121f4246f00ff41e and later · before 4669a8db976c8cbd5427fe9945f12c5fa5168ff3affected · git
- ee2a098851bfbe8bcdd964c0121f4246f00ff41e and later · before 23f852daa4bab4d579110e034e4d513f7d490846affected · git
- 5.10.110 and later · before 5.11affected · semver
- 5.15.33 and later · before 5.16affected · semver
- 5.16.19 and later · before 5.17affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68376Dec 24, 2025 · coresight: ETR: Fix ETR buffer use-after-free issue0Monitor
- ← EarlierCVE-2025-68377Dec 24, 2025 · ns: initialize ns_list_node for initial namespaces0Monitor
- Later →CVE-2025-68379Dec 24, 2025 · RDMA/rxe: Fix null deref on srq->rq.queue after resize failure31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 03fe4c886667b3a09b9d6afc03bbc68afb35c82b | Vendor (CNA) |
| Linux Linux | 23f852daa4bab4d579110e034e4d513f7d490846 | Vendor (CNA) |
| Linux Linux | 2a008f6de163279deffd488c1deab081bce5667c | Vendor (CNA) |
| Linux Linux | 4669a8db976c8cbd5427fe9945f12c5fa5168ff3 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5.17 | Vendor (CNA) |
| Linux Linux | 5.18 | Vendor (CNA) |
| Linux Linux | d1f424a77b6bd27b361737ed73df49a0158f1590 | Vendor (CNA) |
| Linux Linux | d6028caa0ee39dccd005468adfa3223b92bd3ad3 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.63-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/23f852daa4bab4d579110e034e4d513f7d490846
- git.kernel.org/stable/c/2a008f6de163279deffd488c1deab081bce5667c
- git.kernel.org/stable/c/4669a8db976c8cbd5427fe9945f12c5fa5168ff3
- git.kernel.org/stable/c/d1f424a77b6bd27b361737ed73df49a0158f1590
- git.kernel.org/stable/c/d6028caa0ee39dccd005468adfa3223b92bd3ad3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.