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-43455mctp: route: hold key->lock in mctp_flow_prepare_output()

Description

In the Linux kernel, the following vulnerability has been resolved: mctp: route: hold key->lock in mctp_flow_prepare_output() mctp_flow_prepare_output() checks key->dev and may call mctp_dev_set_key(), but it does not hold key->lock while doing so. mctp_dev_set_key() and mctp_dev_release_key() are annotated with __must_hold(&key->lock), so key->dev access is intended to be serialized by key->lock. The mctp_sendmsg() transmit path reaches mctp_flow_prepare_output() via mctp_local_output() -> mctp_dst_output() without holding key->lock, so the check-and-set sequence is racy. Example interleaving: CPU0 CPU1 ---- ---- mctp_flow_prepare_output(key, devA) if (!key->dev) // sees NULL mctp_flow_prepare_output( key, devB) if (!key->dev) // still NULL mctp_dev_set_key(devB, key) mctp_dev_hold(devB) key->dev = devB mctp_dev_set_key(devA, key) mctp_dev_hold(devA) key->dev = devA // overwrites devB Now both devA and devB references were acquired, but only the final key->dev value is tracked for release. One reference can be lost, causing a resource leak as mctp_dev_release_key() would only decrease the reference on one dev. Fix by taking key->lock around the key->dev check and mctp_dev_set_key() call.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

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

CVSS scores of CVE-2026-43455, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 98% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 67737c457281dd199ceb9e31b6ba7efd3bfe566d – < 47893166bc5611ee9a20de6b8d2933b2320fb772
    • affected 67737c457281dd199ceb9e31b6ba7efd3bfe566d – < 86f5334fcb48a5b611c33364ab52ca684d0f6d91
    • affected 67737c457281dd199ceb9e31b6ba7efd3bfe566d – < 0695712f3a6f1a48915f95767cfb42077683dcdc
    • affected 67737c457281dd199ceb9e31b6ba7efd3bfe566d – < 925a5ffd99cddd7a7e41d5ad120c7a2c6d50260f
    • affected 67737c457281dd199ceb9e31b6ba7efd3bfe566d – < 8d27d9b260dd19c1b519e1a13de6448f9984e30e
    • affected 67737c457281dd199ceb9e31b6ba7efd3bfe566d – < 7d86aa41c073c4e7eb75fd2e674f1fd8f289728a
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.19 – ≤ 6.18.*
    • unaffected 6.19.9 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .