🛡️ UBUNTU-CVE-2022-49725
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

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()

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-02-26
Updated 2026-06-15
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 5.15.0-48.54
linux-allwinner-5.19
linux-aws 5.15.0-1020.24
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1020.24~20.04.1
linux-aws-5.19
linux-aws-5.3
linux-aws-5.4 5.4.0-1085.92~18.04.1
linux-aws-5.8
linux-aws-6.2
linux-aws-6.5
linux-aws-fips
linux-aws-hwe 4.15.0-1142.154~16.04.1
linux-azure 5.15.0-1020.25
linux-azure-4.15 4.15.0-1153.168
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1020.25~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.4 5.4.0-1091.96~18.04.1
linux-azure-5.8
linux-azure-6.2
linux-azure-6.5
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.19
linux-azure-fde-6.2
linux-azure-fips
linux-bluefield
linux-fips
linux-gcp 5.15.0-1018.24
linux-gcp-4.15 4.15.0-1137.153
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1018.24~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.4 5.4.0-1089.97~18.04.1
linux-gcp-5.8
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-fips
linux-gke 5.15.0-1016.19
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 5.15.0-1003.5
linux-gkeop-5.15
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-48.54~20.04.1
linux-hwe-5.19
linux-hwe-5.4 5.4.0-126.142~18.04.1
linux-hwe-5.8
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-edge
linux-ibm 5.15.0-1015.17
linux-ibm-5.4 5.4.0-1033.37~18.04.1
linux-intel-5.13
linux-intel-iot-realtime
linux-intel-iotg 5.15.0-1016.21
linux-intel-iotg-5.15 5.15.0-1016.21~20.04.1
linux-iot 5.4.0-1004.6
linux-kvm 5.15.0-1018.22
linux-lowlatency 5.15.0-48.54
linux-lowlatency-hwe-5.15 5.15.0-48.54~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lts-xenial
linux-nvidia 5.15.0-1007.7
linux-nvidia-6.2
linux-nvidia-6.5
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.5
linux-oracle 5.15.0-1018.23
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1018.23~20.04.1
linux-oracle-5.3
linux-oracle-5.4 5.4.0-1083.91~18.04.1
linux-oracle-5.8
linux-oracle-6.5
linux-raspi 5.15.0-1015.17
linux-raspi-5.4 5.4.0-1070.80~18.04.1
linux-raspi-realtime
linux-raspi2
linux-realtime 5.15.0-1021.21
linux-riscv
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1019.22~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.5
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5

Similar Threats

Patch Gap Protection

Running software with known vulnerabilities?

BotEraser can help reduce exposure by blocking IPs associated with exploit activity — even before a patch is available.

Start Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.