# CVE-2025-0662: Uninitialized kernel memory disclosure via ktrace(2)

> An unprivileged user can leak up to 14 bytes of uninitialized kernel memory via the ktrace facility, potentially exposing sensitive kernel data.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-942x-h2h3-8wxm

## What is CVE-2025-0662?

CVE-2025-0662 is a medium-severity vulnerability in FreeBSD, published on 30 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In some cases, the ktrace facility will log the contents of kernel structures to userspace.  In one such case, ktrace dumps a variable-sized sockaddr to userspace.  There, the full sockaddr is copied, even when it is shorter than the full size.  This can result in up to 14 uninitialized bytes of kernel memory being copied out to userspace.

It is possible for an unprivileged userspace program to leak 14 bytes of a kernel heap allocation to userspace.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-0662?


## How do I fix CVE-2025-0662?

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

## Is CVE-2025-0662 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0662 and fix it if it is affected.

What it is: CVE-2025-0662 is a medium-severity vulnerability in FreeBSD, published on 30 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0662 in the wild and no public exploit code.

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

## Sources

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

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