TYPO3 Core

Also occurs in current master.

But there it's only on ElementInformation and not on FileList's default view.

I can confirm with TYPO3 11 on centOS.
In the databases I looked at,

SELECT name, FROM_UNIXTIME(creation_date) as created, FROM_UNIXTIME(modification_date) as modified
    FROM sys_file
        WHERE creation_date < modification_date

returns zero or next to it. That means that creation_date is always newer or equal to modification_date (which is the wrong way round, creation_date should stay fixed, while modification_date should be raised sometimes.

The core file Indexer has this:

  $mappingInfo = [
            // 'driverKey' => 'fileProperty' Key is from the driver, value is for the property in the file
            'size' => 'size',
            'atime' => null,
            'mtime' => 'modification_date',
            'ctime' => 'creation_date',
            'mimetype' => 'mime_type',
        ];

The `ctime` field of a file is the CHANGE time, it is NOT the creation time. The TYPO3 core got this totally wrong, since ever. In most file systems an actual creation time of a file is not known.

ctime (filesystem node change time) gets updates whenever anything regarding the file changes (like name, access modifiers, content, ...).
But mtime (content modification time) gets only updates when the content changes.

So, usually ctime >= mtime.