CVE-2026-97436dpaa2-switch: rework FDB management on the bridge leave path
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 9 days later
· 9 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < ec41bfd281a8bc8027a42d2674eac5b74947ff7a
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < e07ff2338f45adbf572850335d761c2f97545935
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < dc626f2abb3052881911b6166a9425739ce80085
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < abea361a11e4e48695ea149652ef5d3f308b6a49
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < 5adbc4d02d7df8bd7aa02c21874f7a582a576b55
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < efc1d92eacf03afa6f4d53bf7120e059b6f961f2
- affected 5.13
- unaffected < 5.13
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ec41bfd281a8bc8027a42d2674eac5b74947ff7a (opens in a new tab)
- https://git.kernel.org/stable/c/e07ff2338f45adbf572850335d761c2f97545935 (opens in a new tab)
- https://git.kernel.org/stable/c/dc626f2abb3052881911b6166a9425739ce80085 (opens in a new tab)
- https://git.kernel.org/stable/c/abea361a11e4e48695ea149652ef5d3f308b6a49 (opens in a new tab)
- https://git.kernel.org/stable/c/5adbc4d02d7df8bd7aa02c21874f7a582a576b55 (opens in a new tab)
- https://git.kernel.org/stable/c/efc1d92eacf03afa6f4d53bf7120e059b6f961f2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86049 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97436)Record last updated .