{"id":121343,"date":"2025-01-15T09:46:00","date_gmt":"2025-01-15T07:46:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-gotovyashhemsya-v-relizu-yadre-linux-6-13-vyyavlen-sboj-vyzvannyj-kodom-sotrudnika-microsoft"},"modified":"2025-01-15T09:46:00","modified_gmt":"2025-01-15T07:46:00","slug":"v-gotovyashhemsya-v-relizu-yadre-linux-6-13-vyyavlen-sboj-vyzvannyj-kodom-sotrudnika-microsoft","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-gotovyashhemsya-v-relizu-yadre-linux-6-13-vyyavlen-sboj-vyzvannyj-kodom-sotrudnika-microsoft","title":{"rendered":"A crash has been identified in the upcoming release of the Linux kernel 6.13, caused by code from a Microsoft employee","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Linus Torvalds intended to release the Linux kernel 6.13 this Sunday, but testing of the 6.13 branch will likely be extended by a week due to stability issues with the changes prepared by a Microsoft employee and accepted into the 6.13 branch in November. It is also noted that the patch that caused the failure was submitted in a non-standard way \u2014 but was accepted, despite not receiving a single acknowledgment (ACK) from the maintainers of the x86 architecture, which is a violation of standard practices. <\/p>\n
The patch added the capability to use large memory pages in ROX (Read Only Execute) mode when allocating memory intended for executable code. ROX allows the use of memory with executable code in read-only mode, complicating the exploitation of certain vulnerabilities. In kernel 6.13, the use of a cache of large executable memory pages reflected as ROX was enabled by default for executable module code on x86_64 systems. The change addressed the issue of mapping ROX pages for executable code that was not yet fully formed and eliminated the need for temporary remapping of ROX pages to write mode until the kernel modules were ready for operation. <\/p>\n
At the final stage of testing the 6.13 kernel, an engineer from Intel identified a failure that prevents the kernel from correctly waking up from sleep mode on some laptops with Intel processors (for example, CPUs based on the Alder Lake microarchitecture). The failure manifested when the kernel was built with the Clang compiler with Control Flow Integrity (CFI) protection mode enabled, which blocks deviations from the normal execution order due to exploits that modify function pointers stored in memory. As a temporary solution, maintainers from Intel and AMD, responsible for the x86 architecture, suggested disabling EXECMEM_ROX usage in kernel 6.13 until a complete patch is prepared and tested to resolve the issue (the initial fix did not solve the problem). \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"