CVE-2026-64537

bridge: cfm: reject invalid CCM interval at configuration time

N/A
Published: July 27, 2026 at 08:10 PM UTC
Updated: August 17, 2026 at 05:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.2125.11 ≤ v < 6.1.1785.11 ≤ v < 6.12.975.11 ≤ v < 6.18.405.11 ≤ v < 6.6.1455.11 ≤ v < 7.1.55.11 ≤ v < 7.22be665c3940d367e0a2a8128eb4985ce323f99a35.11
Vendor states this is fixed in 2870056a78961e0fecd652362ee9d3fcfd24a8a6 (fixed)
Vendor states this is fixed in 53788b134519e995699ea3721969c96a08d64575 (fixed)
Vendor states this is fixed in 865643640b5b5c4579b32d7a55ac9ad648362eaa (fixed)
Vendor states this is fixed in a090880c1f544589427e5b7050c40fb211ccecb4 (fixed)
Vendor states this is fixed in b42aeb58317f12024734759ff745856b53948873 (fixed)
Vendor states this is fixed in f0f5eb59a97ece0d85de8cfa95dc18c609302a8b (fixed)
Vendor states this is fixed in f3e02edd8322b31b8e6517faa6ba053bf29d1e26 (fixed)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card