# CVE-2026-32849: NetBSD Signed Integer Overflow in cryptodev_op via cryptodev.c

> A local attacker can trigger a kernel panic via integer overflow in NetBSD's cryptodev module, causing denial of service.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/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:** 18 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-rf6w-j5hg-8rcv

## What is CVE-2026-32849?

CVE-2026-32849 is a medium-severity vulnerability in NetBSD src, published on 18 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NetBSD prior to commit ec8451e contains a signed integer overflow vulnerability in the cryptodev_op() function in sys/opencrypto/cryptodev.c where the local variable iov_len is declared as a signed int but assigned from an unsigned cop->dst_len value, causing undefined behavior when cop->dst_len exceeds INT_MAX. A local attacker with access to /dev/crypto and a compression session type can exploit this vulnerability by providing a dst_len value exceeding INT_MAX to trigger a kernel panic through NULL pointer dereference when CONFIG_SVS is disabled and corrupted UIO pointer arithmetic.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-32849 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32849 is a medium-severity vulnerability in NetBSD src, published on 18 May 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-32849 exists.

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

## Sources

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

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