# CVE-2023-54012: linux: In the Linux kernel, the following vulnerability has been resolved: net: fix stack overflow when LRO is disabled for... CVE-2023-54012 is fixed in 20 products on 1 platform, first by ALAS2023-2023-228, released June 21, 2023. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2023-54012 - Priority: High - CVSS: 7.8 (high) - EPSS: 0.0017 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Jun 21, 2023 ## Description 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. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | bpftool-debuginfo amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-debuginfo amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-debuginfo-common-aarch64 amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-debuginfo-common-x86_64 amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-devel amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-headers amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-libbpf amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-libbpf-devel amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-libbpf-static amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-livepatch-6.1.34-56.100 amzn 2023 | 1.0-0.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-tools amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-tools-debuginfo amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | kernel-tools-devel amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | linux Debian 12.15 (bookworm) | 6.1.37-1 | [DEBIAN-CVE-2023-54012](https://patchblox.com/security/data/fix/linux/debian-cve-2023-54012.md) | Dec 24, 2025 | | Linux | linux Debian 13.5 (trixie) | 6.3.7-1 | [DEBIAN-CVE-2023-54012](https://patchblox.com/security/data/fix/linux/debian-cve-2023-54012.md) | Dec 24, 2025 | | Linux | linux Debian 14 | 6.3.7-1 | [DEBIAN-CVE-2023-54012](https://patchblox.com/security/data/fix/linux/debian-cve-2023-54012.md) | Dec 24, 2025 | | Linux | perf amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | perf-debuginfo amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | python3-perf amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | | Linux | python3-perf-debuginfo amzn 2023 | 6.1.34-56.100.amzn2023 | [ALAS2023-2023-228](https://patchblox.com/security/data/fix/linux/alas2023-2023-228.md) | Jun 21, 2023 | --- Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.