Bug 2066522 (CVE-2022-23639) - CVE-2022-23639 rust-crossbeam: unaligned memory accesses and data races could lead to denial of service for 32-bit targets only
Summary: CVE-2022-23639 rust-crossbeam: unaligned memory accesses and data races could...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2022-23639
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2066523
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-22 00:27 UTC by Todd Cullum
Modified: 2022-03-22 04:01 UTC (History)
2 users (show)

Fixed In Version: rust-crossbeam-0.8.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-22 04:01:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Todd Cullum 2022-03-22 00:27:20 UTC
Crossbeam-utils prior to version 0.8.7 incorrectly assumed that the alignment of `{i,u}64` was always the same as `Atomic{I,U}64`. However, the alignment of `{i,u}64` on a 32-bit target can be smaller than `Atomic{I,U}64`. This can cause unaligned memory accesses and data races. Crates using `fetch_*` methods with `AtomicCell<{i,u}64>` are affected by this issue. 32-bit targets without `Atomic{I,U}64` and 64-bit targets are not affected by this issue. This has been fixed in crossbeam-utils 0.8.7. There are currently no known workarounds.

References:
https://github.com/crossbeam-rs/crossbeam/security/advisories/GHSA-qc84-gqf4-9926
https://github.com/crossbeam-rs/crossbeam/pull/781

Comment 1 Todd Cullum 2022-03-22 00:27:35 UTC
Created rust-crossbeam tracking bugs for this issue:

Affects: fedora-all [bug 2066523]

Comment 2 Product Security DevOps Team 2022-03-22 04:01:10 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.