net: rtnetlink: zero ifla_vf_broadcast to avoid stack infoleak in rtnl_fill_vfinfo
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 75345f888f700c4ab2448287e35d48c760b202e6 · < fbe0e6197225e6a83cf113a67a4b425f8de0bcd5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: rtnetlink: zero ifla_vf_broadcast to avoid stack infoleak in rtnl_fill_vfinfo
rtnl_fill_vfinfo() declares struct ifla_vf_broadcast on the stack without initialisation:
struct ifla_vf_broadcast vf_broadcast;
The struct contains a single fixed 32-byte field:
/* include/uapi/linux/if_link.h */ struct ifla_vf_broadcast { __u8 broadcast[32]; };
The function then copies dev->broadcast into it using dev->addr_len as the length:
memcpy(vf_broadcast.broadcast, dev->broadcast, dev->addr_len);
From the CVE record · Linux
The Linux kernel’s rtnetlink code can expose uninitialised kernel stack bytes when reporting virtual-function broadcast addresses. An unprivileged local process can repeatedly request this information through NETLINK_ROUTE on a system with affected virtual functions; no user interaction is needed.
Engineers running Linux kernels on systems with SR-IOV virtual functions should check their kernel; affected versions were not specified.