Home / Affected systems
Inventory
What is still affected?
Your laptop is probably fine. The 15-year controller in a plant, the 32-bit NAS image, and the INT column named created_at are the real list.
| Class | Status | Notes |
|---|---|---|
| 64-bit desktop / server OS | Mostly clear | time_t is 64-bit. Application INT columns can still be 32-bit. |
| Modern iOS / 64-bit Android | Mostly clear | Old 32-bit Android 4-era devices are the exception. |
| 32-bit Linux userland | Mixed | Kernel 5.6+ and glibc 2.34 can be time64. Debian i386 stays time32 on purpose. |
| ext4 large inodes | Extended | Extra epoch bits reach ~2446. 128-byte inodes do not. |
| XFS without bigtime | 2038 | Kernel logs “supports timestamps until 2038”. Enable or recreate with bigtime. |
| MySQL TIMESTAMP | 2038 | Use DATETIME or a 64-bit integer. UNIX_TIMESTAMP improved from 8.0.28 on 64-bit hosts. |
| Embedded / industrial / automotive | Case by case | Long life, rare updates, often 32-bit cores. Verify per product. |
| Windows FILETIME | Different clock | 100 ns since 1601; not Unix time32. 32-bit CRT opt-in is the caveat. |
Ad slot
Rule for this page
We do not mark a product affected without a vendor note, a kernel log, a schema limit, or a reproduced test. “Embedded systems” is a class, not a verdict on your meter.