Summary
A vulnerability in the Linux kernel Ceph client allows an out-of-bounds read caused by an integer overflow when validating snapshot data received from an MDS. The source assigns it a CVSS 3.1 score of 9.8 (critical).
What happened
In the Linux kernel's ceph_update_snap_trace() function, the bounds check for two arrays of snapshot IDs was computed from the sum of two 32-bit counters received over the network. That sum could wrap around to a value smaller than the real one, so the validation let through data that did not fit in the message. As a result, dup_array() read bytes past the end of the message buffer (an out-of-bounds read in slab memory, detected with KASAN). According to the description, this can be reached through an unsolicited CEPH_MSG_CLIENT_SNAP message from a malicious or compromised MDS with no action by the client, and also through snaptraces carried in an MDS reply and in a cap import. The fix computes the length with size_add() and size_mul(), so the result saturates at SIZE_MAX instead of wrapping.
Why it matters
The issue affects the kernel's Ceph client when it processes messages from a malicious or compromised metadata server (MDS), with no client-side action required. The source (CNA: Linux) assigns a CVSS 3.1 score of 9.8, critical severity, with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The source does not report any exploitation and does not include a CWE classification.
Affected products and versions
Linux (kernel). Ranges given by the source: from commit 963b61eb041e8850807d95f8d7a4c6a454c45000 up to, but not including, each of these fix commits: bf8f13872959af1d87e36b7d27096a09fdcf6e47, f0dbd6b9b05e919ebab668f3479aebbcd2431fce, 25ae51760b751d170e29425b7851ee577e2cd5ba and b3bf89767e3ca9506f1c7167cac97c41ec254d42. Version 2.6.34 is also listed as affected; versions earlier than 2.6.34 are listed as unaffected. Versions listed as unaffected are 6.12.117 (6.12.* series), 6.18.63 (6.18.* series), 7.3.4 (7.3.* series) and 7.4-rc1.
| Product | Versions | Fixed in |
|---|---|---|
| Linux Linux | >= 963b61eb041e8850807d95f8d7a4c6a454c45000, < bf8f13872959af1d87e36b7d27096a09fdcf6e47 | — |
| Linux Linux | >= 963b61eb041e8850807d95f8d7a4c6a454c45000, < f0dbd6b9b05e919ebab668f3479aebbcd2431fce | — |
| Linux Linux | >= 963b61eb041e8850807d95f8d7a4c6a454c45000, < 25ae51760b751d170e29425b7851ee577e2cd5ba | — |
| Linux Linux | >= 963b61eb041e8850807d95f8d7a4c6a454c45000, < b3bf89767e3ca9506f1c7167cac97c41ec254d42 | — |
| Linux Linux | 2.6.34 | — |
| Linux Linux | < 2.6.34 | — |
| Linux Linux | 6.12.117 | 6.12.117 |
| Linux Linux | 6.18.63 | 6.18.63 |
| Linux Linux | 7.3.4 | 7.3.4 |
| Linux Linux | 7.4-rc1 | 7.4-rc1 |
Action recommended by the source
According to the source, the issue is resolved in Linux kernel versions 6.12.117, 6.18.63, 7.3.4 and 7.4-rc1, and the fixes are published in the git.kernel.org commits listed in the references (bf8f13872959, f0dbd6b9b05e, 25ae51760b75 and b3bf89767e3c). The source does not state any other mitigations.
Fixed in: 6.12.117, 6.18.63, 7.3.4, 7.4-rc1
Sources and references
- https://git.kernel.org/stable/c/bf8f13872959af1d87e36b7d27096a09fdcf6e47 — CVE Program
- https://git.kernel.org/stable/c/f0dbd6b9b05e919ebab668f3479aebbcd2431fce — CVE Program
- https://git.kernel.org/stable/c/25ae51760b751d170e29425b7851ee577e2cd5ba — CVE Program
- https://git.kernel.org/stable/c/b3bf89767e3ca9506f1c7167cac97c41ec254d42 — CVE Program
Relevant change history
Published
Advisory published.