Changelog in Linux kernel 6.1.173

 
Linux: Linux 6.1.173 [+ + +]
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Fri May 15 14:49:41 2026 +0200

    Linux 6.1.173
    
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
ptrace: slightly saner 'get_dumpable()' logic [+ + +]
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed May 13 11:37:18 2026 -0700

    ptrace: slightly saner 'get_dumpable()' logic
    
    commit 31e62c2ebbfdc3fe3dbdf5e02c92a9dc67087a3a upstream.
    
    The 'dumpability' of a task is fundamentally about the memory image of
    the task - the concept comes from whether it can core dump or not - and
    makes no sense when you don't have an associated mm.
    
    And almost all users do in fact use it only for the case where the task
    has a mm pointer.
    
    But we have one odd special case: ptrace_may_access() uses 'dumpable' to
    check various other things entirely independently of the MM (typically
    explicitly using flags like PTRACE_MODE_READ_FSCREDS).  Including for
    threads that no longer have a VM (and maybe never did, like most kernel
    threads).
    
    It's not what this flag was designed for, but it is what it is.
    
    The ptrace code does check that the uid/gid matches, so you do have to
    be uid-0 to see kernel thread details, but this means that the
    traditional "drop capabilities" model doesn't make any difference for
    this all.
    
    Make it all make a *bit* more sense by saying that if you don't have a
    MM pointer, we'll use a cached "last dumpability" flag if the thread
    ever had a MM (it will be zero for kernel threads since it is never
    set), and require a proper CAP_SYS_PTRACE capability to override.
    
    Reported-by: Qualys Security Advisory <qsa@qualys.com>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: Kees Cook <kees@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 
x86/CPU/AMD: Add X86_FEATURE_ZEN1 [+ + +]
Author: Borislav Petkov (AMD) <bp@alien8.de>
Date:   Sat Dec 2 12:50:23 2023 +0100

    x86/CPU/AMD: Add X86_FEATURE_ZEN1
    
    Commit 232afb557835d6f6859c73bf610bad308c96b131 upstream.
    
    Add a synthetic feature flag specifically for first generation Zen
    machines. There's need to have a generic flag for all Zen generations so
    make X86_FEATURE_ZEN be that flag.
    
    Fixes: 30fa92832f40 ("x86/CPU/AMD: Add ZenX generations flags")
    Suggested-by: Brian Gerst <brgerst@gmail.com>
    Suggested-by: Tom Lendacky <thomas.lendacky@amd.com>
    Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
    Link: https://lore.kernel.org/r/dc3835e3-0731-4230-bbb9-336bbe3d042b@amd.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

x86/CPU/AMD: Add ZenX generations flags [+ + +]
Author: Borislav Petkov (AMD) <bp@alien8.de>
Date:   Tue Oct 31 23:30:59 2023 +0100

    x86/CPU/AMD: Add ZenX generations flags
    
    Commit 30fa92832f405d5ac9f263e99f62445fa3084008 upstream.
    
    Add X86_FEATURE flags for each Zen generation. They should be used from
    now on instead of checking f/m/s.
    
    Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
    Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>
    Acked-by: Thomas Gleixner <tglx@linutronix.de>
    Link: http://lore.kernel.org/r/20231120104152.13740-2-bp@alien8.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

x86/CPU/AMD: Call the spectral chicken in the Zen2 init function [+ + +]
Author: Borislav Petkov (AMD) <bp@alien8.de>
Date:   Wed Nov 1 11:20:01 2023 +0100

    x86/CPU/AMD: Call the spectral chicken in the Zen2 init function
    
    Commit cfbf4f992bfce1fa9f2f347a79cbbea0368e7971 upstream.
    
    No functional change.
    
    Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
    Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>
    Link: http://lore.kernel.org/r/20231120104152.13740-6-bp@alien8.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache [+ + +]
Author: Prathyushi Nangia <prathyushi.nangia@amd.com>
Date:   Tue Dec 9 10:01:33 2025 -0600

    x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache
    
    commit c21b90f77687075115d989e53a8ec5e2bb427ab1 upstream.
    
    Make sure resources are not improperly shared in the op cache and
    cause instruction corruption this way.
    
    Signed-off-by: Prathyushi Nangia <prathyushi.nangia@amd.com>
    Co-developed-by: Borislav Petkov (AMD) <bp@alien8.de>
    Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
    Cc: stable@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

x86/CPU/AMD: Rename init_amd_zn() to init_amd_zen_common() [+ + +]
Author: Borislav Petkov (AMD) <bp@alien8.de>
Date:   Wed Nov 1 12:34:29 2023 +0100

    x86/CPU/AMD: Rename init_amd_zn() to init_amd_zen_common()
    
    Commit 7c81ad8e8bc28a1847e87c5afe1bae6bffb2f73e upstream.
    
    Call it from all Zen init functions.
    
    Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
    Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>
    Link: http://lore.kernel.org/r/20231120104152.13740-7-bp@alien8.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>