CVE-2022-49725 [Medium] | Security Vulnerability in Linux Kernel

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

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.06%	0.03%	-0.03%
2	2025-11-18	0.03%	0.06%	+0.03%
3	2025-10-25	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.06%

0.03%

-0.03%

2025-11-18

0.03%

0.06%

+0.03%

2025-10-25

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-49725

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49725 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-49725
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49725
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-49725/
`ubuntu`	medium	CVE-2022-49725 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 151, ignored 148, not-affected 102, needed 4, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49725

Affected software / configurations for CVE-2022-49725

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.2, < 4.14.285	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.15, < 4.19.249	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.200	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.124	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.49	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.6	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc1::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc2::::::

References for CVE-2022-49725

URL	Tags
https://git.kernel.org/stable/c/0a4e5a3dc5e41212870e6043895ae02455c93f63	Patch
https://git.kernel.org/stable/c/15950157e2c24865b696db1c9ccc72743ae0e967	Patch
https://git.kernel.org/stable/c/322271351b0e41565171e4cce70ea41854fac115	Patch
https://git.kernel.org/stable/c/5ba9956ca57e361fb13ea369bb753eb33177acc7	Patch
https://git.kernel.org/stable/c/814092927a215f5ca6c08249ec72a205e0b473cd	Patch
https://git.kernel.org/stable/c/fd5855e6b1358e816710afee68a1d2bc685176ca	Patch
https://git.kernel.org/stable/c/ff6e03fe84bc917bb0c907d02de668c2fe101712	Patch

URL

CVE-2022-49725 | i40e: Fix call trace in setup_tx_descriptors

Exploit prediction scoring system (EPSS) score for CVE-2022-49725

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49725

Weakness enumeration for CVE-2022-49725

OS Trackers for CVE-2022-49725

Affected software / configurations for CVE-2022-49725

References for CVE-2022-49725