ceph: blocklist the kclient when receiving corrupted snap trace
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:
ceph: blocklist the kclient when receiving corrupted snap trace
When received corrupted snap trace we don't know what exactly has happened in MDS side. And we shouldn't continue IOs and metadatas access to MDS, which may corrupt or get incorrect contents.
This patch will just block all the further IO/MDS requests immediately and then evict the kclient itself.
The reason why we still need to evict the kclient just after blocking all the further IOs is that the MDS could revoke the caps faster.
From the CVE record · Linux
When the Linux kernel’s Ceph client receives a corrupted snap trace, continued I/O and metadata access to the MDS may corrupt data or return incorrect contents. The input does not specify how an attacker could cause this condition, whether authentication is needed, or whether user interaction is required.
Engineers running Linux systems that use the kernel Ceph client should check their deployments; affected versions are not specified.