Strix
26.1K

CVE-2026-64537

Unknown

Last modified

CVE-2026-64537 is a vulnerability of currently unknown severity. 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)..

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 2be665c3940d367e0a2a8128eb4985ce323f99a3, < 2870056a78961e0fecd652362ee9d3fcfd24a8a6; >= 2be665c3940d367e0a2a8128eb4985ce323f99a3, < f0f5eb59a97ece0d85de8cfa95dc18c609302a8b; >= 2be665c3940d367e0a2a8128eb4985ce323f99a3, < 53788b134519e995699ea3721969c96a08d64575; >= 2be665c3940d367e0a2a8128eb4985ce323f99a3, < b42aeb58317f12024734759ff745856b53948873; >= 2be665c3940d367e0a2a8128eb4985ce323f99a3, < a090880c1f544589427e5b7050c40fb211ccecb4; >= 2be665c3940d367e0a2a8128eb4985ce323f99a3, < 865643640b5b5c4579b32d7a55ac9ad648362eaa; >= 2be665c3940d367e0a2a8128eb4985ce323f99a3, < f3e02edd8322b31b8e6517faa6ba053bf29d1e26
LinuxLinux5.11

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-64537?
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).
How severe is CVE-2026-64537?
Severity scoring for CVE-2026-64537 is pending analysis.
How do I fix CVE-2026-64537?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-64537?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST