erofs: delimit inode_share cache key components
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
erofs: delimit inode_share cache key components
Previously, inode_share keys were encoded as follows:
fingerprint || domain_id
It would be better to have a separator between the fingerprint and domain ID so that the fingerprint won't be parsed as part of a domain ID.
Change the key encoding as follows:
domain_id || '\0' || fingerprint
Since domain_id is a NUL-terminated string, this makes the in-memory key indices unambiguous.
From the CVE record · Linux
The Linux kernel's EROFS inode_share cache encoded keys without a separator between the fingerprint and domain ID. This could make the in-memory key components ambiguous. The input does not describe an attacker action or the access conditions needed to trigger the issue.
Engineers running Linux kernels with EROFS should check their versions; affected versions are not specified.