When processing the header of an incoming message, libnv failed to properly validate the message size. The lack of validation allows a malicious program to write outside the bounds of a heap allocation. This can trigger a crash or system panic, and it may be possible for an unprivileged user to exploit the bug to elevate their privileges.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
13.5CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:13.5:-:*:*:*:*:*:* | ||
13.5CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:13.5:beta3:*:*:*:*:*:* | ||
13.5CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:13.5:p1:*:*:*:*:*:* | ||
13.5CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:13.5:p10:*:*:*:*:*:* | ||
13.5CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:13.5:p11:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.1 Bluesky, 0.1 Mastodon, and 0.4 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.