Answer in brief
CVE-2026-97436 records a Unknown severity vulnerability in dpaa2-switch: rework FDB management on the bridge leave path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <abea361a11e4e48695ea149652ef5d3f308b6a49 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5adbc4d02d7df8bd7aa02c21874f7a582a576b55 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <efc1d92eacf03afa6f4d53bf7120e059b6f961f2 || >=0 <6.12.111 || >=0 <6.18.53 | abea361a11e4e48695ea149652ef5d3f308b6a49, 5adbc4d02d7df8bd7aa02c21874f7a582a576b55, efc1d92eacf03afa6f4d53bf7120e059b6f961f2, 6.12.111, 6.18.53 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.