Open Bug 1808236 Opened 2 years ago Updated 2 years ago

Intermittent TSAN socketprocess netwerk/test/unit/test_ech_grease.js | data race in memcpy

Categories

(Core :: Networking, defect, P2)

defect

Tracking

()

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 2 open bugs)

Details

(4 keywords, Whiteboard: [necko-triaged])

Attachments

(1 file)

Context - I'm looking at scheduling socketprocess xpcshell tests on more Linux configurations and this data race is happening in test_ech_grease.js pretty frequently (but not as often as the race in bug 1808235).

Blocks: 1808234, tsan
Group: core-security → network-core-security
Attached file tsan log

The "previous write" stack involves setting some SSL integer pref, which the test does in a few places. Users hopefully are not changing their crypto prefs all of the time so it doesn't really seem exploitable. I'll mark it moderate but maybe it could be unhidden.

Dana, it looks like you touched this test last, so this might be of interest. Thanks.

Flags: needinfo?(dkeeler)

Yeah, this doesn't seem exploitable to me. The relevant NSS API isn't thread-safe, but it's just enabling or disabling some ciphersuites. We could either make this an NSS problem and add some locks, or we could only touch NSS configuration stuff on the socket thread (which wouldn't be too hard, and is arguably the correct approach anyway).

Flags: needinfo?(dkeeler)
Group: network-core-security
See Also: → 1808816

FYI, test_ech_grease.js was skipped for the time-being when bug 1808234 landed, so it'll need re-enabling as part of the patch for this bug.

Blocks: socket-proc
Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: