Answer in brief
CVE-2024-44934 records a High severity (CVSS 7.8) vulnerability in net: bridge: mcast: wait for previous gc cycles when removing port. 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.
CVSS is 7.8. 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 | >=e12cec65b5546f19217e26aafb8add6e2fadca18 <1e16828020c674b3be85f52685e8b80f9008f50f || >=e12cec65b5546f19217e26aafb8add6e2fadca18 <0d8b26e10e680c01522d7cc14abe04c3265a928f || >=e12cec65b5546f19217e26aafb8add6e2fadca18 <e3145ca904fa8dbfd1a5bf0187905bc117b0efce || >=e12cec65b5546f19217e26aafb8add6e2fadca18 <b2f794b168cf560682ff976b255aa6d29d14a658 || >=e12cec65b5546f19217e26aafb8add6e2fadca18 <92c4ee25208d0f35dafc3213cdf355fbe449e078 | 1e16828020c674b3be85f52685e8b80f9008f50f, 0d8b26e10e680c01522d7cc14abe04c3265a928f, e3145ca904fa8dbfd1a5bf0187905bc117b0efce, b2f794b168cf560682ff976b255aa6d29d14a658, 92c4ee25208d0f35dafc3213cdf355fbe449e078 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Aug 26, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: bridge: mcast: wait for previous gc cycles when removing port syzbot hit a use-after-free[1] which is caused because the bridge doesn't make sure that all previous garbage has been collected when removing a port. What happens is: CPU 1 CPU 2 start gc cycle remove port acquire gc lock first wait for lock call br_multicasg_gc() directly acquire lock now but free port the port can be freed while grp timers still running Make sure all previous gc cycles have finished by using flush_work before freeing the port. [1] BUG: KASAN: slab-use-after-free in br_multicast_port_group_expired+0x4c0/0x550 net/bridge/br_multicast.c:861 Read of size 8 at addr ffff888071d6d000 by task syz.5.1232/9699 CPU: 1 PID: 9699 Comm: syz.5.1232 Not tainted 6.10.0-rc5-syzkaller-00021-g24ca36a562d6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 br_multicast_port_group_expired+0x4c0/0x550 net/bridge/br_multicast.c:861 call_timer_fn+0x1a3/0x610 kernel/time/timer.c:1792 expire_timers kernel/time/timer.c:1843 [inline] __run_timers+0x74b/0xaf0 kernel/time/timer.c:2417 __run_timer_base kernel/time/timer.c:2428 [inline] __run_timer_base kernel/time/timer.c:2421 [inline] run_timer_base+0x111/0x190 kernel/time/timer.c:2437
Quoted source text, attributed separately from HOL analysis.