Bug 2347970 (CVE-2022-49654) - CVE-2022-49654 kernel: net: dsa: qca8k: reset cpu port on MTU change
Summary: CVE-2022-49654 kernel: net: dsa: qca8k: reset cpu port on MTU change
Keywords:
Status: NEW
Alias: CVE-2022-49654
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:13 UTC by OSIDB Bzimport
Modified: 2025-11-25 09:55 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:13:07 UTC
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.

Comment 1 Avinash Hanwate 2025-02-26 11:42:48 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022621-CVE-2022-49654-4ed4@gregkh/T

Comment 2 Avinash Hanwate 2025-02-26 16:11:51 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022621-CVE-2022-49654-4ed4@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.