Description
In the Linux kernel, the following vulnerability has been resolved:

dpaa2-switch: rework FDB management on the bridge leave path

On bridge leave, the dpaa2_switch_port_set_fdb() function always
allocates a new FDB for the port which is becoming standalone. In case
no FDB is found, then the port leaving a bridge will continue to use the
current one.

The above logic does not cover the case in which there are multiple
bridges which have ports from the same DPSW instance. In this case, when
the last port leaves bridge #1, it finds an unused FDB to switch to, but
the old FDB is not marked as unused. Since the number of FDBs is equal
to the number of DPSW interfaces, this will eventually lead to multiple
ports sharing the same FDB.

Fix this by changing how we are managing the FDBs on the leave path.
Instead of directly allocating a new FDB, first verify if the current
port is the last one to leave a bridge. If this is the case, then
continue to use the current FDB and only allocate another FDB if there
are other ports remaining in the bridge.
Published: 2026-09-24
Score: n/a
EPSS: n/a
KEV: No
Impact: Network Misrouting
Action: Apply Patch
AI Analysis

Impact

In the Linux kernel, a flaw in the dpaa2 switch driver mismanages forwarding database (FDB) instances when a port leaves a bridge. When the last port departs from one bridge, the driver insists on reusing an unused FDB instead of correctly marking the previous one as unused. As a result, multiple ports that belong to different bridges but share the same Digital Physical Switch (DPSW) instance may end up referencing the same FDB. This sharing can cause traffic routed to one port to appear on another and can expose data between unrelated network segments, representing a risk to confidentiality and integrity. The weakness is an example of improper reinitialization of a critical driver resource and is classified as CWE‑665.

Affected Systems

The vulnerability affects the Linux kernel’s dpaa2 switch driver. No specific kernel versions were listed in the data, so all kernel releases that include the affected driver component are potentially impacted until the patch is applied. The issue is tied to the dpaa2 switch port handling logic within the Linux networking stack.

Risk and Exploitability

The CVSS score is not listed, and the EPSS score is not available, but the vulnerability is tracked and not yet part of the CISA KEV catalog. The attack would most likely involve a user or process with the ability to cause a port to leave its bridge, such as reconfiguration of networking or a defective hardware driver. Once the condition is met, traffic could be misrouted or leaked between bridges. Because the issue requires a state change in bridge membership, it is not trivially exploitable without privileged or sufficient network control. Nonetheless, systems that rely on dpaa2 switching should treat it as a moderate‑to‑high risk until patched.

Generated by OpenCVE AI on September 25, 2026 at 03:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Replace the affected Linux kernel with a version that includes the dpaa2 switch FDB rework fix.
  • If a kernel update is not immediately possible, temporarily disable or remove dpaa2 switching capability on bridges that share a DPSW instance to avoid accidental FDB sharing.
  • Monitor network traffic and bridge configurations to detect anomalies that might indicate inappropriate FDB sharing or misrouting.

Generated by OpenCVE AI on September 25, 2026 at 03:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 04:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Thu, 24 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: rework FDB management on the bridge leave path On bridge leave, the dpaa2_switch_port_set_fdb() function always allocates a new FDB for the port which is becoming standalone. In case no FDB is found, then the port leaving a bridge will continue to use the current one. The above logic does not cover the case in which there are multiple bridges which have ports from the same DPSW instance. In this case, when the last port leaves bridge #1, it finds an unused FDB to switch to, but the old FDB is not marked as unused. Since the number of FDBs is equal to the number of DPSW interfaces, this will eventually lead to multiple ports sharing the same FDB. Fix this by changing how we are managing the FDBs on the leave path. Instead of directly allocating a new FDB, first verify if the current port is the last one to leave a bridge. If this is the case, then continue to use the current FDB and only allocate another FDB if there are other ports remaining in the bridge.
Title dpaa2-switch: rework FDB management on the bridge leave path
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-24T16:03:49.183Z

Reserved: 2026-09-24T14:53:16.869Z

Link: CVE-2026-97436

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T17:17:21.697

Modified: 2026-09-24T17:17:21.697

Link: CVE-2026-97436

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T03:45:15Z

Weaknesses