GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — gh-159811: Raise OpenSSL errors in `_hashlib.HMAC` after re-attaching the thread state by picnixz · Pull Request #159818 · python/cpython

Conversation

@picnixz

@picnixz picnixz commented Oct 19, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

hashlib_openssl_HMAC_update_once() set an exception when the OpenSSL HMAC update function failed, but it was called inside a GIL-released region, with the object's mutex held, by _hashlib.HMAC.update() and _hashlib.hmac_new() when the data exceeds HASHLIB_GIL_MINSIZE bytes. Setting the exception with the thread state detached crashes the interpreter instead of raising an exception.

Remove that helper, call the OpenSSL HMAC update function directly in _hmac_update(), and set the exception once the thread state is re-attached and the mutex is released, as it was done before gh-134531. The OpenSSL error queue is per thread, so the exception type and message are unaffected.

This regression was introduced by gh-134531, so only 3.15 needs a backport. The _hashlib.HASH counterpart, which also affects 3.13 and 3.14, is handled in #159817.

  • Issue: _hashlib: GIL may be released while attempting to set an exception #159811

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@picnixz
picnixz requested a review from gpshead as a code owner October 19, 2026 23:59
@bedevere-app bedevere-app Bot mentioned this pull request Oct 19, 2026
_hashlib: GIL may be released while attempting to set an exception #159811
Closed
@bedevere-app bedevere-app Bot added the awaiting core review label Oct 19, 2026
@picnixz picnixz mentioned this pull request Oct 19, 2026
gh-159811: Raise OpenSSL errors in _hashlib.HASH after re-attaching the thread state #159817
Merged
@picnixz
pythongh-159811: Raise OpenSSL errors in _hashlib.HMAC after re-att…
060abbf
…aching the thread state

`hashlib_openssl_HMAC_update_once()` set an exception when the OpenSSL
HMAC update function failed, but it was called inside a GIL-released
region, with the object's mutex held, by `_hashlib.HMAC.update()` and
`_hashlib.hmac_new()` when the data exceeds HASHLIB_GIL_MINSIZE bytes.
Setting the exception with the thread state detached crashed the
interpreter instead of raising an exception.

Remove that helper, call the OpenSSL HMAC update function directly in
`_hmac_update()`, and set the exception once the thread state is
re-attached and the mutex is released, as it was done before pythongh-134531.
The OpenSSL error queue is per thread, so the exception type and message
are unaffected.
@picnixz
picnixz force-pushed the meta/crypto/c/hashlib/32/hmac-gil-issue-159811 branch from de4951c to 060abbf Compare October 20, 2026 00:07
@picnixz picnixz added needs backport to 3.15 bugs and security fixes sprint labels Oct 20, 2026
@github-project-automation github-project-automation Bot added this to Sprint Oct 20, 2026
@github-project-automation github-project-automation Bot moved this to Todo in Sprint Oct 20, 2026
@picnixz picnixz self-assigned this Oct 20, 2026
@picnixz
picnixz merged commit b4b81e1 into python:main Oct 20, 2026
60 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@github-project-automation github-project-automation Bot moved this from Todo to Done in Sprint Oct 20, 2026
@miss-islington-app

miss-islington-app Bot commented Oct 20, 2026

Copy link
Copy Markdown

Thanks @picnixz for the PR 🌮🎉.. I'm working now to backport this PR to: 3.15.
🐍🍒⛏🤖

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@bedevere-app bedevere-app Bot removed the awaiting core review label Oct 20, 2026
@bedevere-app

bedevere-app Bot commented Oct 20, 2026

Copy link
Copy Markdown

GH-159926 is a backport of this pull request to the 3.15 branch.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@bedevere-app bedevere-app Bot removed the needs backport to 3.15 bugs and security fixes label Oct 20, 2026
@picnixz
picnixz deleted the meta/crypto/c/hashlib/32/hmac-gil-issue-159811 branch October 20, 2026 18:10
picnixz added a commit that referenced this pull request Oct 20, 2026
@miss-islington @picnixz
[3.15] gh-159811: Raise OpenSSL errors in _hashlib.HMAC after re-at…
3421009
…taching the thread state (GH-159818) (#159926)

gh-159811: Raise OpenSSL errors in `_hashlib.HMAC` after re-attaching the thread state (GH-159818)

`hashlib_openssl_HMAC_update_once()` set an exception when the OpenSSL
HMAC update function failed, but it was called inside a GIL-released
region and the object's mutex held by `_hashlib.HMAC.update()` and
`_hashlib.hmac_new()` when the data exceeds `HASHLIB_GIL_MINSIZE` bytes.

Instead, the HMAC update function is called directly in `_hmac_update()`,
and the exception is set once the thread state is re-attached and the mutex
is released (restores the behavior prior to gh-134531).

Since the OpenSSL error queue is per thread, the exception type and message
are unaffected.

(cherry picked from commit b4b81e1)

Co-authored-by: Bénédikt Tran <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gpshead gpshead Awaiting requested review from gpshead gpshead is a code owner

Uh oh!

There was an error while loading. Please reload this page.

Assignees

@picnixz picnixz

Labels

sprint

Projects

Sprint
Archived in project

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@picnixz
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.