cve.bz

CVE-2023-54012 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.4.244
  • Linux Linux: fixed in 5.10.181
  • Linux Linux: fixed in 5.15.114
  • Linux Linux: fixed in 6.1.31
  • Linux Linux: fixed in 6.3.5
  • Linux Linux: fixed in 6.4
  • Debian, Ubuntu, SUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2023-54012 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-54012?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-54012?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-54012 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2023-54012

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2023-54012](https://cve.bz/cve/badge/CVE-2023-54012.svg)](https://cve.bz/cve/CVE-2023-54012)

HTML:

<a href="https://cve.bz/cve/CVE-2023-54012"><img src="https://cve.bz/cve/badge/CVE-2023-54012.svg" alt="CVE-2023-54012"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.4 and later

Fixed in

ProductRelease lineFixed in
Linux5.45.4.244
Linux5.105.10.181
Linux5.155.15.114
Linux6.16.1.31
Linux6.36.3.5
Linuxlater releases6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.37-1DEBIAN-CVE-2023-54012
Debian13, 14linux6.3.7-1DEBIAN-CVE-2023-54012
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2023-54012
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux5.4.0-162.179UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-aws5.4.0-1109.118UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-aws-5.155.15.0-1044.49~20.04.1UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-azure5.4.0-1115.122UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-azure-5.155.15.0-1046.53~20.04.1UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-bluefield5.4.0-1070.76UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-gcp5.4.0-1112.121UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-gcp-5.155.15.0-1041.49~20.04.1UBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2023-54012
Ubuntu20.04:LTSlinux-hwe-5.15, linux-lowlatency-hwe-5.155.15.0-83.92~20.04.1UBUNTU-CVE-2023-54012
46 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.293.1SUSE-SU-2026:0473-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_771-8.3.1SUSE-SU-2026:0473-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5kernel-syms, kernel-source, kernel-default4.12.14-122.293.1SUSE-SU-2026:0473-1
Alpaquitastreamlinux-lts6.6.58-r0BELL-CVE-2023-54012

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This is a network robustness issue caused by unintended recursion in NETDEV_FEAT_CHANGE notifications for stacked bonding/team interfaces. Under specific virtual topology setups it can lead to kernel stack overflow and system crash, resulting in a local denial-of-service. It does not allow memory corruption, privilege escalation, or code execution.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelFix deferred
Red Hat Enterprise Linux 7kernel-rtFix deferred
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-54012.

References

Check your stackJSON