Home/CVE/cryptodev-linux version 1.14 and prior contain a page reference handling flaw in the get_userbuf function of the /dev/cr
CVE
CVE-2026-28529
cryptodev-linux version 1.14 and prior contain a page reference handling flaw in the get_userbuf function of the /dev/cr
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.
EPSS 0.0002
EPSS exploitation odds0.02% · top 94%
Monitor
- ⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-28529, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
▣
Severity & exploitation scoring
EPSS exploitation probability
0.02%
Top 94%odds of exploitation in the next 30 days
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
no
Tech impact
total
⬡
Weakness Classification
CWE-416Use After Free
▤
Related CVEs
4CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2006-4434
Use-after-free vulnerability in Sendmail before 8.13.8 allows remote attackers t...
same CWE-416
HIGH
CVE-2006-4997
The clip_mkip function in net/atm/clip.c of the ATM subsystem in Linux kernel al...
same CWE-416
HIGH
CVE-2007-3929
Use-after-free vulnerability in the BitTorrent support in Opera before 9.22 allo...
same CWE-416
CVE-2008-0077
Use-after-free vulnerability in Microsoft Internet Explorer 6 SP1, 6 SP2, and an...
same CWE-416
HIGH
🔗
References & Sources
4Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.