CyberRota Analysis
AI-GeneratedThe vulnerability in the Linux kernel affects the direct access mechanism for device-dax, where incorrect calculations of kernel virtual addresses could lead to improper memory access due to physical gaps in multi-range devices. This flaw can potentially allow for data corruption or system instability, making it critical for developers and system administrators managing Linux environments to prioritize updates. Organizations utilizing Linux systems with device-dax configurations should address this vulnerability promptly to ensure system integrity and reliability.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: dax/fsdev: use __va(phys) for kaddr in direct_access Use __va(phys) instead of virt_addr + linear_offset for the kaddr return in __fsdev_dax_direct_access(). The previous code added a device-linear byte offset to virt_addr (which is __va of ranges[0]), but for multi-range devices with physical gaps between ranges, this linear arithmetic crosses the gap and produces a wrong kernel virtual address. Using __va(phys) where phys comes from dax_pgoff_to_phys() is correct for any range layout because the direct map translates each physical address independently. This leaves dev_dax->virt_addr write-only, so remove the field (suggested by Dave Jiang).