bridge: cfm: reject invalid CCM interval at configuration time
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2be665c3940d367e0a2a8128eb4985ce323f99a3 · < 865643640b5b5c4579b32d7a55ac9ad648362eaa| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bridge: cfm: reject invalid CCM interval at configuration time
ccm_tx_work_expired() re-arms itself via queue_delayed_work() using the configured exp_interval converted by interval_to_us(). When exp_interval is BR_CFM_CCM_INTERVAL_NONE or out of range, interval_to_us() returns 0, causing the worker to fire immediately in a tight loop that allocates skbs until OOM.
Fix this by validating exp_interval at configuration time:
- Constrain IFLA_BRIDGE_CFM_CC_CONFIG_EXP_INTERVAL to the valid range [BR_CFM_CCM_INTERVAL_3_3_MS, BR_CFM_CCM_INTERVAL_10_MIN] in the netlink policy so userspace cannot set an invalid value.
- Reject starting CCM TX in br_cfm_cc_ccm_tx() when exp_interval has not yet been configured (defaults to 0 from kzalloc).
From the CVE record · Linux
The Linux kernel’s bridge CFM CCM transmitter can enter a tight loop that allocates packets until the system runs out of memory. This can happen when userspace configures an invalid CCM interval or starts CCM transmission before configuring an interval.
Engineers running Linux kernels with bridge CFM support should check their vendor advisory for affected versions.