A buffer over-read exists in the function crc64ib in crc64.c in nasmlib in Netwide Assembler (NASM) 2.14rc16.

published 2019-01-29 7y ago modified 2026-06-17 4mo ago also EUVD-2019-16697

cvss: 5.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

A buffer over-read exists in the function crc64ib in crc64.c in nasmlib in Netwide Assembler (NASM) 2.14rc16. A crafted asm input can cause segmentation faults, leading to denial-of-service.

Is CVE-2019-7147 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-7147 updated 2026-11-07 cvss 5.5

nasm: Buffer over-read in function crc64ib in crc64.c resulting in denial of service

Red Hat Enterprise Linux 5 nasm Red Hat Enterprise Linux 6 nasm, nasm-rdoff Red Hat Enterprise Linux 7 nasm, nasm-rdoff Red Hat Enterprise Linux 8 nasm
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

bugzilla.nasm.us https://bugzilla.nasm.us/show_bug.cgi?id=3392544 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.5	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-125 Out-of-bounds Read

References

bugzilla.nasm.us /show_bug.cgi?id=3392544
exploit, issue-tracking, third-party-advisory

Sources

CVE List CVE-2019-7147
NVD CVE-2019-7147

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.