Description
In the Linux kernel, the following vulnerability has been resolved: bridge: mrp: reject zero test interval to avoid OOM panic br_mrp_start_test() and br_mrp_start_in_test() accept the user-supplied interval value from netlink without validation. When interval is 0, usecs_to_jiffies(0) yields 0, causing the delayed work (br_mrp_test_work_expired / br_mrp_in_test_work_expired) to reschedule itself with zero delay. This creates a tight loop on system_percpu_wq that allocates and transmits MRP test frames at maximum rate, exhausting all system memory and causing a kernel panic via OOM deadlock. The same zero-interval issue applies to br_mrp_start_in_test_parse() for interconnect test frames. Use NLA_POLICY_MIN(NLA_U32, 1) in the nla_policy tables for both IFLA_BRIDGE_MRP_START_TEST_INTERVAL and IFLA_BRIDGE_MRP_START_IN_TEST_INTERVAL, so zero is rejected at the netlink attribute parsing layer before the value ever reaches the workqueue scheduling code. This is consistent with how other bridge subsystems (br_fdb, br_mst) enforce range constraints on netlink attributes.
Product status
20f6a05ef63594feb0c6dfbd629da0448b43124d (git) before 630a15a31c2034b5b697f4aabc769b9d80d82446
20f6a05ef63594feb0c6dfbd629da0448b43124d (git) before e8ec80430bfa520e7352155d6ac632e527cba7aa
20f6a05ef63594feb0c6dfbd629da0448b43124d (git) before c9bc352f716d1bebfe43354bce539ec2d0223b30
20f6a05ef63594feb0c6dfbd629da0448b43124d (git) before fa6e24963342de4370e3a3c9af41e38277b74cf3
5.8
Any version before 5.8
6.12.92 (semver)
6.18.34 (semver)
6.19.12 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/630a15a31c2034b5b697f4aabc769b9d80d82446
git.kernel.org/...c/e8ec80430bfa520e7352155d6ac632e527cba7aa
git.kernel.org/...c/c9bc352f716d1bebfe43354bce539ec2d0223b30
git.kernel.org/...c/fa6e24963342de4370e3a3c9af41e38277b74cf3