If a bad actor capable of doing this is at my computer they're taking the whole computer with or without this vulnerability. Picking it up and walking away.
Not to say it shouldn't be fixed, just that it isn't worth panicking over for most users.
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
If a bad actor capable of doing this is at my computer they're taking the whole computer with or without this vulnerability. Picking it up and walking away.
Not to say it shouldn't be fixed, just that it isn't worth panicking over for most users.
so judging from this: https://ubuntu.com/blog/copy-fail-vulnerability-fixes-available
i should be affected (v25.10):
kmod 34.2-2ubuntu1.1
but even after running the updates and rebooting the version hasn't changed...
ii kmod 34.2-2ubuntu1.1 amd64 tools for managing Linux kernel modules
and i don't get how the kmod version is relevant as it should be the kernel number, no? which is:
Kernel: Linux 6.17.0-23-generic
for me
edit: i just realized it says "Fixed Version" on top, this couldn't be more confusing if they tried...
The kmod change makes it so the affected module cannot be loaded, it was their initial workaround
ah ok, so it is just mitigated by this and not fixed like with a kernel update, do i understand this right?
Edit: to be clear, this advice is specific to Ubuntu. If you come across this and need advice for a different distro, message me or reply to this
Yes.
Ubuntu doesn't follow upstream kernels, so they will have to make a custom backport for 6.17 to fix the kernel
It's very unlikely you need the module that has the bug, so the mitigation should work for you
Just double check lsmod | grep aead
As long as that module is not loaded, and you have the kmod update that adds /etc/modprobe.d/disable-algif.conf you're protected
thank you very much!
lsmod | grep aead
just returns nothing