Jump to content
  • Microsoft pulls a Windows as it breaks Linux on Intel CPUs and angers AMD in the process


    Karlston

    • 1 comment
    • 2.3k views
    • 3 minutes
     Share


    • 1 comment
    • 2.3k views
    • 3 minutes

    Earlier today, we reported about a happy and content Linus Torvalds, who is offering to make a guitar pedal for one of the lucky Linux devs out there since he is pleased with how things have been this holiday season and the progress with the Linux kernel version 6.13.

     

    Unfortunately for Torvalds, a Microsoft-contributed change nearly ruined it, but Intel and AMD had intervened just in time to save the day.

     

    The change in question was related to a ARCH_HAS_EXECMEM_ROX kernel configuration, which would allow caching of executable memory (EXECMEM) with read-only execute (ROX) permissions. It was being added as a performance improvement feature on Linux 6.13 for x86_64/ AMD64, ie, 64-bit AMD and Intel CPUs.

     

    Unfortunately, this was pushed out without acknowledgement (Ack) from an x86 kernel maintainer, and it has broken the CFI or Control Flow Integrity on such CPUs.

     

    Intel's Peter Zijlstra sent this in today to urgently revert the changes related to EXECMEM_ROX support since there is a lot of work left to be done before it is ready to be pushed out. He wrote:

     

    x86: Disable EXECMEM_ROX support

     

    The whole module_writable_address() nonsense made a giant mess of alternative.c, not to mention it still contains bugs -- notable some of the CFI variants crash and burn.

     

    Mike has been working on patches to clean all this up again, but given the current state of things, this stuff just isn't ready.

     

    Disable for now, lets try again next cycle.

    AMD's Borislav Petkov also expressed his annoyance on the matter as he wrote:

     

    I just love it how this went in without a single x86 maintainer Ack, it broke a bunch of things and then it is still there instead of getting reverted. Let's not do this again please.

     

    -- Regards/Gruss, Boris.

    For those who may not know, Control-flow Enforcement Technology (CET) is an important security feature, and it introduced Shadow Stack and Indirect Branch Targeting (IBT). The former helps defend a system against Return Oriented Programming (ROP) attacks, while the latter protects against Call or Jump Oriented Programming (COP/JOP) attacks.

     

    CET is able to do so by checking the normal program stack against a hardware-stored copy (the Shadow Stack) to ensure that the integrity of return addresses is maintained. In simple words, Shadow Stack stops malware from taking over the process steps of legitimate software as it flags potentially compromised software from executing.

     

    Source


    Hope you enjoyed this news post.

    Thank you for appreciating my time and effort posting news every day for many years.

    News posts... 2023: 5,800+ | 2024: 5,700+

    RIP Matrix | Farewell my friend  :sadbye:


    User Feedback

    Recommended Comments



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...