Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31737, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < 184b3a500d60ea48d1b176103cff1706c456edf3
    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < 78da43320d9d6ed788147fb085184e4fc801f057
    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < a7e1bf392acf11dc4209820fef75758f6e42bd65
    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < 8a71911fc7eeea930153322bc1efc065db8cd97e
    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < d45230081f19c280096241353c26b0de457de795
    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < 8351d18989c8642fc53e2e12d94e42314a39b078
    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < 82f86111f0704ab2ded11a2033bc6cf0be3e09ea
    • affected d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e – < c0fd0fe745f5e8c568d898cd1513d0083e46204a
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31737 badge
[![CVE-2026-31737](https://cveledger.app/badge/CVE-2026-31737.svg)](https://cveledger.app/cve/CVE-2026-31737)

Record last updated .