The issue allows local users to obtain sensitive information from kernel stack memory. This can be achieved via a crafted ploop driver ioctl call, related to the `ploop getdevice ioc` function in `drivers/block/ploop/dev.c`, or a crafted quotactl system call, related to the `compat quotactl` function in `fs/quota/quota.c`.