net: ipconfig: bound DHCP option construction
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 130c0f47fdf9c533deb1136cad5136f6cb7020f0 · < 24e79508b237dd2a69bc6fb6ac5cf7f126178307| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: ipconfig: bound DHCP option construction
ic_dhcp_init_options() appends the hostname (option 12), vendor-class (option 60) and client-ID (option 61) options into the fixed 312-byte bootp_pkt.exten[] buffer. Only the client-ID branch checked the remaining space; the hostname and vendor-class writes were unbounded.
A 64-byte hostname together with the maximum 252-byte dhcpclass= identifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available bytes even before the terminating END marker, so the vendor-class memcpy runs past the end of exten[]. With CONFIG_FORTIFY_SOURCE this is reported as a field-spanning write and, when the kernel is booted with panic_on_warn=1, aborts boot with a panic.
Route the optional options through a common helper that makes sure the option, its 2-byte header and the END marker all fit and drops an option that would not. Configurations with short options keep sending exactly the same bytes as before.
From the CVE record · Linux
The Linux kernel's DHCP option construction can write past a fixed-size buffer when a 64-byte hostname is combined with a maximum-length dhcpclass identifier. With CONFIG_FORTIFY_SOURCE and panic_on_warn=1, this can abort boot with a kernel panic. The input does not describe a remote attack or authentication requirement.
Operators running Linux kernels that use DHCP during boot should check whether their kernel includes the fix; affected versions were not provided.