LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26690: net: stmmac: protect updates of 64-bit statistics counters

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: protect updates of 64-bit statistics counters As explained by a comment in <linux/u64_stats_sync.h>, write side of struct u64_stats_sync must ensure mutual exclusion, or one seqcount update could be lost on 32-bit platforms, thus blocking readers forever. Such lockups have been observed in real world after stmmac_xmit() on one CPU raced with stmmac_napi_poll_tx() on another CPU. To fix the issue without introducing a new lock, split the statics into three parts: 1. fields updated only under the tx queue lock, 2. fields updated only during NAPI poll, 3. fields updated only from interrupt context, Updates to fields in the first two groups are already serialized through other locks. It is sufficient to split the existing struct u64_stats_sync so that each group has its own. Note that tx_set_ic_bit is updated from both contexts. Split this counter so that each context gets its own, and calculate their sum to get the total value in stmmac_get_ethtool_stats(). For the third group, multiple interrupts may be processed by different CPUs at the same time, but interrupts on the same CPU will not nest. Move fields from this group to a newly created per-cpu struct stmmac_pcpu_stats.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-26690 is a Linux kernel driver bug in stmmac network statistics handling. On affected systems, concurrent updates can corrupt synchronization for 64-bit counters on 32-bit platforms, causing readers to hang. The source notes real-world lockups, but does not show public exploitation or KEV listing.

Executive priority

Treat this as a targeted kernel reliability risk, not an internet-wide emergency. Prioritize affected network appliances, embedded systems, and 32-bit deployments where a driver hang could disrupt business operations.

Technical view

The stmmac driver used a shared u64_stats_sync sequence counter across statistics updated from transmit, NAPI poll, and interrupt contexts. Concurrent writers could lose a seqcount update on 32-bit platforms, blocking readers indefinitely. The fix splits statistics by update context and moves interrupt-updated fields into per-CPU statistics.

Likely exposure

Exposure is most likely on Linux systems or embedded devices using affected kernels with the stmmac Ethernet MAC driver, especially 32-bit platforms. General Linux systems not using this driver are less likely to be exposed based on the provided evidence.

Exploitation context

The CVE is not listed as KEV in the provided bundle. The source describes real-world lockups caused by an internal race, but provides no evidence of active exploitation, public exploit code, or weaponized attack paths.

Researcher notes

The key condition is concurrent statistics updates across stmmac transmit, NAPI poll, and interrupt paths. The fix separates u64_stats_sync domains and per-CPU interrupt counters. The supplied data does not identify distributions, specific hardware models, or exploitability beyond the CVSS vector.

Mitigation direction

  • Check vendor or distribution advisories for a kernel containing the CVE-2024-26690 fix.
  • Prioritize updates for devices using the stmmac Ethernet driver on affected kernel branches.
  • Track the referenced stable kernel commits as fix indicators during patch validation.
  • For appliances, coordinate firmware or kernel updates with the device vendor.

Validation and detection

  • Inventory Linux hosts, appliances, and embedded systems using the stmmac driver.
  • Confirm kernel version and vendor backport status against CVE-2024-26690.
  • Review logs for stmmac, NAPI, TX, or network-statistics related lockups.
  • After updating, verify the running kernel includes the stable fix or vendor equivalent.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26690 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N2.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2024-26690Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux133466c3bbe171f826294161db203f7670bb30c8, 133466c3bbe171f826294161db203f7670bb30c8, 133466c3bbe171f826294161db203f7670bb30c8, ff12183568e0531f6db935378a92237766ad080a, 6.1.160unaffected
LinuxLinux6.6, 0, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.