CVE-2026-97436

dpaa2-switch: rework FDB management on the bridge leave path

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.

Key facts

Published
24 Sep 2026
Last changed
3 Oct 2026
Assigned by
Linux
EPSS
0.173% likely to be exploited in the next 30 days, higher than 6.746% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 539dda3c5d190c5088b5e57944b1b482fcb464de up to but excluding ec41bfd281a8bc8027a42d2674eac5b74947ff7a (affected)
  • 539dda3c5d190c5088b5e57944b1b482fcb464de up to but excluding e07ff2338f45adbf572850335d761c2f97545935 (affected)
  • 539dda3c5d190c5088b5e57944b1b482fcb464de up to but excluding dc626f2abb3052881911b6166a9425739ce80085 (affected)
  • 539dda3c5d190c5088b5e57944b1b482fcb464de up to but excluding abea361a11e4e48695ea149652ef5d3f308b6a49 (affected)
  • 539dda3c5d190c5088b5e57944b1b482fcb464de up to but excluding 5adbc4d02d7df8bd7aa02c21874f7a582a576b55 (affected)
  • 539dda3c5d190c5088b5e57944b1b482fcb464de up to but excluding efc1d92eacf03afa6f4d53bf7120e059b6f961f2 (affected)
LinuxLinux
  • Default status: affected
  • 5.13 (affected)
  • 0 up to but excluding 5.13 (unaffected)
  • 5.15.222 up to and including 5.15.* (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References