If it's a kernel regression, please bisect.

https://docs.kernel.org/admin-guide/bug-bisect.html

I'm almost sure it's down to some user space upgrades that you've recently performed.

It is difficult for me, I use precompiled kernel

the same issue affected me too

This like is the same as https://lore.kernel.org/regressions/0bf3f2f0-0fc6-4ba5-a420-c0874ef82d64@heusel.eu/ and people are working on a fix;

(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #4)
> This like is the same as
> https://lore.kernel.org/regressions/0bf3f2f0-0fc6-4ba5-a420-
> c0874ef82d64@heusel.eu/ and people are working on a fix;

is temperature being read via hdparm? 
I see this:
hdparm -h | grep temp
 -H   Read temperature from drive (Hitachi only)

and for my seagate drive hdparm shows temperature incorrectly. 

or do you mean, that before the temperature query, status check might return an error and thus no temp check was performed?

please also notice that Christian Heusel confirmed this issue on 6.11-rc2 while for me there was everything fine on 6.10.2 and the problem appeared only on 6.10.3 and 6.10.4 

also I have this problem in psensor app which asks temperature info via udisks2 (for sata drives). the data taken via lmsensor (nvme) still shown ok.

That temperature problem and the udisk aspect are mentioned in the thread and the commit that causes it was recently backported, so it's likely the same problem (but I might be wrong, not my area of expertise).

also test on 6.11-rc2 and udisk cannot retrieve temperature on my system

Should be fixed soon:

https://lore.kernel.org/linux-ide/20240812151517.1162241-2-cassel@kernel.org/