CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 5e531e71b9d21d5e985251440e0d722f71299b7a, 7afb5fb42d4950f33af2732b8147c552659f79b7, 86c6613a69bca815f1865ed8cedfd4b9142621ab; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
Low priority for now. Upgrade to Linux Linux 5e531e71b9d21d5e985251440e0d722f71299b7a, 7afb5fb42d4950f33af2732b8147c552659f79b7, 86c6613a69bca815f1865ed8cedfd4b9142621ab; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: net: dsa: clean up FDB, MDB, VLAN entries on unbind As explained in many places such as commit b117e1e8a86d ("net: dsa: delete dsa_legacy_fdb_add and dsa_legacy_fdb_del"), DSA is written given the assumption that higher layers have balanced additions/deletions. As such, it only makes sense to be extremely vocal when those assumptions are violated and the driver unbinds with entries still present. But Ido Schimmel points out a very simple situation where that is wrong: https://lore.kernel.org/netdev/ZDazSM5UsPPjQuKr@shredder/ (also briefly discussed by me in the aforementioned commit). Basically, while the bridge bypass operations are not something that DSA explicitly documents, and for the majority of DSA drivers this API simply causes them to go to promiscuous mode, that isn't the case for all drivers. Some have the necessary requirements for bridge bypass operations to do something useful - see dsa_switch_supports_uc_filtering(). Although in tools/testing/selftests/net/forwarding/local_termination.sh, we made an effort to popularize better mechanisms to manage address filters on DSA interfaces from user space - namely macvlan for unicast, and setsockopt(IP_ADD_MEMBERSHIP) - through mtools - for multicast, the fact is that 'bridge fdb add ... self static local' also exists as kernel UAPI, and might be useful to someone, even if only for a quick hack. It seems counter-productive to block that path by implementing shim .ndo_fdb_add and .ndo_fdb_del operations which just return -EOPNOTSUPP in order to prevent the ndo_dflt_fdb_add() and ndo_dflt_fdb_del() from running, although we could do that. Accepting that cleanup is necessary seems to be the only option. Especially since we appear to be coming back at this from a different angle as well. Russell King is noticing that the WARN_ON() triggers even for VLANs: https://lore.kernel.org/netdev/Z_li8Bj8bD4-BYKQ@shell.armlinux.org.uk/ What happens in the bug report above is that dsa_port_do_vlan_del() fails, then the VLAN entry lingers on, and then we warn on unbind and leak it. This is not a straight revert of the blamed commit, but we now add an informational print to the kernel log (to still have a way to see that bugs exist), and some extra comments gathered from past years' experience, to justify the logic.
- BDU:2026-09430
- openSUSE-SU-2025:20081-1
- SUSE-SU-2025:02853-1
- SUSE-SU-2025:02969-1
- SUSE-SU-2025:02996-1
- SUSE-SU-2025:02997-1
- SUSE-SU-2025:03023-1
- SUSE-SU-2025:20577-1
- SUSE-SU-2025:20586-1
- SUSE-SU-2025:20601-1
- SUSE-SU-2025:20602-1
- SUSE-SU-2025:21074-1
- SUSE-SU-2025:21139-1
- SUSE-SU-2025:21179-1
- SUSE-SU-2026:20560-1
- Published
- May 9, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-617
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.18 and later · before 6.6.88
- linux linux kernel6.7 and later · before 6.12.25
- linux linux kernel6.13 and later · before 6.14.4
- linux linux kernel6.15
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.18affected
- 0832cd9f1f023226527e95002d537123061ddac4 and later · before 5e531e71b9d21d5e985251440e0d722f71299b7aaffected · git
- 0832cd9f1f023226527e95002d537123061ddac4 and later · before 86c6613a69bca815f1865ed8cedfd4b9142621abaffected · git
- 0832cd9f1f023226527e95002d537123061ddac4 and later · before 8fcc1e6f808912977caf17366c625b95dc29ba4faffected · git
- 0832cd9f1f023226527e95002d537123061ddac4 and later · before 99c50c98803425378e08a7394dc885506dc85f06affected · git
- 0832cd9f1f023226527e95002d537123061ddac4 and later · before 7afb5fb42d4950f33af2732b8147c552659f79b7affected · git
- before 5.18not affected · semver
- 6.1.175 and later · up to and including 6.1.*not affected · semver
- 6.6.88 and later · up to and including 6.6.*not affected · semver
- 6.12.25 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
| openSUSE:Leap 15.6 | dtb-aarch64 | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-64kb | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-azure | before 6.4.0-150600.8.48.1 | 6.4.0-150600.8.48.1 |
| openSUSE:Leap 15.6 | kernel-debug | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-default | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-default-base | before 6.4.0-150600.23.65.1.150600.12.28.4 | 6.4.0-150600.23.65.1.150600.12.28.4 |
| openSUSE:Leap 15.6 | kernel-docs | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-kvmsmall | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-obs-build | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-obs-qa | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| openSUSE:Leap 15.6 | kernel-rt_debug | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| openSUSE:Leap 15.6 | kernel-source | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-source-azure | before 6.4.0-150600.8.48.1 | 6.4.0-150600.8.48.1 |
| openSUSE:Leap 15.6 | kernel-source-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| openSUSE:Leap 15.6 | kernel-syms | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 15.6 | kernel-syms-azure | before 6.4.0-150600.8.48.1 | 6.4.0-150600.8.48.1 |
| openSUSE:Leap 15.6 | kernel-syms-rt | before 6.4.0-150600.10.49.1 | 6.4.0-150600.10.49.1 |
| openSUSE:Leap 15.6 | kernel-zfcpdump | before 6.4.0-150600.23.65.1 | 6.4.0-150600.23.65.1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
+56
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-37858May 9, 2025 · fs/jfs: Prevent integer overflow in AG size calculation22Monitor
- ← EarlierCVE-2025-37863May 9, 2025 · ovl: don't allow datadir only22Monitor
- Later →CVE-2025-37865May 9, 2025 · net: dsa: mv88e6xxx: fix -ENOENT when deleting VLANs and MST is unsupported22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5e531e71b9d21d5e985251440e0d722f71299b7a | Vendor (CNA) |
| Linux Linux | 7afb5fb42d4950f33af2732b8147c552659f79b7 | Vendor (CNA) |
| Linux Linux | 86c6613a69bca815f1865ed8cedfd4b9142621ab | Vendor (CNA) |
| Linux Linux | 8fcc1e6f808912977caf17366c625b95dc29ba4f | Vendor (CNA) |
| Linux Linux | 99c50c98803425378e08a7394dc885506dc85f06 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-azure | 6.4.0-150600.8.48.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-debug | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.4.0-150600.23.65.1.150600.12.28.4 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-docs | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.4.0-150600.23.65.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-azure | 6.4.0-150600.8.48.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 6.4.0-150600.8.48.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-azure | 6.4.0-150600.8.48.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150600.23.65.1.150600.12.28.4 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-docs | 6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_3 | 1-150700.1.5.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150700.7.13.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-150600.23.65.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-source-azure | 6.4.0-150600.8.48.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-150700.7.13.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
+3
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31739357 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC35Monitor
- CVE-2026-52952411 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset35Monitor
- CVE-2025-39803129 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2026-31398329 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2026-46117384 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
- CVE-2023-52621409 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.