rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.
History

Sat, 05 Sep 2026 19:00:00 +0000

Type Values Removed Values Added
Description rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.
Title rpcapd memory leak in libpcap before 1.10.7
Weaknesses CWE-401
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Tcpdump

Published:

Updated: 2026-09-05T18:51:32.438Z

Reserved: 2026-07-29T17:47:46.571Z

Link: CVE-2026-18313

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-05T19:16:55.590

Modified: 2026-09-05T19:16:55.590

Link: CVE-2026-18313

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-05T20:30:17Z