All Threat Alerts
criticalCVE Alert
CVE-2025-68726

Critical Vulnerability: CVE-2025-68726

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

Thursday, July 30, 2026Vulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2025-68726 is rated CRITICAL โ€” exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Executive Summary

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

Why It Matters

CVE-2025-68726 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.8/10

๐Ÿ›ก๏ธWhat Defenders Should Check

  • Check if you are affected โ€” Review your asset inventory for products listed in CVE-2025-68726.
  • Apply available patches โ€” Visit vendor advisories for the latest security updates.
  • Monitor for exploitation โ€” Check your SIEM/IDS logs for related indicators.
  • Use Vulnios to continuously monitor your exposure to CVE-2025-68726 and similar vulnerabilities.

    References & Sources

    How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for SBOM-based CVE matching and Vulnios CVE feed continuous monitoring against your asset inventory. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat โ€” including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2025-68726?

    CVE-2025-68726 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. 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

    Am I affected?

    Affected technology is listed in the Affected Products section above. If your asset inventory contains any of them, assume in-scope until you can prove otherwise.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2025-68726. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts โ€” all in one platform.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios