🛡️ SUSE-SU-2026:1548-1 — kea (CVE-2026-3608)
Description
Security update for kea
This update for kea fixes the following issues:
Update to release 2.6.5.
Security issues fixed:
- CVE-2026-3608: stack overflow error via specially crafted message to the kea-ctrl-agent, kea-dhcp-ddns, kea-dhcp4, or
kea-dhcp6 daemons(bsc#1260380).
Other updates and bugfixes:
- A null dereference is now no longer possible when configuring the Control Agent with a socket that lacks the
mandatory socket-name entry.
- UNIX sockets are now created as group-writable.
- Corrected an issue in logging configuration when parsing 'syslog:'.
- Fixed crash when handling misconfigured global reservations.
- Support for recent versions of Sphinx has been added.
Affected software
SUSE-SU-2026:1548-1 is recorded against 1 package.
- kea (fixed in 2.6.5-150600.13.9.1)
Timeline and source
Published on 22 April 2026 and last revised on 23 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
www.suse.com (Advisory)
bugzilla.suse.com (Report)
www.suse.com (Web)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| kea | — | 2.6.5-150600.13.9.1 |
References
Similar Threats
- Unknown RHSA-2026:11344
- Unknown RLSA-2026:7342
- Unknown RHSA-2026:7342
- Unknown openSUSE-SU-2026:20452-1
- Unknown SUSE-SU-2026:1091-1
Free Vulnerability Check
Is your site affected by SUSE-SU-2026:1548-1?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against SUSE-SU-2026:1548-1 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.