CVE-2026-97436 — dpaa2-switch: rework FDB management on the bridge leave path
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 539dda3c5d190c5088b5e57944b1b482fcb464de and < ec41bfd281a8bc8027a42d2674eac5b74947ff7a≥ 539dda3c5d190c5088b5e57944b1b482fcb464de and < e07ff2338f45adbf572850335d761c2f97545935≥ 539dda3c5d190c5088b5e57944b1b482fcb464de and < dc626f2abb3052881911b6166a9425739ce80085≥ 539dda3c5d190c5088b5e57944b1b482fcb464de and < abea361a11e4e48695ea149652ef5d3f308b6a49≥ 539dda3c5d190c5088b5e57944b1b482fcb464de and < 5adbc4d02d7df8bd7aa02c21874f7a582a576b55≥ 539dda3c5d190c5088b5e57944b1b482fcb464de and < efc1d92eacf03afa6f4d53bf7120e059b6f961f2version 5.13 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
6 on the record
- git.kernel.org/stable/c/abea361a11e4e48695ea149652ef5d3f308b6a49
- git.kernel.org/stable/c/5adbc4d02d7df8bd7aa02c21874f7a582a576b55
- git.kernel.org/stable/c/efc1d92eacf03afa6f4d53bf7120e059b6f961f2
- git.kernel.org/stable/c/e07ff2338f45adbf572850335d761c2f97545935
- git.kernel.org/stable/c/dc626f2abb3052881911b6166a9425739ce80085
- git.kernel.org/stable/c/ec41bfd281a8bc8027a42d2674eac5b74947ff7a
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 3d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 3d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-97436 is "dpaa2-switch: rework FDB management on the bridge leave path", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.