CVE-2026-32848: NetBSD cryptodev Race Condition Double-Free via cryptodev_op()
NetBSD prior to commit ec8451e contains a race condition vulnerability in cryptodev_op() within the opencrypto subsystem that allows local attackers to trigger a double-free condition by concurrently issuing CIOCCRYPT operations on the same session identifier on SMP systems. Attackers can exploit mutable per-operation state embedded in the csession struct to corrupt kernel heap memory.
Security readout for executives and security teams
Plain-English summary
This is a local NetBSD kernel memory-safety flaw. A logged-in attacker can race crypto operations on the same session and trigger a double-free, corrupting kernel heap memory. The supplied scoring points to availability impact, not data theft or direct remote compromise.
Executive priority
Treat this as a moderate-priority hardening item. It is not presented as remotely exploitable or actively exploited, but kernel heap corruption on shared NetBSD hosts can create outage risk and may justify faster maintenance scheduling.
Technical view
The issue is a race condition in NetBSD opencrypto cryptodev_op(). Concurrent CIOCCRYPT operations against one session identifier on SMP systems can reuse mutable per-operation state in csession, leading to double-free behavior and kernel heap corruption. The CVSS v4 vector is local, high complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure appears limited to NetBSD systems built from affected src before commit ec8451e, especially SMP systems where untrusted local users can reach cryptodev functionality. The bundle does not identify specific released NetBSD versions or distributions carrying the flaw.
Exploitation context
The bundle includes a public technical write-up tagged as exploit, but KEV is false and no cited source states active exploitation. Exploitation requires local access, low privileges, high attack complexity, and concurrent operations on the same crypto session.
Researcher notes
Key uncertainty is release mapping: the source bundle names NetBSD src before commit ec8451e but does not list affected release numbers. Focus validation on commit presence, cryptodev exposure, SMP configuration, and local account threat model. Do not claim active exploitation from the provided evidence.
Mitigation direction
Apply NetBSD commit ec8451efc1565516aba9e7047e1a1a1ce7953a2f or a vendor branch containing it.
Check NetBSD guidance for supported release backports and exact package or source update paths.
Prioritize shared, multi-user, or exposed NetBSD hosts where local account abuse is plausible.
Avoid relying on undocumented workarounds; use vendor-confirmed remediation where available.
Validation and detection
Inventory NetBSD systems and determine whether their source tree includes commit ec8451e.
Confirm whether affected hosts are SMP and permit untrusted local user access.
Review kernel or source package provenance against NetBSD vendor branches containing the fix.
Monitor vulnerability sources for release-specific advisories not present in the bundle.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.