Skip to main content

Cryptodev Linux CVE-2026-28529

| EUVDEUVD-2026-15408 HIGH
Use After Free (CWE-416)
2026-03-25 VulnCheck GHSA-vgx9-cpq5-rx9p
8.5
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Access /dev/crypto device
  2. Delivery
    Call get_userbuf function repeatedly
  3. Exploit
    Decrement page reference counts
  4. Execution
    Trigger use-after-free condition
  5. Impact
    Execute arbitrary code with elevated privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Attacker must have low-privilege local user access to a Linux system running cryptodev-linux version 1.14 or prior with the /dev/crypto device driver loaded and accessible. No victim interaction required.

Impact

This vulnerability represents a critical real-world risk despite the absence of a numerical CVSS score in the provided data. The exploit scenario is highly favorable to attackers: the attack vector is local (requiring access to /dev/crypto), the attack complexity is low (the vulnerability can be triggered through controlled page manipulation), and the privilege level required is user-level access to the device file. The availability of publicly disclosed proof-of-concept exploits on GitHub (gist.github.com/n4sm/0fd2479e0c23e0fa2f192cd8fda45750) and detailed technical writeups (nasm.re) significantly accelerates exploitation risk. Use-after-free vulnerabilities are consistently automatable and lead to arbitrary code execution, placing this squarely in the technical impact category of complete system compromise. From an SSVC perspective, exploitation is demonstrated (public POC exists), the attack is automatable, and the technical impact is total system compromise—all factors pointing to immediate remediation priority. The primary limiting factor is that exploitation requires local access; systems restricting user access to /dev/crypto or running kernel versions with the patch mitigate this significantly.

Exploit ScenarioDerived

An unprivileged local attacker with standard user account access to a system running cryptodev-linux 1.14 can open the /dev/crypto device and craft a sequence of cryptographic operations that manipulate page reference counts in the get_userbuf function. By repeatedly decrementing reference counts on pages under their control, the attacker triggers a use-after-free condition, allowing them to overwrite kernel memory and ultimately execute arbitrary code with root privileges. A publicly available proof-of-concept exploit (referenced at https://nasm.re/posts/cryptodev-linux-vuln/ and https://gist.github.com/n4sm/0fd2479e0c23e0fa2f192cd8fda45750) demonstrates this attack path, making exploitation straightforward for attackers with local access.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 25, 2026

cryptodev-linux 1.14 and earlier suffer from a use-after-free vulnerability in the /dev/crypto device driver that enables local privilege escalation through reference count manipulation. Attackers with local access can exploit this memory corruption flaw to gain elevated privileges on affected systems. Public exploit code exists for this vulnerability.

Earlier versions of this analysis (1)
v1 Mar 25, 2026 - 13:30 CVSS 8.5

A use-after-free vulnerability exists in cryptodev-linux version 1.14 and prior within the get_userbuf function of the /dev/crypto device driver, allowing local users with access to the /dev/crypto interface to trigger memory corruption conditions leading to local privilege escalation. Publicly available proof-of-concept exploits exist, and a vendor patch is available, making this an actively exploitable vulnerability for any system running the affected cryptodev-linux versions without mitigation.

RemediationAI

Immediately upgrade cryptodev-linux to a version newer than 1.14 that includes the patch from PR #104 (https://github.com/cryptodev-linux/cryptodev-linux/pull/104). If immediate patching is not feasible, restrict access to the /dev/crypto device by removing user permissions on the device file (chmod 600 /dev/crypto) and ensuring only privileged system services that require cryptographic acceleration can access it. Audit system configurations to identify any unnecessary exposure of /dev/crypto to untrusted local users, and consider disabling the cryptodev-linux module entirely if hardware crypto acceleration is not required. Apply the vendor patch as soon as possible, as no effective workaround fully eliminates the exploitation risk once the device is exposed.

Affected VersionsENISA

cryptodev-linux 0 ≤1.14

Affected Packages

euvd cryptodev_linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The cryptodev-linux project provides a Linux kernel device driver (/dev/crypto) that exposes cryptographic hardware acceleration and software implementations to userspace applications via the /dev/crypto character device interface. The vulnerability resides in the get_userbuf function, which is responsible for managing page reference counts when handling user-supplied buffers for cryptographic operations. The root cause is classified under CWE-416 (Use After Free), a memory safety defect where the driver fails to properly track page reference counts, permitting attackers to decrement reference counts on controlled pages multiple times. This results in premature page deallocation while the kernel still holds references to those pages, creating a use-after-free condition exploitable for memory corruption and privilege escalation. The affected product is identified by CPE string cpe:2.3:a:cryptodev-linux:cryptodev-linux:*:*:*:*:*:*:*:*, covering all versions up to and including 1.14.

Know when Cryptodev Linux gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.5 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck) · only source for this CVE.

CVSS VectorVendor: VulnCheck

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
PoC Detected
Mar 25, 2026 - 15:41 vuln.today
Public exploit code
Patch released
Mar 25, 2026 - 13:30 nvd
Patch available
CVE Published
Mar 25, 2026 - 13:00 nvd
HIGH 8.5

DescriptionCVE.org

cryptodev-linux version 1.14 and prior contain a page reference handling flaw in the get_userbuf function of the /dev/crypto device driver that allows local users to trigger use-after-free conditions. Attackers with access to the /dev/crypto interface can repeatedly decrement reference counts of controlled pages to achieve local privilege escalation.

Executive ViewAI

Why It Matters

CVE-2026-28529 presents significant security risk, a use-after-free vulnerability rated CVSS 8.5. Successful exploitation could significantly impact the confidentiality, integrity, or availability of affected systems. Proof-of-concept code is publicly available, increasing the risk of exploitation. A patch is available and should be applied as part of regular vulnerability management.

Business Impact: Severe
Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Enable ASLR and DEP where available; (2) Implement network segmentation; (3) Monitor for exploitation indicators.

Threat Intelligence Overview

EPSS Score
0.0%
Top 98% exploitable
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

62
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

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