From this webpage screenshot, the following key information about the vulnerability can be obtained: 1. Vulnerability Description: - Issue Description: In dm cache, an out-of-bounds access may occur if the fast device is unexpectedly expanded before the first suspend. This happens because expanding the fast device requires reloading the cache table, and the cache table size may not match the new fast device size, leading to incorrect checks during the first suspend and resulting in out-of-bounds access. - Reproduction Steps: 1. Prepare the component device. 2. Load the cache table, and deliberately expand the fast device before suspending the cache, causing a mismatch in kernel data structures. 3. Suspend the cache to write the kernel dirty bitmap and hint array, triggering an out-of-bounds access at offset 0x40 in the dirty bitmap. 2. KASAN Report: - KASAN reported an out-of-bounds access error in the function. - Virtual address: 0x82b/0x80, size: 8 bytes. 3. Fix: - The issue is fixed by checking for cache size changes during the first suspend. 4. Sign-off and Attribution: - Submitted by: Ming-Hung Tsai - Fixes: dm cache: cache shrinking support - CC: stable@vger.kernel.org - Signed-off-by: Mikulas Patocka, Joe Thornber, Greg Kroah-Hartman 5. Diffstat: - One file ( ) was modified with 16 insertions and 21 deletions. 6. Diff Content: - Modified the function by adding code to check for cache size changes. - Modified the function by adding code to check for cache size changes. This information indicates that the vulnerability arises when the fast device is expanded, causing a mismatch between the cache table size and the fast device size, leading to incorrect checks during the first suspend and resulting in out-of-bounds access. The fix involves checking for cache size changes during the first suspend to resolve the issue.