ext4: verify orphan file size is not too big
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37 · < 0a6ce20c156442a4ce2a404747bb0fb05d54eeb3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: verify orphan file size is not too big
In principle orphan file can be arbitrarily large. However orphan replay needs to traverse it all and we also pin all its buffers in memory. Thus filesystems with absurdly large orphan files can lead to big amounts of memory consumed. Limit orphan file size to a sane value and also use kvmalloc() for allocating array of block descriptor structures to avoid large order allocations for sane but large orphan files.
From the CVE record · Linux
The Linux kernel's ext4 orphan replay can consume large amounts of memory when a filesystem has an excessively large orphan file. An attacker who can cause such a filesystem to be replayed could trigger this memory consumption; the input does not specify authentication or user-interaction requirements.
Anyone running the Linux kernel with ext4 should check whether their version is affected; affected versions are not specified.