Bug 2575741 (CVE-2026-132049) - CVE-2026-132049 lldpd: lldpd: out-of-bounds read in liblldpctl on a short LLDP-MED location
Summary: CVE-2026-132049 lldpd: lldpd: out-of-bounds read in liblldpctl on a short LLD...
Keywords:
Status: NEW
Alias: CVE-2026-132049
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2575751
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-18 10:02 UTC by OSIDB Bzimport
Modified: 2026-11-18 10:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.