Answer in brief
CVE-2022-49725 records a High severity (CVSS 7.8) vulnerability in i40e: Fix call trace in setup_tx_descriptors. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-49725 records a High severity (CVSS 7.8) vulnerability in i40e: Fix call trace in setup_tx_descriptors. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e17bc411aea8fbebc51857037f104ab09f765120 <5ba9956ca57e361fb13ea369bb753eb33177acc7 || >=e17bc411aea8fbebc51857037f104ab09f765120 <15950157e2c24865b696db1c9ccc72743ae0e967 || >=e17bc411aea8fbebc51857037f104ab09f765120 <ff6e03fe84bc917bb0c907d02de668c2fe101712 || >=e17bc411aea8fbebc51857037f104ab09f765120 <814092927a215f5ca6c08249ec72a205e0b473cd || >=e17bc411aea8fbebc51857037f104ab09f765120 <0a4e5a3dc5e41212870e6043895ae02455c93f63 || >=e17bc411aea8fbebc51857037f104ab09f765120 <322271351b0e41565171e4cce70ea41854fac115 || >=e17bc411aea8fbebc51857037f104ab09f765120 <fd5855e6b1358e816710afee68a1d2bc685176ca | 5ba9956ca57e361fb13ea369bb753eb33177acc7, 15950157e2c24865b696db1c9ccc72743ae0e967, ff6e03fe84bc917bb0c907d02de668c2fe101712, 814092927a215f5ca6c08249ec72a205e0b473cd, 0a4e5a3dc5e41212870e6043895ae02455c93f63, 322271351b0e41565171e4cce70ea41854fac115, fd5855e6b1358e816710afee68a1d2bc685176ca |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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()
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e17bc411aea8fbebc51857037f104ab09f765120 <5ba9956ca57e361fb13ea369bb753eb33177acc7 || >=e17bc411aea8fbebc51857037f104ab09f765120 <15950157e2c24865b696db1c9ccc72743ae0e967 || >=e17bc411aea8fbebc51857037f104ab09f765120 <ff6e03fe84bc917bb0c907d02de668c2fe101712 || >=e17bc411aea8fbebc51857037f104ab09f765120 <814092927a215f5ca6c08249ec72a205e0b473cd || >=e17bc411aea8fbebc51857037f104ab09f765120 <0a4e5a3dc5e41212870e6043895ae02455c93f63 || >=e17bc411aea8fbebc51857037f104ab09f765120 <322271351b0e41565171e4cce70ea41854fac115 || >=e17bc411aea8fbebc51857037f104ab09f765120 <fd5855e6b1358e816710afee68a1d2bc685176ca | 5ba9956ca57e361fb13ea369bb753eb33177acc7, 15950157e2c24865b696db1c9ccc72743ae0e967, ff6e03fe84bc917bb0c907d02de668c2fe101712, 814092927a215f5ca6c08249ec72a205e0b473cd, 0a4e5a3dc5e41212870e6043895ae02455c93f63, 322271351b0e41565171e4cce70ea41854fac115, fd5855e6b1358e816710afee68a1d2bc685176ca |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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()
Quoted source text, attributed separately from HOL analysis.