CVE-2026-64537
CVE CVE-2026-64537EUVD EUVD-2026-49588Published 2026-07-27T20:10:32.000Z
What the advisory describes
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).
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.1.178; patch: 6.6.145; patch: 7.1.5; 2be665c3940d367e0a2a8128eb4985ce323f99a3 <53788b134519e995699ea3721969c96a08d64575; 2be665c3940d367e0a2a8128eb4985ce323f99a3 <f0f5eb59a97ece0d85de8cfa95dc18c609302a8b; patch: 6.18.40; patch: 7.2-rc1; 2be665c3940d367e0a2a8128eb4985ce323f99a3 <a090880c1f544589427e5b7050c40fb211ccecb4; 2be665c3940d367e0a2a8128eb4985ce323f99a3 <b42aeb58317f12024734759ff745856b53948873; 2be665c3940d367e0a2a8128eb4985ce323f99a3 <2870056a78961e0fecd652362ee9d3fcfd24a8a6; 2be665c3940d367e0a2a8128eb4985ce323f99a3 <f3e02edd8322b31b8e6517faa6ba053bf29d1e26; patch: 5.15.212; 5.11; patch: 0; patch: 6.12.97; 2be665c3940d367e0a2a8128eb4985ce323f99a3 <865643640b5b5c4579b32d7a55ac9ad648362eaa
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.