# CVE-2025-68724: crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id

> An integer overflow in the Linux kernel's asymmetric key generation allows attackers to trigger buffer overflows via malicious X.509 certificates, potentially leading to code execution or crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-73159, BELL-CVE-2025-68724, DEBIAN-CVE-2025-68724, GHSA-fhmc-454p-hp6f, ROOT-OS-DEBIAN-11-CVE-2025-68724, ROOT-OS-DEBIAN-12-CVE-2025-68724, ROOT-OS-UBUNTU-2204-CVE-2025-68724, ROOT-OS-UBUNTU-2404-CVE-2025-68724, UBUNTU-CVE-2025-68724

## What is CVE-2025-68724?

CVE-2025-68724 is a high-severity vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id

Use check_add_overflow() to guard against potential integer overflows
when adding the binary blob lengths and the size of an asymmetric_key_id
structure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a
possible buffer overflow when copying data from potentially malicious
X.509 certificate fields that can be arbitrarily large, such as ASN.1
INTEGER serial numbers, issuer names, etc.

## Which versions are affected by CVE-2025-68724?


## How do I fix CVE-2025-68724?

Apply the vendor's patch.

## Is CVE-2025-68724 being exploited?

There is no known exploitation of CVE-2025-68724 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68724 and fix it if it is affected.

What it is: CVE-2025-68724 is a high-severity vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68724 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68724/ (Markdown: https://insights.sbomify.com/CVE-2025-68724/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68724
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68724
- OSV: https://osv.dev/vulnerability/CVE-2025-68724

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68724/
Summaries are generated and may contain mistakes; the official description above is the record.