---
id: CVE-2026-97436
title: |-
  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…
summary: |-
  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…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    abea361a11e4e48695ea149652ef5d3f308b6a49
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    5adbc4d02d7df8bd7aa02c21874f7a582a576b55
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    efc1d92eacf03afa6f4d53bf7120e059b6f961f2
  - Linux < 6.12.111
  - Linux < 6.18.53
  - Linux (all versions)
published: '2026-09-24'
updated: '2026-09-24'
sourceUpdated: '2026-09-24T17:17:21.697'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97436'
references:
  - url: 'https://git.kernel.org/stable/c/5adbc4d02d7df8bd7aa02c21874f7a582a576b55'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/abea361a11e4e48695ea149652ef5d3f308b6a49'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/efc1d92eacf03afa6f4d53bf7120e059b6f961f2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-24T16:47:15.879Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.