Node.js maintainer and V8 committer speaking. The bug fix should first
land in V8's ToT (tip-of-top). When merged, open a cherry-pick pull
request to node's main branch.
Your cherry-pick is normally back-ported to release branches
automatically (first Current, then later LTS.) If it doesn't apply
cleanly or causes test suite regressions, you'll get a ping on your
pull request with a request to back-port it manually.
If you have a fix for an issue that doesn't exist in upstream V8
anymore, you can open a node pull request targeting the affected
branch directly but mention in the pull request why you're skipping
the "upstream first" process, otherwise it'll get rejected out of
hand.
More details here:
https://github.com/nodejs/node/blob/main/doc/contributing/maintaining/maintaining-V8.md