Skip to content
Heist/ feed
Back to feed
HighFix available

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

Type: advisorySources: OSV

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

Products
Kernel
Affected versions
Not specified
Fixed versions
5.10.181, 5.15.114, 5.4.244, 6.1.31, 6.3.5
CVEs
CVE-2023-54012
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 03:30 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 24 Dec 2025, 10:55 UTC

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

osv:CVE-2023-54012

Kernel

Fixed versions: 5.4.244, 5.10.181, 5.15.114, 6.1.31, 6.3.5

Complete source record
{
  "id": "da67d3f01cbd40d87f32626aeb96c17ba813d46a50ac27771b15022b899296ca",
  "url": "https://osv.dev/vulnerability/CVE-2023-54012",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "net: fix stack overflow when LRO is disabled for virtual interfaces",
    "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 ",
    "evidence": "osv:CVE-2023-54012",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.4.244",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.10.181",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.114",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.31",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.3.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2023-54012",
      "aliases": [
        "CVE-2023-54012"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "fd867d51f889aec11cca235ebb008578780d052d"
                },
                {
                  "fixed": "9ea0c5f90a27b5b884d880e146e0f65f3052e401"
                },
                {
                  "fixed": "4bb955c4d2830a58c08e2a48ab75d75368e3ff36"
                },
                {
                  "fixed": "cf3b5cd7127cc10c5b12400c545f263f0e5e715c"
                },
                {
                  "fixed": "ed66e6327a69fec95034cda2ac5b6a57b8b3b622"
                },
                {
                  "fixed": "6bf00bb3dc7e5b9fb05488e11616e65d64e975fa"
                },
                {
                  "fixed": "ae9b15fbe63447bc1d3bba3769f409d17ca6fdf6"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-54012.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "4.4.0"
                },
                {
                  "fixed": "5.4.244"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.5.0"
                },
                {
                  "fixed": "5.10.181"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.114"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "6.1.31"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.3.5"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-54012.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:25.846016493Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/4bb955c4d2830a58c08e2a48ab75d75368e3ff36",
        "https://git.kernel.org/stable/c/6bf00bb3dc7e5b9fb05488e11616e65d64e975fa",
        "https://git.kernel.org/stable/c/9ea0c5f90a27b5b884d880e146e0f65f3052e401",
        "https://git.kernel.org/stable/c/ae9b15fbe63447bc1d3bba3769f409d17ca6fdf6",
        "https://git.kernel.org/stable/c/cf3b5cd7127cc10c5b12400c545f263f0e5e715c",
        "https://git.kernel.org/stable/c/ed66e6327a69fec95034cda2ac5b6a57b8b3b622",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/54xxx/CVE-2023-54012.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2023-54012",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/54xxx/CVE-2023-54012.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2023-54012",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 492202,
  "published_at": "2025-12-24T10:55:44.835+00:00"
}