# CVE-2024-42416: Multiple issues in ctl(4) CAM Target Layer

> A guest VM or remote iSCSI initiator can exploit a kernel validation flaw to achieve code execution on the host, typically within the bhyve process.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-hgfp-qxpq-6q7w

## What is CVE-2024-42416?

CVE-2024-42416 is a high-severity memory corruption vulnerability in Freebsd Freebsd, published on 5 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ctl_report_supported_opcodes function did not sufficiently validate a field provided by userspace, allowing an arbitrary write to a limited amount of kernel help memory.

Malicious software running in a guest VM that exposes virtio_scsi can exploit the vulnerabilities to achieve code execution on the host in the bhyve userspace process, which typically runs as root.  Note that bhyve runs in a Capsicum sandbox, so malicious code is constrained by the capabilities available to the bhyve process.  A malicious iSCSI initiator could achieve remote code execution on the iSCSI target host.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-823 (Use of Out-of-range Pointer Offset), CWE-790 (Improper Filtering of Special Elements)

## Which versions are affected by CVE-2024-42416?

It affects 1 product.


Products: Freebsd Freebsd.

## How do I fix CVE-2024-42416?

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

## Is CVE-2024-42416 being exploited?

There is no known exploitation of CVE-2024-42416 in the wild and no public exploit code.

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42416 and fix it if it is affected.

What it is: CVE-2024-42416 is a high-severity memory corruption vulnerability in Freebsd Freebsd, published on 5 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42416 in the wild and no public exploit code.

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

## Sources

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

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