Bug 2575741 (CVE-2026-132049)

Summary: CVE-2026-132049 lldpd: lldpd: out-of-bounds read in liblldpctl on a short LLDP-MED location
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in lldpd. The service fails to verify that Link Layer Discovery Protocol - Media Endpoint Discovery (LLDP-MED) location records received from network neighbors match their declared lengths. An adjacent attacker on the local network can exploit this flaw by sending crafted packets, causing client applications using the liblldpctl library to read past buffer boundaries when parsing location data. This issue can lead to an information disclosure of adjacent process memory.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2575751    
Bug Blocks:    

Description OSIDB Bzimport 2026-11-18 10:02:08 UTC
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.