Skip to main content

Linux Kernel CVE-2025-68726

CRITICAL
2025-12-24 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Critical
Disputed · 9.8 Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
4.7 MEDIUM

Bug is an internal Crypto API sizing error triggered by locally invoking a specific affected AEAD transform (AV:L/AC:H/PR:L); demonstrated impact is memory corruption and kernel crash, i.e. availability only (A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 30, 2026 - 07:03 vuln.today
CVE Published
Dec 24, 2025 - 11:16 cve.org
CRITICAL 9.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

crypto: aead - Fix reqsize handling

Commit afddce13ce81d ("crypto: api - Add reqsize to crypto_alg") introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks.

However, this is being recommended for use in all crypto algs instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in aead algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [1]

Add proper set_reqsize calls in the aead init function to properly initialize reqsize for these algorithms in the framework.

[1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b

AnalysisAI

Kernel-side memory corruption in the Linux kernel's crypto AEAD framework arises because AEAD algorithms began populating the generic cra_reqsize field (added by commit afddce13ce81d) without the framework being updated to translate it into a proper per-request size via crypto_aead_set_reqsize(). As a result, request buffers for affected AEAD transforms are undersized, producing out-of-bounds memory writes and kernel crashes when the algorithm is used. This is tracked as a Denial-of-Service class issue; no public exploit identified at time of analysis, and it is not listed in CISA KEV.

Technical ContextAI

The affected component is the Linux kernel Crypto API, specifically the AEAD (Authenticated Encryption with Associated Data) algorithm framework (e.g. GCM/CCM/authenc-style constructions). Commit afddce13ce81d introduced cra_reqsize in struct crypto_alg to centralize the per-request scratch size that ahash and acomp use. AEAD algorithms adopted cra_reqsize, but the AEAD framework's init path never propagates that value into the request context sizing that crypto_aead callers rely on, so tfm->reqsize stays wrong and request objects are allocated too small. The fix adds explicit set_reqsize calls in the AEAD init function. The root cause is a memory-safety/buffer-sizing defect (an out-of-bounds write / incorrect buffer length class, akin to CWE-787/CWE-131); the input lists CWE as N/A, so this classification is inferred from the description rather than assigned by NVD.

Affected ProductsAI

The affected product is the mainline and stable Linux kernel, in the window between the introduction of cra_reqsize by commit afddce13ce81d and the corrective commits. No exact kernel version range or CPE was provided in the input; affected/fixed points are identified only by stable-tree commit hashes 12b413f5460c393d1151a37f591140693eca0f84, 64377e66e187164bd6737112d07257f5f0feb681, and 9b04d8f00569573796dd05397f5779135593eb24 (git.kernel.org). Any distribution kernel that backported the cra_reqsize change to AEAD without the corresponding set_reqsize fix is potentially affected; distributors should map these commits to their own package versions.

RemediationAI

Upstream fix available as stable-tree commits (12b413f5, 64377e66, 9b04d8f0 at git.kernel.org/stable) that add the missing crypto_aead set_reqsize calls in the AEAD init function; a specific released/tagged kernel version was not provided, so update to your distribution's kernel build that incorporates these commits and reboot. Because the defect lives in the kernel Crypto API itself there is no meaningful userspace configuration workaround; the only compensating control is to avoid loading or using AEAD transforms that hit the miscomputed reqsize path (for example holding off on modules/features that newly rely on the affected algorithms), which is impractical for general workloads and may break disk/network encryption, so patching is strongly preferred over mitigation. Track your distributor's advisory keyed to CVE-2025-68726 for the exact fixed package version.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

CVE-2025-68726 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy