Looks like a display glitch in cpview and probably not a real underlying problem. If you convert some of those decimal values to hex and binary you can see they are bumping up against the maximum size/precision of the cpview display variable, or possibly have wrapped around backwards from the precision upper boundary FFFFFFFFFFFFFFFF:
18,446,744,073,709,212,468
FFFFFFFFFFFAD334
1111111111111111111111111111111111111111111110101101001100110100
18,446,744,073,708,827,132
FFFFFFFFFFF4F1FC
1111111111111111111111111111111111111111111101001111000111111100
Attend my 60-minute "Be your Own TAC: Part Deux" Presentation
Exclusively at CPX 2025 Las Vegas Tuesday Feb 25th @ 1:00pm