# CVE-2026-28529: cryptodev-linux <= 1.14 get_userbuf Use After Free LPE

> Local attackers can exploit a use-after-free flaw in the cryptodev-linux driver to achieve privilege escalation.

- **Severity:** High 8.5 (`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`)
- **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:** No
- **Published:** 25 Mar 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-vgx9-cpq5-rx9p

## What is CVE-2026-28529?

CVE-2026-28529 is a high-severity use after free vulnerability in cryptodev-linux, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-28529?

It affects 1 product.


Products: Cryptodev-Linux Cryptodev-Linux.

## How do I fix CVE-2026-28529?

No fix has been published for CVE-2026-28529 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-28529 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28529 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28529 and fix it if it is affected.

What it is: CVE-2026-28529 is a high-severity use after free vulnerability in cryptodev-linux, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28529 exists.

Affected product: cryptodev-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-2026-28529/ (Markdown: https://insights.sbomify.com/CVE-2026-28529/index.md)
```

## Sources

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

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