If a DHCPv4 client sends a request with some specific options, and Kea fails to find an appropriate subnet for the client, the `kea-dhcp4` process will abort with an assertion failure. This happens only if the client request is unicast directly to Kea; broadcast messages do not cause the problem.
This issue affects Kea versions 2.7.1 through 2.7.9, 3.0.0, and 3.1.0.
References
Configurations
No configuration.
History
04 Nov 2025, 22:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
29 Aug 2025, 16:24
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
27 Aug 2025, 21:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-08-27 21:15
Updated : 2025-11-04 22:16
NVD link : CVE-2025-40779
Mitre link : CVE-2025-40779
CVE.ORG link : CVE-2025-40779
JSON object : View
Products Affected
No product.
CWE
CWE-476
NULL Pointer Dereference
