cve.bz

CVE-2025-39917 linux linux kernel: Out-of-bounds Write

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-01-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-39917 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-39917?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-39917?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-39917 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.10 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.48
Linux6.166.16.8
Linuxlater releases6.17

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.48-1DEBIAN-CVE-2025-39917
Debian14linux6.16.8-1DEBIAN-CVE-2025-39917
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-39917
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-39917
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-39917
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-39917
Ubuntu24.04:LTSlinux-intel, linux-riscv, linux-oem-6.8 and 17 moreno fix listedUBUNTU-CVE-2025-39917
Ubuntu25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-39917
UbuntuPro:Realtime:24.04:LTSlinux-realtime-6.14no fix listedUBUNTU-CVE-2025-39917
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.8.1SUSE-SU-2026:20021-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 5 more6.12.0-160000.8.1SUSE-SU-2026:20015-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.8.1.160000.2.5SUSE-SU-2026:20015-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.8.1.160000.2.5SUSE-SU-2026:20012-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.8.1SUSE-SU-2026:20012-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.8.1SUSE-SU-2026:20562-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.8.1.160000.2.5openSUSE-SU-2025:20172-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 8 more6.12.0-160000.8.1openSUSE-SU-2025:20172-1
Alpaquita25linux-lts6.12.51-r0BELL-CVE-2025-39917
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-39917

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The patch prevents an out-of-bounds write in bpf_crypto_crypt() by rejecting cases where the source dynptr is larger than the destination (src_len > dst_len).

Impact is kernel memory corruption (high integrity/availability impact).

For the CVSS the PR:H because these BPF crypto kfuncs are root-only, so only privileged users can invoke them and supply mismatched dynptr sizes.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-39917.

References

Check your stackJSON