Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64537bridge: cfm: reject invalid CCM interval at configuration time

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

Timeline

  1. ID reserved

    By Linux

  2. · 8 days later

    Published

  3. · 21 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Awaiting Analysis.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 2be665c3940d367e0a2a8128eb4985ce323f99a3 – < 2870056a78961e0fecd652362ee9d3fcfd24a8a6
    • affected 2be665c3940d367e0a2a8128eb4985ce323f99a3 – < f0f5eb59a97ece0d85de8cfa95dc18c609302a8b
    • affected 2be665c3940d367e0a2a8128eb4985ce323f99a3 – < 53788b134519e995699ea3721969c96a08d64575
    • affected 2be665c3940d367e0a2a8128eb4985ce323f99a3 – < b42aeb58317f12024734759ff745856b53948873
    • affected 2be665c3940d367e0a2a8128eb4985ce323f99a3 – < a090880c1f544589427e5b7050c40fb211ccecb4
    • affected 2be665c3940d367e0a2a8128eb4985ce323f99a3 – < 865643640b5b5c4579b32d7a55ac9ad648362eaa
    • affected 2be665c3940d367e0a2a8128eb4985ce323f99a3 – < f3e02edd8322b31b8e6517faa6ba053bf29d1e26
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64537 badge
[![CVE-2026-64537](https://cveledger.app/badge/CVE-2026-64537.svg)](https://cveledger.app/cve/CVE-2026-64537)

Record last updated .