vfio/mlx5: Fix racy bitfields and tighten struct layout
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.1.178, Kernel 6.18.40, Kernel 7.1.4 and 8 more.
In the Linux kernel, the following vulnerability has been resolved: vfio/mlx5: Fix racy bitfields and tighten struct layout Bitfield operations are not atomic, they use a read-modify-write pattern, therefore we should be careful not to pack bitfields that can be concurrently updated into the same storage unit. This split takes a binary approach: flags that are only modified pre/post open/close remain bitfields, flags modified from user action, including actions that reach across to another device (ex. reset) use dedicated storage units. Note mlx5_vhca_page_tracker.status is relocated to fill the alignment hole this split exposes. Bitfield justifications: migrate_cap: written only in mlx5vf_cmd_set_migratable() at probe chunk_mode: written only in mlx5vf_cmd_set_migratable() at probe mig_state_cap: written only in mlx5vf_cmd_set_migratable() at probe Dedicated storage units: mdev_detach: written in the VF attach/detach event notifier mlx5fv_vf_event() at runtime log_active: written in mlx5vf_start_page_tracker()/ mlx5vf_stop_page_tracker() during runtime dirty tracking deferred_reset: written in mlx5vf_state_mutex_unlock()/ mlx5vf_pci_aer_reset_done() during runtime reset handling is_err: set by tracker error handling and dirty-log polling at runtime object_changed: set by tracker event handling and cleared by dirty-log polling at runtime
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5.19 <6.1.178, >=6.13 <6.18.40, >=6.19 <7.1.4, >=6.2 <6.6.145, >=6.7 <6.12.97, =7.2, >=61a2f1460fd03285ea34c1a235f2f50f71e13a1f <399d806f998f7a25405fc1b97227e579aead24af, >=61a2f1460fd03285ea34c1a235f2f50f71e13a1f <39d163627b51886492bf31f66cb02c94613d2287, >=61a2f1460fd03285ea34c1a235f2f50f71e13a1f <7ed120b1a007bace57c461805519d70e1af44e59, >=61a2f1460fd03285ea34c1a235f2f50f71e13a1f <f1db80a67da928a92ba460ede1be52d8941f46be, >=61a2f1460fd03285ea34c1a235f2f50f71e13a1f <f2365a63b02ddea32e7db78b742c2503ec7b81f1, =5.19, >=61a2f1460fd03285ea34c1a235f2f50f71e13a1f <1dd99b8f4e143592e12e5a77e7b538bc698116cb | 6.1.178, 6.18.40, 7.1.4, 6.6.145, 6.12.97, 399d806f998f7a25405fc1b97227e579aead24af, 39d163627b51886492bf31f66cb02c94613d2287, 7ed120b1a007bace57c461805519d70e1af44e59, f1db80a67da928a92ba460ede1be52d8941f46be, f2365a63b02ddea32e7db78b742c2503ec7b81f1, 1dd99b8f4e143592e12e5a77e7b538bc698116cb |
| linux-kernel: Kernel | >=5.19.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.4, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97 | 6.1.178, 6.18.40, 7.1.4, 6.6.145, 6.12.97 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket