CVE-2026-132049: Lldpd: lldpd: out-of-bounds read in liblldpctl on a short lldp-med location
A flaw was found in lldpd. The service fails to verify that Link Layer ...
Other sources
A flaw was found in lldpd's liblldpctl. The daemon stores an LLDP-MED location from a neighbor without checking that the body matches the length the location claims. The civic-address CA-element iterator uses that length byte and can read past the end of the buffer. The coordinate getters read a coordinate location that is shorter than 16 bytes the same way. The first civic over-read is in the iterator value function. lldpcli calls the iterator only after the integer location-format getter, and that getter already rejects both bad lengths, so lldpcli does not reach the over-read. A client that walks civic elements or reads coordinate fields without that integer check can disclose adjacent heap bytes from the client process. The fix is upstream commit f39254f, released in lldpd 1.0.23.
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/lldpdto a version that resolves this vulnerability.Fixed in 1.0.23-1 - Upgrade
Upgrade
lldpdto a version that resolves this vulnerability.Fixed in 1.0.23Patch f39254f
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must be adjacent on the local network and able to send crafted LLDP-MED packets that lldpd accepts from a network neighbor. The disclosure occurs in a client application using liblldpctl to parse the malicious neighbor location data.
Are all lldpd command-line clients affected?
lldpcli does not reach the described over-read path. It calls the integer location-format getter before iterating civic-address elements, and that getter rejects the malformed lengths involved.
What application behavior is unsafe?
A liblldpctl client is at risk if it walks LLDP-MED civic-address elements or reads coordinate fields without first using the integer location-format getter to validate the location data. Malformed civic element lengths and coordinate locations shorter than 16 bytes can cause reads beyond the stored buffer and disclose adjacent heap memory.