Summary
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.
Fixed packages 7
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · 22.04 LTS 22.04:LTS | libpcap | 1.10.1-4ubuntu1.22.04.2 |
| Ubuntu · 24.04 LTS 24.04:LTS | libpcap | 1.10.4-4.1ubuntu3.1 |
| Ubuntu · 26.04 LTS 26.04:LTS | libpcap | 1.10.6-1ubuntu1.1 |
| Ubuntu · Pro 14.04 LTS Pro:14.04:LTS | libpcap | 1.5.3-2ubuntu0.1+esm1 |
| Ubuntu · Pro 16.04 LTS Pro:16.04:LTS | libpcap | 1.7.4-2ubuntu0.1+esm1 |
| Ubuntu · Pro 18.04 LTS Pro:18.04:LTS | libpcap | 1.8.1-6ubuntu1.18.04.2+esm1 |
| Ubuntu · Pro 20.04 LTS Pro:20.04:LTS | libpcap | 1.9.1-3ubuntu1.20.04.1+esm1 |
Vulnerabilities 1
-
High 8.7
OOBR and OOBW in libpcap before 1.10.7
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 p…
References
-
report
https://ubuntu.com/security/CVE-2026-0799