CVE-2025-39917: bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt
Stanislav reported that in bpf_crypto_crypt() the destination dynptr's
size is not validated to be at least as large as the source dynptr's
size before calling into the crypto backend with 'len = src_len'. This
can result in an OOB write when the destination is smaller than the
source.
Concretely, in mentioned function, psrc and pdst are both linear
buffers fetched from each dynptr:
psrc = __bpf_dynptr_data(src, src_len);
[...]
pdst = __bpf_dynptr_data_rw(dst, dst_len);
[...]
err = decrypt ?
ctx->type->decrypt(ctx->tfm, psrc, pdst, src_len, piv) :
ctx->type->encrypt(ctx->tfm, psrc, pdst, src_len, piv);
The crypto backend expects pdst to be large enough with a src_len length
that can be written. Add an additional src_len > dst_len check and bail
out if it's the case. Note that these kfuncs are accessible under root
privileges only.
Security readout for executives and security teams
Plain-English summary
CVE-2025-39917 is a Linux kernel flaw in BPF crypto handling. A destination buffer can be smaller than the source, allowing an out-of-bounds write. The source states these kernel functions require root privileges, so exposure is local and privileged, not remote unauthenticated.
Executive priority
Treat as high priority for Linux patch management, especially on systems where privileged local access is plausible. It is not described as remotely exploitable, but kernel memory corruption can materially affect system integrity and availability.
Technical view
In bpf_crypto_crypt(), src_len is passed to the crypto encrypt/decrypt backend without first confirming dst_len is large enough. If src_len exceeds dst_len, the backend may write past the destination dynptr. The fix adds a src_len > dst_len check and returns before the backend call.
Likely exposure
Systems running affected Linux kernel versions or builds containing the vulnerable BPF crypto code may be exposed. The provided sources identify Linux kernel impact but do not map affected distribution packages. Exposure depends on deployed kernel version and privileged access to the relevant BPF kfuncs.
Exploitation context
No active exploitation is stated in the provided sources, and KEV is false. Exploitation is local and privilege-gated per the CVE text, which says the kfuncs are accessible only under root privileges. Impact is still serious because the write occurs in kernel context.
Researcher notes
The key condition is src_len greater than dst_len in bpf_crypto_crypt() before encrypt/decrypt backend invocation. The source bundle names CWE-787 and CVSS 7.8. Evidence is incomplete for distribution-level package status and any real-world exploitation.
Mitigation direction
Update affected Linux kernels using vendor-supported packages containing the referenced stable fixes.
If immediate patching is unavailable, follow Linux distribution vendor guidance for temporary controls.
Restrict root and privileged local access to systems until patched.
Prioritize shared, multi-user, and high-value Linux hosts for remediation.
Validation and detection
Inventory running kernel versions across Linux assets.
Check vendor advisories or changelogs for the bpf_crypto_crypt destination length fix.
Verify deployed kernels include one of the referenced stable commits or downstream backports.
Confirm vulnerable kernels are removed from production after patch rollout.
Monitor CVE and vendor pages for revised affected-version or exploitation information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.