Vulnerability · Published Dec 24, 2025 · Assigned by Linux

CVE-2023-54012net: fix stack overflow when LRO is disabled for virtual interfaces

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 93.4% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.37-1DEBIAN-CVE-2023-54012
Debian:13linux6.3.7-1DEBIAN-CVE-2023-54012
Debian:14linux6.3.7-1DEBIAN-CVE-2023-54012
Ubuntu:22.04:LTSlinux5.15.0-83.92UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-aws5.15.0-1044.49UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-azure5.15.0-1046.53UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1046.53.1UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-gcp5.15.0-1041.49UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-gke5.15.0-1041.46UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1027.32UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-ibm5.15.0-1037.40UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1039.45UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-kvm5.15.0-1041.46UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-83.92UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1032.32UBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1017.17UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1004.4UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-oracle5.15.0-1042.48UBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-raspi5.15.0-1037.40UBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-54012
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1025.29UBUNTU-CVE-2023-54012

Affected products (as reported)

VendorProductVersions
Linux Linux fd867d51f889aec11cca235ebb008578780d052d – before 9ea0c5f90a27b5b884d880e146e0f65f3052e401fd867d51f889aec11cca235ebb008578780d052d – before 4bb955c4d2830a58c08e2a48ab75d75368e3ff36fd867d51f889aec11cca235ebb008578780d052d – before cf3b5cd7127cc10c5b12400c545f263f0e5e715cfd867d51f889aec11cca235ebb008578780d052d – before ed66e6327a69fec95034cda2ac5b6a57b8b3b622fd867d51f889aec11cca235ebb008578780d052d – before 6bf00bb3dc7e5b9fb05488e11616e65d64e975fafd867d51f889aec11cca235ebb008578780d052d – before ae9b15fbe63447bc1d3bba3769f409d17ca6fdf6
Linux Linux 4.4

References