LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49234: net: dsa: Avoid cross-chip syncing of VLAN filtering

In the Linux kernel, the following vulnerability has been resolved: net: dsa: Avoid cross-chip syncing of VLAN filtering Changes to VLAN filtering are not applicable to cross-chip notifications. On a system like this: .-----. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-' '-1-2-' '-1-2-' Before this change, upon sw1p1 leaving a bridge, a call to dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1. In this scenario: .---------. .-----. .-----. | sw1 +---+ sw2 +---+ sw3 | '-1-2-3-4-' '-1-2-' '-1-2-' When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be called for sw2 and sw3 with a non-existing port - leading to array out-of-bounds accesses and crashes on mv88e6xxx.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Linux systems controlling certain multi-chip network switches may crash when a port leaves a software bridge. A VLAN-setting change can be sent to another switch chip where that port does not exist, causing an out-of-bounds memory access. Exposure appears limited to specialized DSA switch configurations. The supplied sources show no active exploitation.

Executive priority

Treat as high priority for network appliances or embedded systems matching the described DSA topology because crashes could interrupt connectivity. First identify applicable hardware, then obtain the vendor-supported kernel update. Systems without DSA multi-chip switching can be deprioritized after verification.

Technical view

Linux DSA incorrectly propagated VLAN-filtering changes through cross-chip notifications. In switch trees with differing port counts, the originating port index could reference a nonexistent port on another chip, causing an array out-of-bounds access and crashes on mv88e6xxx. The cited kernel changes prevent cross-chip synchronization for these notifications.

Likely exposure

Risk is concentrated in Linux systems using DSA multi-chip switch trees, particularly mv88e6xxx, with bridge and VLAN-filtering changes. Systems without this switching hardware and topology are unlikely to encounter the described flaw. The supplied version data is ambiguous, so kernel package and backport status require vendor confirmation.

Exploitation context

The CVSS vector indicates local access, low privileges, low complexity, and no user interaction. However, the sources establish only out-of-bounds access and crashes, not code execution. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation.

Researcher notes

The supplied affected-version record is difficult to interpret and includes 5.2, 0, 5.17.2, and 5.18 alongside commit identifiers. Do not rely on version strings alone; inspect vendor backports. The documented outcome is an array out-of-bounds access and crashes on mv88e6xxx. Remote exploitation and code execution are not established.

Mitigation direction

  • Apply a vendor or distribution kernel update containing the applicable cited stable fix.
  • Confirm the correct fixed package or backport with the system or appliance vendor.
  • Restrict local access and permissions capable of changing bridge or switch configuration.
  • If patching is delayed, avoid unnecessary topology changes on confirmed affected systems.

Validation and detection

  • Inventory running kernels on appliances and hosts using Linux DSA switching.
  • Identify multi-chip DSA topologies and systems using the mv88e6xxx driver.
  • Verify packages contain either cited fix or a vendor-confirmed equivalent backport.
  • Review kernel logs for out-of-bounds reports, panics, or crashes during bridge changes.
  • Use vendor-approved regression testing in a non-production environment after updating.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49234 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-49234Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd371b7c92d190448f3ccbf082c90bf929285f648, d371b7c92d190448f3ccbf082c90bf929285f648unaffected
LinuxLinux5.2, 0, 5.17.2, 5.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.