rustsec-2025-0023
Vulnerability from osv_rustsec
Published
2025-04-07 12:00
Modified
2025-10-28 06:02
Summary
Broadcast channel calls clone in parallel, but does not require `Sync`
Details

The broadcast channel internally calls clone on the stored value when receiving it, and only requires T:Send. This means that using the broadcast channel with values that are Send but not Sync can trigger unsoundness if the clone implementation makes use of the value being !Sync.

Thank you to Austin Bonander for finding and reporting this issue.

To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "memory-corruption"
        ],
        "cvss": null,
        "informational": "unsound"
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "tokio",
        "purl": "pkg:cargo/tokio"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.2.5"
            },
            {
              "fixed": "1.38.2"
            },
            {
              "introduced": "1.39.0"
            },
            {
              "fixed": "1.42.1"
            },
            {
              "introduced": "1.43.0"
            },
            {
              "fixed": "1.43.1"
            },
            {
              "introduced": "1.44.0"
            },
            {
              "fixed": "1.44.2"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "GHSA-rr8g-9fpq-6wmg"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "The broadcast channel internally calls `clone` on the stored value when\nreceiving it, and only requires `T:Send`. This means that using the broadcast\nchannel with values that are `Send` but not `Sync` can trigger unsoundness if\nthe `clone` implementation makes use of the value being `!Sync`.\n\nThank you to Austin Bonander for finding and reporting this issue.",
  "id": "RUSTSEC-2025-0023",
  "modified": "2025-10-28T06:02:18Z",
  "published": "2025-04-07T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/tokio"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2025-0023.html"
    },
    {
      "type": "WEB",
      "url": "https://github.com/tokio-rs/tokio/pull/7232"
    }
  ],
  "related": [],
  "severity": [],
  "summary": "Broadcast channel calls clone in parallel, but does not require `Sync`"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.