CVE Catalog

CVE-2026-97615

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel's network bridge module, there is an issue with CFM and MRP frame handling. When these protocols are enabled on multiple bridges, the same list node is added to multiple lists, leading to list state corruption when unregistering on one bridge. The fix tracks per-bridge enable state using option bits and dispatches the handler directly, also reducing the net_bridge structure size.

Risk Assessment

The vulnerability could lead to memory corruption or improper functioning of network bridges, potentially causing network outages or system crashes.

Recommendation

It is recommended to apply the kernel patch that fixes this issue as soon as possible and to monitor for new kernel releases.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: net: bridge: use option bits for CFM/MRP frame handlers CFM and MRP register a global br_frame_type whose hlist_node is linked into the per-bridge frame_type_list when the first MEP/MRP instance is created. Enabling the protocol on multiple bridges therefore inserts the same node into multiple lists. Unregistering it on one bridge then corrupts list state belonging to another. These handlers can only be installed once per bridge, and they are uncommon. Track their per-bridge enable state with net_bridge option bits, which already live on the Rx hot cache line, and dispatch the matching handler directly from the receive path. Check both bits together first as an unlikely case. Remove the generic frame_type_list and br_frame_type helpers, which have had no other users since CFM and MRP were added. That shrinks struct net_bridge by 8 bytes and drops the list walk from the fast path. When neither protocol is compiled in, BR_CFM_MRP_OPTS is 0 and the compiler prunes the branch.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS