Safeguard
Vulnerability Analysis•

CVE-2022-23085: High Integer Overflow in FreeBSD netmap

CVE-2022-23085 is an integer overflow in FreeBSD netmap scored 8.2. Affects systems with netmap in devfs_ruleset. Update FreeBSD and reboot.

Safeguard Security Team
3 min read

CVE-2022-23085 is a high severity integer overflow in FreeBSD's netmap code, scored 8.2 by NVD. A privileged process in a jail could corrupt kernel memory and affect the host. Only systems that include netmap in their devfs_ruleset are exposed. Update to a patched FreeBSD release and reboot.

What's affected

This CVE shares advisory SA-22:04 with CVE-2022-23084. FreeBSD says all supported versions at the time were affected, namely 13.0, 13.1 at release candidate stage, and 12.3.

The advisory lists these corrections: stable/13 on 2022-03-19, stable/12 on 2022-03-20, and release branches on 2022-04-06. Fixed release levels are 13.1-RC1-p1, 13.0-RELEASE-p11 and 12.3-RELEASE-p5.

The condition that limits exposure is the same: only systems that include netmap in their devfs_ruleset are affected. A default installation does not. The advisory offers no workaround.

The score is 8.2 in the NVD record, a little higher than the 7.5 given to the sibling timing flaw, and the record carries two weakness classes, out-of-bounds write and a classic buffer copy without size check. The advisory itself gives no numeric severity, so the figure comes from NVD alone.

Weakness class per the record: CWE-787, CWE-120.

How to check if you're exposed

Run these on each FreeBSD host:

freebsd-version -ku
devfs rule show

The first shows kernel and userland patch levels. Compare them with 13.0-RELEASE-p11, 13.1-RC1-p1 or 12.3-RELEASE-p5, or newer. The second helps you see whether any ruleset exposes netmap to jails.

If you build from source, confirm the branch was built from a commit dated after the correction date for your branch in the advisory. Vendors who ship FreeBSD inside appliances may publish their own notice; the NetApp bulletin referenced in the record is one example.

What to do now

  1. Identify hosts that expose netmap to jails through a devfs ruleset.
  2. Update with freebsd-update or by applying the signed source patch from the advisory, then reboot.
  3. Confirm the new patch level with freebsd-version -ku.
  4. If you cannot patch yet, stop exposing netmap to jails, since the advisory lists no other workaround.

Why it matters

A user supplied integer option was passed to the request copy routine without checking whether it would overflow. When arithmetic wraps around, a size or offset that looked safe becomes a small number, and later code writes past the end of a buffer. Here that buffer is in the kernel.

The bug class is old and well understood, but its impact depends on where it lives. In the kernel, memory corruption can lead to code running with full system rights. In a jail setup, the host is supposed to be out of reach.

Because exposure needs an unusual device ruleset, risk is concentrated in a small set of systems. Those are the ones to patch first, and to review for other devices exposed to jails.

Quick check

Why do two netmap CVEs share one advisory?

They are two separate input validation bugs in the same request copying code, so FreeBSD fixed and announced them together in SA-22:04.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.