libpcap 1.10.7 fixes infinite-loop flaw CVE-2026-6554
Original title: one more reason to update libpcap to at least 1.10.7
A later-found, more common configuration can trigger the same loop first scored CVSS 5.5.
Denis Ovsienko told oss-security that libpcap 1.10.7, released more than a month earlier, fixed CVE-2026-6554, an infinite loop. At release the only known vector was an uncommon configuration, and the CVE scored CVSS 5.5. He says another vector can trigger the same flaw with a more common configuration when a vulnerable libpcap is used. The note is cut off before naming that configuration.
Unconfirmed: The post is cut off before describing the second configuration or listing affected versions.
- libpcap 1.10.7 was released more than a month before the October 22 note.
- The original attack vector was described as a rather uncommon configuration.
- At release the CVE scored CVSS 5.5, rated medium.
- The post says a second vector uses a more common configuration.
Impact: infinite loop via a more common libpcap configuration
| Product | Affected | Fixed in |
|---|---|---|
| libpcap | — | 1.10.7 |
- 1.Update libpcap to at least 1.10.7
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-6554 | libpcap BPF interpreter treats the offset in the 'ja L' BPF instruction as a signed integer to implement looping via backward jumps, but it does not limit the… | 7.5 | <1% |
From the original article
Posted by Denis Ovsienko on Oct 22 To whom it may concern, libpcap 1. 10. 7, which was released more than a month ago, among other things has fixed CVE-2026-6554 (an infinite loop).
seclists.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.