arm64: mte: Do not warn if the page is already tagged in copy_highpage()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0bbf3fc6e9211fce9889fe8efbb89c220504d617, Kernel 5ff5765a1fc526f07d3bbaedb061d970eb13bcf4 and Kernel b98c94eed4a975e0c80b7e90a649a46967376f58.
In the Linux kernel, the following vulnerability has been resolved: arm64: mte: Do not warn if the page is already tagged in copy_highpage() The arm64 copy_highpage() assumes that the destination page is newly allocated and not MTE-tagged (PG_mte_tagged unset) and warns accordingly. However, following commit 060913999d7a ("mm: migrate: support poisoned recover from migrate folio"), folio_mc_copy() is called before __folio_migrate_mapping(). If the latter fails (-EAGAIN), the copy will be done again to the same destination page. Since copy_highpage() already set the PG_mte_tagged flag, this second copy will warn. Replace the WARN_ON_ONCE(page already tagged) in the arm64 copy_highpage() with a comment.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.11, >=060913999d7a9e50c283fdb15253fc27974ddadc <0bbf3fc6e9211fce9889fe8efbb89c220504d617, >=060913999d7a9e50c283fdb15253fc27974ddadc <5ff5765a1fc526f07d3bbaedb061d970eb13bcf4, >=060913999d7a9e50c283fdb15253fc27974ddadc <b98c94eed4a975e0c80b7e90a649a46967376f58 | 0bbf3fc6e9211fce9889fe8efbb89c220504d617, 5ff5765a1fc526f07d3bbaedb061d970eb13bcf4, b98c94eed4a975e0c80b7e90a649a46967376f58 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket