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-2025-39973i40e: add validation for ring_len param

Description

In the Linux kernel, the following vulnerability has been resolved: i40e: add validation for ring_len param The `ring_len` parameter provided by the virtual function (VF) is assigned directly to the hardware memory context (HMC) without any validation. To address this, introduce an upper boundary check for both Tx and Rx queue lengths. The maximum number of descriptors supported by the hardware is 8k-32. Additionally, enforce alignment constraints: Tx rings must be a multiple of 8, and Rx rings must be a multiple of 32.

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 12 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-2025-39973, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Deferred3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < 0543d40d6513cdf1c7882811086e59a6455dfe97
    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < 7d749e38dd2b7e8a80da2ca30c93e09de95bfcf9
    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < 45a7527cd7da4cdcf3b06b5c0cb1cae30b5a5985
    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < d3b0d3f8d11fa957171fbb186e53998361a88d4e
    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < c0c83f4cd074b75cecef107bfc349be7d516c9c4
    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < 05fe81fb9db20464fa532a3835dc8300d68a2f84
    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < afec12adab55d10708179a64d95d650741e60fe0
    • affected 5c3c48ac6bf56367c4e89f6453cd2d61e50375bd – < 55d225670def06b01af2e7a5e0446fbe946289e8
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 5.4.300 – ≤ 5.4.*
    • unaffected 5.10.245 – ≤ 5.10.*
    • unaffected 5.15.194 – ≤ 5.15.*
    • unaffected 6.1.155 – ≤ 6.1.*
    • unaffected 6.6.109 – ≤ 6.6.*
    • unaffected 6.12.50 – ≤ 6.12.*
    • unaffected 6.16.10 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .