CVE-2026-97436
Last modified
CVE-2026-97436 is a vulnerability of currently unknown severity. 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.
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 539dda3c5d190c5088b5e57944b1b482fcb464de, < abea361a11e4e48695ea149652ef5d3f308b6a49; >= 539dda3c5d190c5088b5e57944b1b482fcb464de, < 5adbc4d02d7df8bd7aa02c21874f7a582a576b55; >= 539dda3c5d190c5088b5e57944b1b482fcb464de, < efc1d92eacf03afa6f4d53bf7120e059b6f961f2 |
| Linux | Linux | 5.13 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97436?
How severe is CVE-2026-97436?
How do I fix CVE-2026-97436?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97430In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97431In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97432In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97433In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-97434In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97435In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97437In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-97438In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-97439In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9744IBM Netezza Software 11.3.0.3 through Interim Fix 002 does n…5.9
- CVE-2026-97440In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97441In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-97436?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
