October 9, 2025, 3:36 pm | Read time: 2 minutes
The Y2K38 problem affects systems used worldwide in many sectors. It’s particularly critical for industrial control systems and critical infrastructures, as it can lead to chain reactions.
About 25 years ago, the so-called Year 2000 problem caused significant concern. The issue stemmed from outdated programming practices from the 1960s and 1970s that stored only the last two digits of a year. Many feared that computer systems might fail at the turn of the millennium. Thanks to extensive corrections, the anticipated collapse was avoided. Now, experts warn of a similar risk—the so-called Y2K38 problem, which primarily affects Unix-based systems.
Background and Technical Cause
The Y2K38 problem is based on how Unix time is counted. This method of timekeeping stores the elapsed time since Jan. 1, 1970, as continuous seconds in a 32-bit integer. This number can represent a maximum of 2,147,483,647. Once this value is reached, the counter resets to –2,147,483,647. This corresponds to Feb. 13, 1901—a date outside the expected timeframe for computer systems.
The critical moment will be reached on Jan. 19, 2038, as reported by “Security Week.” All systems based on the classic 32-bit representation of Unix time are affected. This includes operating systems like Linux and macOS, as well as many embedded systems in everyday devices such as cars, routers, smart TVs, or e-book readers.
Possible Consequences and Risks
Experts fear that the Y2K38 problem could have more severe impacts than the Millennium Bug. With significantly more systems digitally interconnected today, the potential damage is considerably greater. A failure in industrial controls, the military, or safety-critical areas like energy supply and transportation would be particularly critical.
An overflow of the Unix counter could lead to software processing incorrect time data, processes crashing, or stored data being damaged. In the worst case, systems that people rely on could fail.
There is still time to convert the affected systems to a 64-bit time representation, which will keep the counter usable well beyond 2038. However, the effort is likely to be substantial, similar to the preparations for the Millennium Bug.