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

In the Linux kernel, the following vulnerability has been resolved: net: dsa: qca8k: reset cpu port on MTU change It was discovered that the Documentation lacks of a fundamental detail on how to correctly change the MAX_FRAME_SIZE of the switch. In fact if the MAX_FRAME_SIZE is changed while the cpu port is on, the switch panics and cease to send any packet. This cause the mgmt ethernet system to not receive any packet (the slow fallback still works) and makes the device not reachable. To recover from this a switch reset is required. To correctly handle this, turn off the cpu ports before changing the MAX_FRAME_SIZE and turn on again after the value is applied.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-22	0.04%	0.05%	+0.01%
2	2025-10-24	0.05%	0.04%	-0.01%
3	2025-08-06	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-22

0.04%

0.05%

+0.01%

2025-10-24

0.05%

0.04%

-0.01%

2025-08-06

—

0.05%

—

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-49654

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49654 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1.	https://security-tracker.debian.org/tracker/CVE-2022-49654
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2022-49654
`suse`	medium	CVE-2022-49654 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 198 product×package rows across 36 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 12 SP5, … (36 product lines)): Known Not Affected 198.	https://www.suse.com/security/cve/CVE-2022-49654/
`ubuntu`	medium	CVE-2022-49654 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, ignored 146, not-affected 145, released 114, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49654

Affected software / configurations for CVE-2022-49654

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.9, < 5.15.54	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.11	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::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc3::::::

References for CVE-2022-49654

URL	Tags
https://git.kernel.org/stable/c/188c798f3c2554fa0d7147e9b97baf144b817019	Patch
https://git.kernel.org/stable/c/1993f5a06736ada59dd54b50dc96755a38796ee5	Patch
https://git.kernel.org/stable/c/386228c694bf1e7a7688e44412cb33500b0ac585	Patch

URL

CVE-2022-49654 | net: dsa: qca8k: reset cpu port on MTU change

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

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

Weakness enumeration for CVE-2022-49654

OS Trackers for CVE-2022-49654

Affected software / configurations for CVE-2022-49654

References for CVE-2022-49654