Acknowledged
Created: Jun 18, 2025
Updated: Sep 4, 2026
Resolved Date: Jun 19, 2025
Found In Version: 10.25.33.1
Severity: Standard
Applicable for: Wind River Linux LTS 25
Component/s: Kernel
In the Linux kernel, the following vulnerability has been resolved:EOL][EOL]vfio: Split migration ops from main device ops[EOL][EOL]vfio core checks whether the driver sets some migration op (e.g.[EOL]set_state/get_state) and accordingly calls its op.[EOL][EOL]However, currently mlx5 driver sets the above ops without regards to its[EOL]migration caps.[EOL][EOL]This might lead to unexpected usage/Oops if user space may call to the[EOL]above ops even if the driver doesn't support migration. As for example,[EOL]the migration state_mutex is not initialized in that case.[EOL][EOL]The cleanest way to manage that seems to split the migration ops from[EOL]the main device ops, this will let the driver setting them separately[EOL]from the main ops when it's applicable.[EOL][EOL]As part of that, validate ops construction on registration and include a[EOL]check for VFIO_MIGRATION_STOP_COPY since the uAPI claims it must be set[EOL]in migration_flags.[EOL][EOL]HISI driver was changed as well to match this scheme.[EOL][EOL]This scheme may enable down the road to come with some extra group of[EOL]ops (e.g. DMA log) that can be set without regards to the other options[EOL]based on driver caps.
CREATE(Triage):(User=lchen-cn) [CVE-2022-50117 (https://nvd.nist.gov/vuln/detail/CVE-2022-50117)