It is surprisingly easy to corrupt the FPU state on Intel Macs running macOS Sonoma.

main.mm

#import <Cocoa/Cocoa.h>
#import <iostream>

static long double _giantValue = 0.0;

void writeGiantValue(long double inValue) {
	_giantValue = inValue;
}

long double readGiantValue() {
	return _giantValue;
}

static void interactWithGiantValue(void) {
	writeGiantValue(1.0);
	long double gv = readGiantValue();
	if ( gv != 1.0 ) {
		std::cout << "ERROR: Giant value should be 1, but it is instead " << gv << std::endl;
	} else {
		std::cout << "All good. Giant value is " << gv << std::endl;
	}
}

int main(int argc, char *argv[]) {
	/* 
		 Before decoding the troublesome image, we can interact with Float80
		 values, and not encounter any problems.
	 */
	interactWithGiantValue();

	/* 
		 Load the image, and force it to be decoded.
	 */
	NSImage *songAlbumArt = [[NSImage alloc] initWithData:[NSData dataWithContentsOfURL:[NSURL fileURLWithPath:@"artwork.jpg"]]];
	id imageRef = [songAlbumArt TIFFRepresentation];

	/* 
		 On Intel machines running macOS Sonoma, this will report a NaN value being
		 read from _giantValue. This is likely a result of someone corrupting---or,
		 failing to restore---the FPU state.
	 */
	interactWithGiantValue();

	return 0;
}

If you have the jpeg image that triggers this, here's the output on an Intel Mac running Sonoma:

% clang -o testFPU -O0 main.mm -L. -std=gnu++20 -framework Cocoa -lstdc++

% ./testFPU 
All good. Giant value is 1
ERROR: Giant value should be 1, but it is instead nan