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-2022-49725i40e: Fix call trace in setup_tx_descriptors

Description

In the Linux kernel, the following vulnerability has been resolved: i40e: Fix call trace in setup_tx_descriptors After PF reset and ethtool -t there was call trace in dmesg sometimes leading to panic. When there was some time, around 5 seconds, between reset and test there were no errors. Problem was that pf reset calls i40e_vsi_close in prep_for_reset and ethtool -t calls i40e_vsi_close in diag_test. If there was not enough time between those commands the second i40e_vsi_close starts before previous i40e_vsi_close was done which leads to crash. Add check to diag_test if pf is in reset and don't start offline tests if it is true. Add netif_info("testing failed") into unhappy path of i40e_diag_test()

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 18 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-2022-49725, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.30% · top 77% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e17bc411aea8fbebc51857037f104ab09f765120 – < 5ba9956ca57e361fb13ea369bb753eb33177acc7
    • affected e17bc411aea8fbebc51857037f104ab09f765120 – < 15950157e2c24865b696db1c9ccc72743ae0e967
    • affected e17bc411aea8fbebc51857037f104ab09f765120 – < ff6e03fe84bc917bb0c907d02de668c2fe101712
    • affected e17bc411aea8fbebc51857037f104ab09f765120 – < 814092927a215f5ca6c08249ec72a205e0b473cd
    • affected e17bc411aea8fbebc51857037f104ab09f765120 – < 0a4e5a3dc5e41212870e6043895ae02455c93f63
    • affected e17bc411aea8fbebc51857037f104ab09f765120 – < 322271351b0e41565171e4cce70ea41854fac115
    • affected e17bc411aea8fbebc51857037f104ab09f765120 – < fd5855e6b1358e816710afee68a1d2bc685176ca
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 4.14.285 – ≤ 4.14.*
    • unaffected 4.19.249 – ≤ 4.19.*
    • unaffected 5.4.200 – ≤ 5.4.*
    • unaffected 5.10.124 – ≤ 5.10.*
    • unaffected 5.15.49 – ≤ 5.15.*
    • unaffected 5.18.6 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .