CVE-2026-97436
CVE CVE-2026-97436EUVD EUVD-2026-86049Published 2026-09-24T16:03:49.000ZLast changed 2026-09-25T12:44:13.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.2; patch: 6.18.53; 539dda3c5d190c5088b5e57944b1b482fcb464de <5adbc4d02d7df8bd7aa02c21874f7a582a576b55; patch: 0; 5.13; 539dda3c5d190c5088b5e57944b1b482fcb464de <efc1d92eacf03afa6f4d53bf7120e059b6f961f2; patch: 6.12.111; 539dda3c5d190c5088b5e57944b1b482fcb464de <abea361a11e4e48695ea149652ef5d3f308b6a49
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.