CVE-2025-40063 json
crypto: comp - Use same definition of context alloc and free ops
published 2025-10-28 12 mo ago modified 2026-10-19 20 d ago also EUVD-2025-36465
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
crypto: comp - Use same definition of context alloc and free ops
In commit 42d9f6c77479 ("crypto: acomp - Move scomp stream allocation code into acomp"), the crypto_acomp_streams struct was made to rely on having the alloc_ctx and free_ctx operations defined in the same order as the scomp_alg struct. But in that same commit, the alloc_ctx and free_ctx members of scomp_alg may be randomized by structure layout randomization, since they are contained in a pure ops structure (containing only function pointers). If the pointers within scomp_alg are randomized, but those in crypto_acomp_streams are not, then the order may no longer match. This fixes the problem by removing the union from scomp_alg so that both crypto_acomp_streams and scomp_alg will share the same definition of alloc_ctx and free_ctx, ensuring they will always have the same layout.
Patch / fix
- Linux Linux 6.17.3, 6.18
- linux Debian 14 6.17.6-1
debian advisories DEBIAN-CVE-2025-40063
- linux Ubuntu 25.10 6.17.0-14.14
- linux-aws Ubuntu 25.10 6.17.0-1007.7
- linux-gcp Ubuntu 25.10 6.17.0-1007.7
- linux-azure Ubuntu 25.10 6.17.0-1008.8
- linux-raspi Ubuntu 25.10 6.17.0-1008.8
- linux-riscv Ubuntu 25.10 6.17.0-14.14.1
- linux-oracle Ubuntu 25.10 6.17.0-1007.7
- linux-aws-6.17 Ubuntu 24.04 LTS 6.17.0-1007.7~24.04.1
ubuntu advisories UBUNTU-CVE-2025-40063
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source-longterm openSUSE Tumbleweed 6.18.16-1.1
- kernel-source openSUSE Tumbleweed 6.17.7-1.1
opensuse advisories openSUSE-SU-2026:10301-1openSUSE-SU-2025:15702-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-40063 updated cvss 6.1
kernel: crypto: comp - Use same definition of context alloc and free ops
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
Sources
- CVE List CVE-2025-40063
- NVD CVE-2025-40063
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.