cxl/features: Serialize multi-part Get/Set Feature transfers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7682b617db1f19bc606b5f1badadcf1e63a87b14, Kernel 77b814c1832fde018c30357b4ec3fcdaa91a1c10 and Kernel c6492e17412048387435f256ffafc4dd6518db28.
In the Linux kernel, the following vulnerability has been resolved: cxl/features: Serialize multi-part Get/Set Feature transfers A Get or Set Feature payload larger than the mailbox payload size is split into several mailbox commands. mbox_mutex only serializes individual mailbox commands and is dropped between iterations of these loops. Nothing serializes the multi-part transfer as a whole. cxl_get_feature() and cxl_set_feature() are reachable concurrently from fwctl (per-fd RPCs run under a read-held registration lock) and from the EDAC scrub/ECS/repair paths, so two transfers to the same mailbox can interleave their parts and corrupt the device's transfer context. Add a per-mailbox feat_mutex and hold it across the whole transfer in both functions. It nests outside mbox_mutex (which is taken inside cxl_internal_send_cmd()), and is taken nowhere else, so no lock-ordering inversion is introduced.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=5e5ac21f629de796ab5d598b59c5e468c6fe4f95 <7682b617db1f19bc606b5f1badadcf1e63a87b14, >=5e5ac21f629de796ab5d598b59c5e468c6fe4f95 <77b814c1832fde018c30357b4ec3fcdaa91a1c10, >=5e5ac21f629de796ab5d598b59c5e468c6fe4f95 <c6492e17412048387435f256ffafc4dd6518db28 | 7682b617db1f19bc606b5f1badadcf1e63a87b14, 77b814c1832fde018c30357b4ec3fcdaa91a1c10, c6492e17412048387435f256ffafc4dd6518db28 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket