graphprotocol / graphprotocol/graph-node
RUSTSEC-2026-0204: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Invalid pointer dereference in
fmt::Pointerimpl forAtomicandSharedwhen the underlying pointer is invalid
| Details | |
|---|---|
| Package | crossbeam-epoch |
| Version | 0.9.18 |
| URL | https://github.com/crossbeam-rs/crossbeam/pull/1276 |
| Date | 2026-07-06 |
| Patched versions | >=0.9.20 |
| Unaffected versions | <0.9.0 |
Affected versions of fmt::Display dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with Atomic::null or Shared::null. fmt::Debug impls and pre-0.9 fmt::Display impls, which do not dereference pointers, are not affected by this issue.
See advisory page for additional details.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the RustSec advisory and the crossbeam-rs/crossbeam pull request linked in the issue, then inspect how graph-node depends on crossbeam-epoch 0.9.18. Done means the affected dependency is no longer used in the affected version and the project’s dependency checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100