CVE-2026-97436dpaa2-switch: rework FDB management on the bridge leave path
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 3, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 539dda3c5d190c5088b5e57944b1b482fcb464de before ec41bfd281a8bc8027a42d2674eac5b74947ff7a; from 539dda3c5d190c5088b5e57944b1b482fcb464de before e07ff2338f45adbf572850335d761c2f97545935; from 539dda3c5d190c5088b5e57944b1b482fcb464de before dc626f2abb3052881911b6166a9425739ce80085; from 539dda3c5d190c5088b5e57944b1b482fcb464de before abea361a11e4e48695ea149652ef5d3f308b6a49; 539dda3c5d190c5088b5e57944b1b482fcb464de builds before 5adbc4d02d7df8bd7aa02c21874f7a582a576b55; from 539dda3c5d190c5088b5e57944b1b482fcb464de before efc1d92eacf03afa6f4d53bf7120e059b6f961f2 | CNA record |
References
- https://git.kernel.org/stable/c/ec41bfd281a8bc8027a42d2674eac5b74947ff7a
- https://git.kernel.org/stable/c/e07ff2338f45adbf572850335d761c2f97545935
- https://git.kernel.org/stable/c/dc626f2abb3052881911b6166a9425739ce80085
- https://git.kernel.org/stable/c/abea361a11e4e48695ea149652ef5d3f308b6a49
- https://git.kernel.org/stable/c/5adbc4d02d7df8bd7aa02c21874f7a582a576b55
- https://git.kernel.org/stable/c/efc1d92eacf03afa6f4d53bf7120e059b6f961f2
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.