Answer in brief
CVE-2026-72389 records a Unknown severity vulnerability in bridge: stp: Fix a potential use-after-free when deleting a bridge. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72389 records a Unknown severity vulnerability in bridge: stp: Fix a potential use-after-free when deleting a bridge. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c86579b0a2d201792bcb59316629f4ba4758cfc8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <297a747f59bff6573196d7236178144d66524e68 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4c40eec06eeac37c58e47a6058eb32901218d5d4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <39283907a25e5caf0f2bd2947f6e56644b01e2b7 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b4b3458ef88df4798632619f018791d4344bcd92 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <40cbfa3a28e0919469d1b086629bb3ce38a83593 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2a00517db8de4be7df3d483b215c5544fb30a191 | c86579b0a2d201792bcb59316629f4ba4758cfc8, 297a747f59bff6573196d7236178144d66524e68, 4c40eec06eeac37c58e47a6058eb32901218d5d4, 39283907a25e5caf0f2bd2947f6e56644b01e2b7, b4b3458ef88df4798632619f018791d4344bcd92, 40cbfa3a28e0919469d1b086629bb3ce38a83593, 2a00517db8de4be7df3d483b215c5544fb30a191 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c86579b0a2d201792bcb59316629f4ba4758cfc8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <297a747f59bff6573196d7236178144d66524e68 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4c40eec06eeac37c58e47a6058eb32901218d5d4 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <39283907a25e5caf0f2bd2947f6e56644b01e2b7 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b4b3458ef88df4798632619f018791d4344bcd92 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <40cbfa3a28e0919469d1b086629bb3ce38a83593 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2a00517db8de4be7df3d483b215c5544fb30a191 | c86579b0a2d201792bcb59316629f4ba4758cfc8, 297a747f59bff6573196d7236178144d66524e68, 4c40eec06eeac37c58e47a6058eb32901218d5d4, 39283907a25e5caf0f2bd2947f6e56644b01e2b7, b4b3458ef88df4798632619f018791d4344bcd92, 40cbfa3a28e0919469d1b086629bb3ce38a83593, 2a00517db8de4be7df3d483b215c5544fb30a191 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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
Quoted source text, attributed separately from HOL analysis.