CVE-2025-37864
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2025-37864
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-37864.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2025-37864
- Downstream
- Related
- Published
- 2025-05-09T06:43:54Z
- Modified
- 2025-10-10T10:28:53.186236Z
- Summary
- net: dsa: clean up FDB, MDB, VLAN entries on unbind
- Details
-
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 dsalegacyfdbadd and dsalegacyfdbdel"), 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 dsaswitchsupportsucfiltering().
Although in tools/testing/selftests/net/forwarding/localtermination.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(IPADD_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 .ndofdbadd and .ndofdbdel operations which just return -EOPNOTSUPP in order to prevent the ndodfltfdbadd() and ndodfltfdbdel() 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 WARNON() triggers even for VLANs: https://lore.kernel.org/netdev/Zli8Bj8bD4-BYKQ@shell.armlinux.org.uk/
What happens in the bug report above is that dsaportdovlandel() 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.
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/7afb5fb42d4950f33af2732b8147c552659f79b7
- https://git.kernel.org/stable/c/86c6613a69bca815f1865ed8cedfd4b9142621ab
- https://git.kernel.org/stable/c/8fcc1e6f808912977caf17366c625b95dc29ba4f
- https://git.kernel.org/stable/c/99c50c98803425378e08a7394dc885506dc85f06
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced0832cd9f1f023226527e95002d537123061ddac4Fixed86c6613a69bca815f1865ed8cedfd4b9142621ab
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced0832cd9f1f023226527e95002d537123061ddac4Fixed8fcc1e6f808912977caf17366c625b95dc29ba4f
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced0832cd9f1f023226527e95002d537123061ddac4Fixed99c50c98803425378e08a7394dc885506dc85f06
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced0832cd9f1f023226527e95002d537123061ddac4Fixed7afb5fb42d4950f33af2732b8147c552659f79b7