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-72126can: isotp: use unconditional synchronize_rcu() in isotp_release()

Description

In the Linux kernel, the following vulnerability has been resolved: can: isotp: use unconditional synchronize_rcu() in isotp_release() isotp_notify() unregisters the (RCU) CAN filters via can_rx_unregister() and clears so->bound without waiting for a grace period. isotp_release() uses so->bound to decide whether it needs to call synchronize_rcu() before cancelling so->rxtimer, so when NETDEV_UNREGISTER runs first it skips that synchronize_rcu() and can cancel the timer while an in-flight isotp_rcv() is still executing and about to re-arm it via isotp_send_fc(), leading to a use-after-free timer callback on the freed socket. sakisho-bot remarked a problem with rtnl_lock held in isotp_notify(), therefore make isotp_release() always call synchronize_rcu() before cancelling the timers, regardless of so->bound. This still closes the original race (isotp_notify() clearing so->bound without waiting for in-flight isotp_rcv() callers before isotp_release() cancels the RX timer) without adding any RCU wait to the netdevice notifier path.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 months 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

CVSS scores of CVE-2026-72126, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 22bfa94db2ef6900c790884fa9461486516626e9 – < 945d9894502cd9124f5d676181c542ed2000f7c0
    • affected 14a4696bc3118ba49da28f79280e1d55603aa737 – < 59672aa4bcd8d32172c1ff6a179583981d6acabc
    • affected 14a4696bc3118ba49da28f79280e1d55603aa737 – < 15413a082df69175c2f96aeab4c26fe1ff7cff03
    • affected 14a4696bc3118ba49da28f79280e1d55603aa737 – < 6280eda96e0707264849fa7d036fed873c1f8a6d
    • affected 14a4696bc3118ba49da28f79280e1d55603aa737 – < cb6abc584a1bfab107ac003d64948a4aef1730aa
    • affected 14a4696bc3118ba49da28f79280e1d55603aa737 – < b88a511308779c225005d7994b8744561bdbafbc
    • affected 14a4696bc3118ba49da28f79280e1d55603aa737 – < b8278ff605187ef3fa0f2705e93251cce4c4f8ee
    • affected 14a4696bc3118ba49da28f79280e1d55603aa737 – < 9b1a02e0d980ac6b0e36a90378f847062f81d7e4
    • affected 80c6ddf771df2ef786f28c1ca5919b3f1080091b
    • affected ebf91625b3e404bd2b4b694c7ee71c1e8f8bd08f
    • affected 5.10.50 – < 5.10.261
    • affected 5.12.17 – < 5.13
    • affected 5.13.2 – < 5.14
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.10.261 – ≤ 5.10.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .