CVE-2023-54012

published 24 Dec 2025 · updated 15 Oct 2026

net: fix stack overflow when LRO is disabled for virtual interfaces

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4bb955c4d2830a58c08e2a48ab75d75368e3ff36, Kernel 6bf00bb3dc7e5b9fb05488e11616e65d64e975fa, Kernel 9ea0c5f90a27b5b884d880e146e0f65f3052e401 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: net: fix stack overflow when LRO is disabled for virtual interfaces When the virtual interface's feature is updated, it synchronizes the updated feature for its own lower interface. This propagation logic should be worked as the iteration, not recursively. But it works recursively due to the netdev notification unexpectedly. This problem occurs when it disables LRO only for the team and bonding interface type. team0 | +------+------+-----+-----+ | | | | | team1 team2 team3 ... team200 If team0's LRO feature is updated, it generates the NETDEV_FEAT_CHANGE event to its own lower interfaces(team1 ~ team200). It is worked by netdev_sync_lower_features(). So, the NETDEV_FEAT_CHANGE notification logic of each lower interface work iteratively. But generated NETDEV_FEAT_CHANGE event is also sent to the upper interface too. upper interface(team0) generates the NETDEV_FEAT_CHANGE event for its own lower interfaces again. lower and upper interfaces receive this event and generate this event again and again. So, the stack overflow occurs. But it is not the infinite loop issue. Because the netdev_sync_lower_features() updates features before generating the NETDEV_FEAT_CHANGE event. Already synchronized lower interfaces skip notification logic. So, it is just the problem that iteration logic is changed to the recursive unexpectedly due to the notification mechanism. Reproducer: ip link add team0 type team ethtool -K team0 lro on for i in {1..200} do ip link add team$i master team0 type team ethtool -K team$i lro on done ethtool -K team0 lro off In order to fix it, the notifier_ctx member of bonding/team is introduced.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.4, >=fd867d51f889aec11cca235ebb008578780d052d <4bb955c4d2830a58c08e2a48ab75d75368e3ff36, >=fd867d51f889aec11cca235ebb008578780d052d <6bf00bb3dc7e5b9fb05488e11616e65d64e975fa, >=fd867d51f889aec11cca235ebb008578780d052d <9ea0c5f90a27b5b884d880e146e0f65f3052e401, >=fd867d51f889aec11cca235ebb008578780d052d <ae9b15fbe63447bc1d3bba3769f409d17ca6fdf6, >=fd867d51f889aec11cca235ebb008578780d052d <cf3b5cd7127cc10c5b12400c545f263f0e5e715c, >=fd867d51f889aec11cca235ebb008578780d052d <ed66e6327a69fec95034cda2ac5b6a57b8b3b6224bb955c4d2830a58c08e2a48ab75d75368e3ff36, 6bf00bb3dc7e5b9fb05488e11616e65d64e975fa, 9ea0c5f90a27b5b884d880e146e0f65f3052e401, ae9b15fbe63447bc1d3bba3769f409d17ca6fdf6, cf3b5cd7127cc10c5b12400c545f263f0e5e715c, ed66e6327a69fec95034cda2ac5b6a57b8b3b622

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-54012 severity on Zeptric[![CVE-2023-54012](https://zeptric.io/badge/cve/CVE-2023-54012.svg)](https://zeptric.io/cve/CVE-2023-54012)