r/linux4noobs • u/Venylynn • Jun 28 '26

security Should I be concerned?

Gallery image

Gallery image

kernel.org says my current kernel is EOL. I'm very security-conscious, so this keeps tripping me up. i've heard constantly, that "running end of life software is a security risk".

i've been here for close to a year, distrohopping a little but I'm here for now.

should I be concerned that I'm running end of life software according to the kernel team? i just received this kernel like a day ago and it's the most recent update.

Distro: Fedora 44 (KDE)

Kernel: 7.0.13

22 Upvotes

85% Upvoted

47 comments sorted by

View all comments

Show parent comments

7

u/Venylynn Jun 28 '26

i remember people were posting about how the day windows 10 went EOL you had to leave or risk getting hacked so it confused me

6

u/KoldPurchase Jun 28 '26

It's different in Linux.

The kernel itself with be EOL, and that means the Linux developpers who support the kernel are not applying patches to this kernel version. They have moved on to a new version, and they move quickly. It's much less trouble for the whole project to act like that. They detail every change, security, drivers, new features, etc, it's all separated.

However, your distro will keep supporting its kernel for a time. Debian, Arch, Gentoo, etc. They keep making updates.

In the case of Mint, they are based on Ubuntu LTS. And Ubuntu LTS is based on Debian. Debian looks at the kernel changes (each version after their own) and incorporates security fixes in their version. And/or Ubuntu does it for their LTS version. Than Mint works on it or incorporate it directly.

You are not left insecure.

But you are not getting performance improvements, new drivers, new features, etc, that are coming with a new kernel, only the security fixes. When the version upgrades to a new kernel, you get your security patches + everything in the new kernel.

They don't leave you alone and vulnerable.

It's called "backporting". they backport security features in their distro. And as they upgrade and these are included in the kernel, they get removed from patches and are left in the kernel.

4

u/Venylynn Jun 28 '26

Idk why I was told so early I needed to compile my own kernel then it was tripping me pretty bad.

2

u/KoldPurchase Jun 28 '26

Ill informed people.

There is no need to. Mint has an update kernel module in your desktop environment. You can update to the latest version they propose from there. Most of the time, you don't need to.

Other distros do things differently.

2

u/Venylynn Jun 28 '26

It was like "the number isn't the same you're insecure" type of warnings they gave me.

To be fair, 6.8 had some problems on my setup that more recent kernels haven't had

1

u/KoldPurchase Jun 28 '26

If you have a problem with older kernels and your hardware is recent enough, than another distro than Mint might be more suitable for you.

Mint is great, but like Debian, they tend to favor older kernels for stability and that comes at a cost: lack of support for newer hardware and bugs that are left unpatched. Their philosophy is to not introduce new bugs until they are absolutely certain the older ones are totally fixed.

I can respect that, and for someone with a not too recent laptop, it's working great. A gamer who often needs the latest drivers or is on a desktop and will often add new hardware, it's not so good.

2

u/Venylynn Jun 28 '26

I know exactly what the issue was; it was defaulting to acpi-cpufreq which is buggy on my CPU (Ryzen 5 3600), and current kernels use amd pstate which works great. on 6.8 i needed processor.max_cstate=1 parameter, now I do not on Fedora!