CVE-2026-31737: net: ftgmac100: fix ring allocation unwind on open failure

Q: Who is exposed to this issue?

Systems using the Linux kernel ftgmac100 network driver are affected. The failure occurs when the driver opens and ring allocation fails partway through.

Q: What conditions are required to trigger the resource leak?

An attacker or local process needs local access with low privileges according to the supplied CVSS vector. Exploitation requires causing an intermediate memory-allocation failure while ftgmac100_alloc_rings() is allocating its receive/transmit buffers, descriptors, or scratch area.

Q: What is the impact if the issue is triggered?

Previously allocated ring resources were leaked when a later allocation stage failed. The reported impact is availability loss, with no confidentiality or integrity impact indicated.

Q: What mitigation is available if patching cannot happen immediately?

The provided data does not identify a configuration workaround. Reducing opportunities for local low-privileged users to trigger repeated driver-open allocation failures may limit exposure, but the documented fix is to apply a kernel version containing the corrected staged cleanup path.

Published May 1, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved:

net: ftgmac100: fix ring allocation unwind on open failure

ftgmac100allocrings() allocates rxskbs, txskbs, rxdes, txdes, and rxscratch 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.

Affected Software

14 affected components

Linux Linux kernel (ftgmac100)

Linux Linux kernel>=4.12<5.10.253

Linux Linux kernel>=5.11<5.15.203

Linux Linux kernel>=5.16<6.1.168

Linux Linux kernel>=6.2<6.6.134

Linux Linux kernel>=6.7<6.12.81

Linux Linux kernel>=6.13<6.18.22

Linux Linux kernel>=6.19<6.19.12

Linux Linux kernel=7.0-rc1

Linux Linux kernel=7.0-rc2

Linux Linux kernel=7.0-rc3

Linux Linux kernel=7.0-rc4

Linux Linux kernel=7.0-rc5

Linux Linux kernel=7.0-rc6

Event History

May 1, 2026

CVE Published

via MITRE·02:14 PM

Data Sourced

via MITRE·02:14 PM

Description

Data Sourced

via NVD·03:16 PM

RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

Who is exposed to this issue?

Systems using the Linux kernel ftgmac100 network driver are affected. The failure occurs when the driver opens and ring allocation fails partway through.

What conditions are required to trigger the resource leak?

An attacker or local process needs local access with low privileges according to the supplied CVSS vector. Exploitation requires causing an intermediate memory-allocation failure while ftgmac100_alloc_rings() is allocating its receive/transmit buffers, descriptors, or scratch area.

What is the impact if the issue is triggered?

Previously allocated ring resources were leaked when a later allocation stage failed. The reported impact is availability loss, with no confidentiality or integrity impact indicated.

What mitigation is available if patching cannot happen immediately?

The provided data does not identify a configuration workaround. Reducing opportunities for local low-privileged users to trigger repeated driver-open allocation failures may limit exposure, but the documented fix is to apply a kernel version containing the corrected staged cleanup path.

CVE-2026-31737: net: ftgmac100: fix ring allocation unwind on open failure

Affected Software

Event History

Frequently Asked Questions

Who is exposed to this issue?

What conditions are required to trigger the resource leak?

What is the impact if the issue is triggered?

What mitigation is available if patching cannot happen immediately?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this issue?

What conditions are required to trigger the resource leak?

What is the impact if the issue is triggered?

What mitigation is available if patching cannot happen immediately?