This bug seems very much like a similar bug which was introduced with the release of 24H2 around late October/early November 2024, which affected a number of WD_Black 2TB nVME SSDs (ask me how I know). After finally stumbling across an article about the particular bug from 24H2 in a tech blog, I tracked down a firmware update for my drive and all my problems were resolved.
EDIT: Fortunately, none of the three m.2 drives in my recently-built system appear to be affected by this new bug.