The vulnerability occurs when the SecY component of a MACsec device is not fully initialized before the netdevice is registered. When IPv4 forwarding is enabled, the registration flow triggers a notification that reaches macsec_fill_info() before macsec_add_dev() has initialized the SecY, so the key length remains zero and the fill function returns –EMSGSIZE, causing a WARN_ON in rtmsg_ifinfo_build_skb() even though the buffer is sufficient. Based on the description, it is inferred that the primary impact is the appearance of warning messages and the potential exposure of uninitialized SecY attributes, such as the SCI, during early registration notifications. This does not directly enable code execution but may lead to inconsistent device state and erroneous diagnostic output.

All installations of the Linux kernel that enable the macsec driver are affected. The bug originates from the macsec driver and the netdevice registration path, so any kernel version where the driver is loaded and MACsec devices are configured is potentially impacted until a patched release replaces the registration order. No explicit version bounds are listed, so the risk applies to all recent kernels where macsec is actively used.

Exploitability requires local kernel privilege—an attacker must be able to register a MACsec device or load the macsec module. The bug does not provide a path for privilege escalation, remote code execution, or direct data disclosure beyond the uninitialized attributes exposed in kernel logs. The EPSS score of 0.00167 indicates a very low exploitation probability, and the issue is not listed in the CISA KEV catalog. The primary risk is diagnostic noise and potential misconfiguration rather than a direct security breach.