CVE-2026-97436

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

N/A
Published: September 24, 2026 at 04:03 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.13 ≤ v < 5.15.2225.13 ≤ v < 6.1.1895.13 ≤ v < 6.12.1115.13 ≤ v < 6.18.535.13 ≤ v < 6.6.1585.13 ≤ v < 7.25.13539dda3c5d190c5088b5e57944b1b482fcb464de
Vendor states this is fixed in 5adbc4d02d7df8bd7aa02c21874f7a582a576b55 (fixed)
Vendor states this is fixed in abea361a11e4e48695ea149652ef5d3f308b6a49 (fixed)
Vendor states this is fixed in dc626f2abb3052881911b6166a9425739ce80085 (fixed)
Vendor states this is fixed in e07ff2338f45adbf572850335d761c2f97545935 (fixed)
Vendor states this is fixed in ec41bfd281a8bc8027a42d2674eac5b74947ff7a (fixed)
Vendor states this is fixed in efc1d92eacf03afa6f4d53bf7120e059b6f961f2 (fixed)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card