bridge: stp: Fix a potential use-after-free when deleting a bridge (Linux Linux)
At a glance
- Source
- NVD
- EPSS
- EPSS 0.16 % · percentile 6 ()
- State
- PUBLISHED
- Published
- Updated
- Assigner
- Linux
- NVD status
- Received
Description
In the Linux kernel, the following vulnerability has been resolved: bridge: stp: Fix a potential use-after-free when deleting a bridge The three STP timers are not supposed to be armed while the bridge is administratively down. They are synchronously deactivated when the bridge is put administratively down and the various call sites check for 'IFF_UP' before arming them. This check is missing from br_topology_change_detection() and it is possible to engineer a situation in which the topology change timer is armed while the bridge is administratively down, resulting in a use-after-free [1] when the bridge is deleted. Fix by adding the missing check and for good measures synchronously shutdown the three timers when the bridge is deleted. [1] ODEBUG: free active (active state 0) object: ffff88811662b9b0 object type: timer_list hint: br_topology_change_timer_expired (net/bridge/br_stp_timer.c:120) WARNING: lib/debugobjects.c:629 at debug_print_object+0x1bc/0x450, CPU#9: ip/359
References
- https://git.kernel.org/stable/c/c86579b0a2d201792bcb59316629f4ba4758cfc8
- https://git.kernel.org/stable/c/297a747f59bff6573196d7236178144d66524e68
- https://git.kernel.org/stable/c/4c40eec06eeac37c58e47a6058eb32901218d5d4
- https://git.kernel.org/stable/c/39283907a25e5caf0f2bd2947f6e56644b01e2b7
- https://git.kernel.org/stable/c/b4b3458ef88df4798632619f018791d4344bcd92
- https://git.kernel.org/stable/c/40cbfa3a28e0919469d1b086629bb3ce38a83593
- https://git.kernel.org/stable/c/2a00517db8de4be7df3d483b215c5544fb30a191
Scores
| Version | Score | Vector | Scored by |
|---|---|---|---|
| CVSS 3.1 | HIGH 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | Linux |
| CVSS 3.1 | HIGH 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD · 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Secondary) |
European references
- ENISA EUVD · EUVD-2026-59288
- GCVE · GCVE-0-2026-72389
CERT-FR advisories
- CERTFR-2026-AVI-1385 — Multiples vulnérabilités dans les produits VMware · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1333 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1288 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1286 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1255 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1231 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1202 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1164 — Multiples vulnérabilités dans le noyau Linux de SUSE · cert.ssi.gouv.fr
Affected products
| Product | Versions |
|---|---|
| Linux · Linux | affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c86579b0a2d201792bcb59316629f4ba4758cfc8 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 297a747f59bff6573196d7236178144d66524e68 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4c40eec06eeac37c58e47a6058eb32901218d5d4 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 39283907a25e5caf0f2bd2947f6e56644b01e2b7 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b4b3458ef88df4798632619f018791d4344bcd92 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 40cbfa3a28e0919469d1b086629bb3ce38a83593 |
| Linux · Linux | affected 2.6.12 ; unaffected 0 < 2.6.12 ; unaffected 5.15.212 ≤ 5.15.* ; unaffected 6.1.178 ≤ 6.1.* ; unaffected 6.6.145 ≤ 6.6.* ; unaffected 6.12.97 ≤ 6.12.* |
Sources
| Source | Licence |
|---|---|
| CVE List (CVEProject cvelistV5) | CVE Program Terms of Use |
| EPSS (FIRST.org) | FIRST — attribution requested |
| ENISA EUVD | ENISA — reproduction authorised, source acknowledged |
| CERT-FR (ANSSI) | Licence Ouverte / Etalab 2.0 |
| NVD (NIST) via fkie-cad/nvd-json-data-feeds | Public domain — this product uses data from the NVD API but is not endorsed or certified by the NVD |