net: fix stack overflow when LRO is disabled for virtual interfaces
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.244, 5.10.181, 5.15.114, 6.1.31, 6.3.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From fd867d51f889aec11cca235ebb008578780d052d · fixed in 9ea0c5f90a27b5b884d880e146e0f65f3052e401; From fd867d51f889aec11cca235ebb008578780d052d · fixed in 4bb955c4d2830a58c08e2a48ab75d75368e3ff36; From fd867d51f889aec11cca235ebb008578780d052d · fixed in cf3b5cd7127cc10c5b12400c545f263f0e5e715c; From fd867d51f889aec11cca235ebb008578780d052d · fixed in ed66e6327a69fec95034cda2ac5b6a57b8b3b622; From fd867d51f889aec11cca235ebb008578780d052d · fixed in 6bf00bb3dc7e5b9fb05488e11616e65d64e975fa; From fd867d51f889aec11cca235ebb008578780d052d · fixed in ae9b15fbe63447bc1d3bba3769f409d17ca6fdf6
- Linux Linux
4.4
- KernelLinux
From 4.4.0 · fixed in 5.4.244; From 5.5.0 · fixed in 5.10.181; From 5.11.0 · fixed in 5.15.114; From 5.16.0 · fixed in 6.1.31; From 6.2.0 · fixed in 6.3.5