Segfault in invalid concurrent.futures.interpreter.WorkerContext
#127165
Labels
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
extension-modules
C modules in the Modules dir
topic-subinterpreters
type-crash
A hard crash of the interpreter, possibly with a core dump
Crash report
What happened?
It's possible to segfault the interpreter by calling
initialize()
on aconcurrent.futures.interpreter.WorkerContext
instance that was created with theshared
argument being a dict containing the null byte as a key:This doesn't require threads or free-threading. It can be traced to the
_interpreters
module:The backtrace is:
Found using fusil by @vstinner.
CPython versions tested on:
3.14, CPython main branch
Operating systems tested on:
Linux
Output from running 'python -VV' on the command line:
Python 3.14.0a2+ (heads/main:0af4ec3, Nov 20 2024, 21:45:19) [GCC 13.2.0]
Linked PRs
_interpreters
#127199The text was updated successfully, but these errors were encountered: