The flaw lies in the time/namespace subsystem of the Linux kernel. The proc_timens_set_offset() function accepts a timespec64 structure and validates only the seconds component, ignoring that the nanoseconds field must be in the range 0 to 999,999,999. This omission allows negative or excessively large values to be passed to timespec64_add(), which expects normalized inputs. The resulting incorrect arithmetic can produce corrupted timestamps and unpredictable time‑keeping behavior, potentially affecting scheduling, logging, or authentication mechanisms dependent on accurate time.

Affected systems are Linux kernels on all architectures that implement the time‑namespace proc interface without the added validation. The advisory does not provide a specific version range; any kernel that predates the commit adding the check is considered vulnerable.

The EPSS score indicates that exploitation is expected to be rare, and the vulnerability is not listed in the CISA KEV catalog. No remote exploitation path is documented; an attacker would typically need local code execution or privileged interaction with the /proc/time namespace entries. Without a crafted exploit the risk remains largely theoretical, but the missing validation justifies timely remediation.