CVE-2026-0799
published 2026-09-05CVE-2026-0799: In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but…
PriorityP343high8.7CVSS 3.1
AVLACLPRLUINSCCLIHAH
EPSS
0.11%
1.1th percentile
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| openshift | ose-rhel-coreos-8 | — | — |
| openshift | ose-rhel-coreos-9 | — | — |
| the_tcpdump_group | libpcap | < 1.10.7 | 1.10.7 |
| the_tcpdump_group | libpcap | — | — |
| ubuntu | libpcap | — | — |
CVSS provenance
nvdv3.18.7HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
vendor_redhat8.7HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
libpcap vulnerability
vendor_ubuntu·2026-09-25
CVE-2026-0799 libpcap vulnerability
Title: libpcap vulnerability
Summary: Applications using libpcap could be made to crash if given specially
crafted data.
It was discovered that libpcap did not properly validate BPF instructions
in some situation. An attacker could possibly use this issue to perform out
of bound memory operations.
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access
vendor_redhat·2026-09-05·CVSS 8.7
CVE-2026-0799 [HIGH] CWE-125 libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access
libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.
A flaw was found in libpcap. The Berkeley Packet Filter (BPF) interpreter in libpcap does not properly validate register indexes in BPF instructions. A local attacker could craft a malicious filter program to trigger an out-of-bounds r
VulDB
Tcpdump Group libpcap up to 1.10.6 BPF Interpreter out-of-bounds (EUVD-2026-72015)
vuldb·2026-09-05·CVSS 8.7
CVE-2026-0799 [HIGH] Tcpdump Group libpcap up to 1.10.6 BPF Interpreter out-of-bounds (EUVD-2026-72015)
A vulnerability, which was classified as problematic, was found in Tcpdump Group libpcap up to 1.10.6. This affects an unknown function of the component BPF Interpreter. Executing a manipulation can lead to out-of-bounds read.
This vulnerability is tracked as CVE-2026-0799. The attack is restricted to local execution. No exploit exists.
You should upgrade the affected component.
GHSA
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the
ghsa_unreviewed·2026-09-05
CVE-2026-0799 [HIGH] CWE-125 In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-0799 libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access [fedora-all]
bugzilla·2026-09-09·CVSS 8.7
CVE-2026-0799 [HIGH] CVE-2026-0799 libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access [fedora-all]
CVE-2026-0799 libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit
Bugzilla
CVE-2026-0799 libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access
bugzilla·2026-09-05·CVSS 8.7
CVE-2026-0799 [HIGH] CVE-2026-0799 libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access
CVE-2026-0799 libpcap: libpcap: Out-of-bounds read and write vulnerability allows arbitrary memory access
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.
2026-09-05
Published