CVE-2026-31737: net: ftgmac100: fix ring allocation unwind on open failure
In the Linux kernel, the following vulnerability has been resolved:
net: ftgmac100: fix ring allocation unwind on open failure
ftgmac100_alloc_rings() allocates rx_skbs, tx_skbs, rxdes, txdes, and
rx_scratch in stages. On intermediate failures it returned -ENOMEM
directly, leaking resources allocated earlier in the function.
Rework the failure path to use staged local unwind labels and free
allocated resources in reverse order before returning -ENOMEM. This
matches common netdev allocation cleanup style.
Security readout for executives and security teams
Plain-English summary
CVE-2026-31737 is a Linux kernel cleanup bug in the ftgmac100 network driver. If opening the network device fails partway through memory allocation, earlier allocations may be leaked. The public record does not provide CVSS, confirmed attacks, or broad product impact. Priority is mainly for systems using this driver or vendor appliances shipping affected kernels.
Executive priority
Treat as routine patch management unless you operate embedded, industrial, or appliance systems using this Linux network driver. No active exploitation is cited, and severity is not scored. Still, kernel resource leaks can affect reliability, so track vendor fixes and prioritize exposed operational technology or always-on network appliances.
Technical view
The flaw is in ftgmac100_alloc_rings(). Allocation occurs in stages for RX/TX buffers and descriptors; intermediate -ENOMEM returns skipped cleanup of earlier allocations. Kernel stable commits rework the failure path to unwind resources in reverse order. Impact appears to be kernel memory/resource leakage on device open failure, with exposure tied to affected Linux kernels and ftgmac100 driver use.
Likely exposure
Most exposed assets are Linux-based systems that include and use the ftgmac100 Ethernet driver. The CVE record lists Linux kernel versions as affected and provides stable kernel fix commits. Distribution and appliance exposure depends on vendor backports. Siemens advisories are referenced, but this source bundle does not enumerate specific Siemens affected products.
Exploitation context
There is no KEV listing and no cited source here reporting active exploitation. Exploitation context is limited by available evidence: the condition occurs during failed ring allocation while opening the driver. Practical impact likely requires the vulnerable driver path and allocation failure conditions, suggesting denial-of-service/resource exhaustion risk rather than direct remote compromise based on provided sources.
Researcher notes
Evidence is limited to the CVE description and kernel stable references. No CWE, CVSS, exploit status, or detailed threat model is provided. Analysis should focus on driver reachability, whether allocation-failure paths are triggerable in deployed environments, and whether downstream vendors have backported the staged unwind fix.
Mitigation direction
Update to a kernel containing the referenced stable ftgmac100 fix commits.
Use distribution or appliance vendor kernel updates when available.
Review Siemens advisories if operating Siemens products covered by the referenced notices.
Prioritize systems that actually use the ftgmac100 network driver.
If no vendor patch is available, monitor vendor guidance for supported mitigations.
Validation and detection
Inventory Linux kernels and appliances that include the ftgmac100 driver.
Confirm running kernels include one of the referenced stable fix commits.
Check distribution changelogs for CVE-2026-31737 backports.
Verify vendor advisories for affected product and firmware status.
Document systems where ftgmac100 is unused to reduce remediation priority.
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-2026-31737 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
1ADP providers
11Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 1, 2026, 14:14 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.