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-98301net: bridge: mst: move switchdev call outside rcu

Description

In the Linux kernel, the following vulnerability has been resolved: net: bridge: mst: move switchdev call outside rcu This is a follow-up of one of sashiko's pre-existing bug reports. br_mst_set_state() calls switchdev_port_attr_set() for nonzero MSTIs while holding rcu_read_lock() which invokes the blocking switchdev notifier chain and may sleep. Nonzero MSTI changes come from netlink with rtnl held. Move the switchdev call before entering the rcu section and assert that rtnl is held. The call cannot be deferred because netlink needs its error and extack. Also DSA reads the old bridge MST state during the callback and checks it. A deferred callback will be late and will see the updated state.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (13 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 8ca9a750fc711911ef616ceb627d07357b04545e – < b9661fd2423fc25e91e0517ecc0b6156ad83e3a8
    • affected 4488617e5e995a09abe4d81add5fb165674edb59 – < 6b431b63219853eef4054e2f1cb073d2ca2059b4
    • affected 3a7c1661ae1383364cd6092d851f5e5da64d476b – < abf734d150c61acfdfee102169d0e5d1c482e285
    • affected 3a7c1661ae1383364cd6092d851f5e5da64d476b – < d5c4ee1fa4e83a12afc051c831936cd8e006cde3
    • affected 3a7c1661ae1383364cd6092d851f5e5da64d476b – < c40ed3e884c8dc0350f26484030438ef24208ff1
    • affected 3a7c1661ae1383364cd6092d851f5e5da64d476b – < 18a6fe05fb6e18de29fa90d388bb34044114b3d8
    • affected a2b01e65d9ba8af2bb086d3b7288ca53a07249ac
    • affected e43dd2b1ec746e105b7db5f9ad6ef14685a615a4
    • affected 6.1.93 – < 6.1.189
    • affected 6.6.33 – < 6.6.158
    • affected 6.8.12 – < 6.9
    • affected 6.9.3 – < 6.10
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .