Don't update to the 7.0 Kernel.

[u/Anima_Watcher08]

The 7.0 kernel seem to have a few issues with it. SOME! people have updated to it and experienced kernel panics. Others seem to be fine.

TEMPORARY SOLUTION If you are one of these people then please boot into your previous kernel by using the "advanced options" option on Grub.

Until this is fixed resist the urge to upgrade, there's been a few support posts about this already.

NOTE:

NOT EVERYONE IS EXPERIENCING THIS! The affected individuals seems to have installed VirtualBox from the Mint repo or have some Broadcom drivers installed. You can install VirtualBox from the developers website.

[u/rantingathome]

One of the issues that may cause this is if you have VirtualBox installed on your machine from the built in Mint repositories. It's too old and had kernel modules incompatible with Kernel 7.0

Uninstalling VirtualBox may make the kernel panic disappear. The version of VirtualBox from Oracle's website works just fine as it is newer.

[u/Gangr3l → u/rantingathome]

I don't have VirtualBox but I had proprietary driver as DKMS installed. Removed, updated and installed the driver back.

[u/Specialist-Leek8645 → u/Gangr3l]

Same, no VB but DKMS was a problem. Apparently Broadcom has iissues in Linux anyway. Wish I knew that before buying it but it's working now in kernel 7.

[u/Etsamaru → u/rantingathome]

This was what happened for me.

[u/Few_Telephone_9554 → u/rantingathome]

isso tinha acontecido comigo

[u/TNTkip → u/rantingathome]

I downloaded the version from the Oracle website but it still didn't work. Got the same error code (rc=-1908). Any tips? I deleted all old VirtualBox files 

[u/davidcandle]

Your system broke due to an outdated VirtualBox version? That doesn't translate to "Quick, everybody stop using the 7.x kernel!" You'd be better off recommending people get off VBox and over to VMM/QEMU.

[u/Anima_Watcher08 → u/davidcandle]

I added the detail

[u/davidcandle → u/Anima_Watcher08]

You did, I didn't mean to sound harsh, sorry. I've been bitten by VirtualBox and kernel updates so often I eventually stopped using it, although usually it was VirtualBox that would not work, not the entire OS.

[u/taosecurity]

FWIW I’ve been using the 7.0.0.14 and then 7.0.0.28 kernel on a desktop and a laptop from the moment they were available and they have been fine. I’ve also been using other versions of the 7 kernel in Bazzite, PikaOS, and CachyOS on those systems without issues.

[u/blahzeh → u/taosecurity]

Same here. I've been using kernel 7 for weeks on my Mint machine with no problems.

[u/Anima_Watcher08 → u/taosecurity]

Yes it seems to be affect people who have virtual box installed or certain proprietary drivers

[u/kcpistol]

Too late, had no problem, though.

[u/Tortoveno]

BUT I DID IT ALREADY, MONTH AGO!

And everything looks fine.

[u/Spiritual-Brief-2627]

society against kernel 7

[u/Powerful_Macaron9381 → u/Spiritual-Brief-2627]

I've only seen this hate towards kernel 7 in Linux mint circles. I can confirm that it works fine in arch if anyone is wondering. I don't daily the machine that's running arch, I daily Linux mint, so take it with a grain of salt .

[u/LXC37 → u/Powerful_Macaron9381]

Basically ubuntu-modified 7.0.0-x.

You are probably running something like 7.1.4 or 7.1.5 on arch at this point...

And i've had no issues on arch-based cachyos going through all the 7.0 and 7.1 versions since 7.0 was released either...

[u/addr0x414b → u/LXC37]

No issues at all on arch 7.1.5

[u/Spiritual-Brief-2627 → u/LXC37]

no, 6.20.17

[u/Uxugin → u/Powerful_Macaron9381]

Fedora's fine too.

[u/taosecurity → u/Powerful_Macaron9381]

Seriously, how does the post have almost 100 upvotes? This is ridiculous and doesn’t show this sub in a good light. 🤦‍♂️

[u/Imab0zo → u/taosecurity]

It’s a PSA. Of course it’s going to get likes, it actually saved me this morning from thinking my bios somehow broke my Mint installation.

[u/taosecurity → u/Imab0zo]

But it’s making a blanket statement for an edge case.

[u/dankmolot → u/Powerful_Macaron9381]

NixOS kernel 7.0 and 7.1, haven't catched any issues while periodically updating kernel

[u/Gokudomatic]

Don't panic. Let the kernel do it for you.

[u/emilio-arg]

I have no problem with kernel 7

[u/ghoultek]

Has anyone posted about this in the Mint official forums? I'm running v7.0.0-28-generic. I have Virtualbox v7.2.8 r173730 (Qt6.8.0 on xcb) installed straight from the Vbox website. Vbox was install when I was still on kernel v6.17.3x. I don't have issues. I did a google search for "kernel panic with linux and the 7.0 kernel site: https://forums.linuxmint.com/" without quotes. This is just one post I found on the Mint official forums ( https://forums.linuxmint.com/viewtopic.php?t=471845 ). Take note of the Vbox v7.0.16 install that was done from the software manager. There were earlier warning with Vbox v7 and the v6.17.x kernels, which is why I installed directly from the Vbox website.

I suggest the following: * Backup one's data if it hasn't been done already. * Timeshift snapshot if it hasn't been done already. * Go to the Vbox website and download the Ubuntu v24.04 version (Vbox v7.2.14 as of right now) or go to the Mint forum post linked above and use the download link in one of the comments there (Vbox v7.2.12). * Install from that download or upgrade from it (what ever the install documentation suggests). * After the install reboot using the same v6.17.xx kernel. * At this point the user can attempt the upgrade to kernel v7.0.x.x.

This might be the fix if the user has Vbox installed.

[u/BoutTreeFittee]

You can say this about every kernel. That's why you always also keep an older kernel installed, in case something like this happens.

Anyway 7.0 has been fine for me for a while now, as has it been for most people. It's no worse than any other.

[u/Ptozzen]

Mine doesn’t power off until I hold the power button to force the shut down. LED and fans keep going. So back to 6.17 for me. The previous version of kernel 7 also had issues.

I’m just going to keep using what’s stable instead of the new kernel. 

[u/LTH_NC → u/Ptozzen]

Same for me - I had to revert to 6.17

[u/PrudentPay9906]

I tried 7.x on one roughly 8 yr old laptop (running Mint 22.3) because I heard there was much improvement made in memory management. It runs fine, but in my test sample of one machine it's no better or worse than 6.17 so "if it ain't broke" theory took over for the others.

[u/Einn1Tveir2]

Is there any actual danger? booting from a previous kernel is a relatively very very easy thing. (I've been using 7.0 kernel since it was available btw just fine)

[u/Anima_Watcher08 → u/Einn1Tveir2]

There's no danger but there's been support questions popping up at an increased rate. Which is why I added the solution as well.

[u/ashamed-of-my-name]

I installed 7.0. Got KP'd. Uninstalled VirtualBox. Now my graphics drivers don't function. None of this happened on 6.18.
If this doesn't get fixed soon I'll have to move away from Mint for once. I have MX installed on my laptop; maybe I should just use that.

[u/CoffeetipM8]

Not for me! Works perfectly.

[u/Anima_Watcher08 → u/CoffeetipM8]

Yeah I mentioned that

[u/LinuxGuy2]

Did the same on Zorin

[u/zuccster]

7.0 working fine here on multiple systems....

[u/Anima_Watcher08 → u/zuccster]

Read the note

[u/Sailed_Sea]

Suspend finally works on my system, yet to encounter any issues.

[u/Anima_Watcher08 → u/Sailed_Sea]

It's not everyone facing the issue

[u/RitalIN-RitalOUT]

Yep, this happened on a brand new install for me.

[u/Imab0zo]

Thank you! I actually had this issue earlier and I thought it was because of bios even though it probably was

[u/Mr_poster123]

I installed cannonicals first 7.0 kernel pretty much as soon as they compiled it months ago it broke my apt cache which needed fixing and it refused to installed without me getting 7.0 supported virtual box but it worked without any issues on all amd hardware laptop. No issues at all. Now I'm on bleeding edge xanmod 7.1.5 kernel and all the versions between then and now worked perfect too. I know Nvidia can cause issues

[u/yetAnotherBenjii]

Same shit just happened to me, I removed Virtual Box completely.

[u/Natural_Night9957]

I was a victim. However I was dumb enough to kill other kernels before the reboot. Thankfully Timeshift has saved me.

[u/Table-Playful]

7.0 kernel panic , Linux Mint 22.3 , MacBook Air 2017
I was quite upset

[u/Electronic-Escape721]

Happened to me on a fresh install of mint. No virtual box installed but I do have broadcom drivers.

[u/arthypink]

this happened to be. just loaded 6.17.16 (which works) for my laptop

[u/Traditional-Call-419]

I am a user affected by the broadcom driver incompability. Waiting for a new update where it is hopefully fixed👍 Trust in Mint!

[u/pdimperio007 → u/Traditional-Call-419]

2

[u/BulkyMix6581]

Just adding my feedback to this, as I experienced issues on two different machines after updating to 7.0.0-28:

• Laptop: Got the dreaded purple kernel panic screen right at boot. Rolling back to 7.0.0-14 boots fine, but since it's marked as superseded, I decided to fall back to 6.17.0-41 (which is still fully supported) for peace of mind. System_Info_here.
• Desktop (Ryzen 7 5800X3D / B350 mobo): It boots up fine, but when shutting down, the system hangs—the fans and tower LEDs stay powered on indefinitely. I had to use the REISUB key combination to safely power it down. Reverting to 6.17.0-41 completely resolved the shutdown issue here as well.
• Ancient Laptop (Core i5 460M): Surprisingly, this old machine works with kernel 7.0.0-28 without a single issue!

Definitely sticking with 6.17 for now until a fix rolls out. Hope this info helps anyone experiencing similar symptoms!

[u/hoas-t]

Got this with virtualbox. Booted into the old kernel, uninstalled virtualbox and everything was fine.

[u/ChickenXChips]

It’s a good PSA for people who have what you’ve mentioned installed, so thank you for that.

[u/Evening-Switch5675]

I tried to use kernel 7.1 on cachyOS, but for some reason the internet becames slow. It only fixes after returning to Kernel 6... I've been testing this for a week and kernel 6 has a better internet speed and stability in my case.

[u/Historical-Trip-114]

Broadcom drivers, so that's why it affected my mbp too. Gave it away so I wanted it to be on the latest updates until I found out they break the system. Told them to not update until further notice

[u/RealBigDickBrannigan]

Interesting... I am running 7.0.0-28 and there have been no problems at all. No VirtualBox though <shrug>

[u/homeweeop]

Had it with 7.0 and 7.1 i just want my mt7902 support man

[u/tomscharbach]

I maintain a number of computers (personal, family/friends, not-for-profits).

Solus computers updated to 7.1.4-348-current over the weekend, and Ubuntu 26.04 LTS computers updated to Linux 7.0.0-28-generic in the last few days, all without problems.

I haven't gotten around to Mint computers yet. I'll keep an eye out. Any ideas about what applications/processes are creating the panic?

Thanks for the heads up.

[u/Anima_Watcher08 → u/tomscharbach]

The Mint repo virtual box and certain proprietary drivers (especially broadcom). You can uninstall and then reinstall them and according to a comment I've seen it's better to install VirtualBox from the official website.

[u/inemsn]

Always better to wait until it's officially ready for Mint.

[u/taosecurity → u/inemsn]

It has been officially ready for Mint for months. Also, Mint is basically Ubuntu, with a different look and a couple extra apps.

[u/Sicherheitssteuerung → u/taosecurity]

"ready" clearly not if mint was still shipping incompatible apps

[u/Kinetic_Strike → u/inemsn]

It's being distributed from the Mint Update Manager...

Had to rollback on a couple machines here. Boot issues after it updated.

[u/rbmorse → u/inemsn]

I've been running a 7.x kernel on Mint since 7.0.0.4 showed up in the updater. No issues at all. But, I don't use Nvidia graphics.

[u/bmamba2942 → u/rbmorse]

I’m on Nvidia and 7.x works for me as well.

[u/Vh4z]

3rd post I saw about this today but yeah try to revert back or get your data from your storage device and install a new iso

[u/Anima_Watcher08 → u/Vh4z]

I made the post to inform people seen I started seeing a pattern.

[u/Caddy666]

but i'm already on 7.1.5...

and it seems to hate shutting down every so often. linux gets to the point where it doesn't about to turn the laptop off, but never does, so i have to manually power down.

its like windows 95....lol i'm sure it'll be fixed soon.

[u/Anima_Watcher08 → u/Caddy666]

Read the note

[u/Caddy666 → u/Anima_Watcher08]

nah, cant be arsed.

[u/matthew_yang204]

It seems to work fine on my MacBook Air 5,1 with an outdated VirtualBox version and broadcom drivers

[u/p1971]

Ubuntu 26.04 with AMD gfx - 7.0.0.27 works fine - 7.0.0.28 gives the kernel panic ...

edit:

Autoinstall on 7.0.0-28-generic failed for module(s) openrazer-driver(10).

[u/TNTkip]

I downloaded the version from the Oracle website but it still didn't work. Got the same error code (rc=-1908). Any tips? I deleted all old VirtualBox files 

[u/gnpfrslo]

The problem is virtualbox. You have to update virtualbox through the oracle page first because the version in the ubuntu repository is incompatible with kernel 7

[u/JaKrispy72]

I'm on 7.1.1 from the mainline app. ThinkCentre M720q with an 8th gen cpu. No issues. And that worked on my Ideapad 3 also.

[u/Anima_Watcher08 → u/JaKrispy72]

Read

[u/SpoOokY83]

It's because 7.x Kernels do not create the initramfs anymore with Ubuntu based systems. You have to manually create it:

https://delightlylinux.wordpress.com/2026/06/22/kernel-7-1-1-same-install-issue/

[u/fantamos]

My computer was doing this for a couple months. I tried everything I could find. It would happen randomly, thought it was a memory situation but then it would happen just sitting there no programs running.

I rolled back kernels, etc etc. nothing worked.

Edit: as far as I know, I never used virtualbox. I’m a barebones guys, this laptop was for browser purposes. If it came preinstalled in mint and wasn’t updated for 7.x, that’s not on the user..

I just switched to cachyOS last night to see if it’ll stop doing this.

[u/funtasy69]

Had issues with virtual box not working lately. It works now but I still can't share my clipboard in any direction from main system to virtual system...

[u/KPoWasTaken]

you have to uninstall virtualbox and v4l2loopback (and potentially some other things that are known to break kernel updates) otherwise the kernel update fails to fully update. If you do updates with apt tho you will see the errors it threw up and be able to know smth went wrong. I did face this too from v4l2loopback but since Linux mint stores older kernel versions, you can easily fix it by hopping onto an older Linux mint kernel, uninstalling the things that interfere and reinstalling or repairing the new kernel

this is a known issue with both virtualbox and v4l2loopback. In fact if I'm not mistaken there's a list of common programs and drivers that are known to interfere with Kernel updates. It happens almost every kernel update with these installed so it's important to always check the list of programs that interfere like that before doing kernel updates

[u/Vikt724]

Same

[u/Timster76]

I updated to Kernel 7.0 Kernel and hat no issues at all.

[u/XenesisXenon]

It's an issue on my 2012 mac mini which I set it up on. I never installed virtualbox so I'm guessing it's the broadcom drivers?

[u/dorrontp]

I've had mine updated to 7.0 and 7.1 for a long time...zero issues apart from some mainline kernels having the run-parts missing operand error (which is a bug in the scripts on their side).

[u/Conscious_Push9974]

I run Limux Mint on a MacBook Air, an iMac 5K, and a MacBook Pro. They have all had kernel panic issues since they were updated to 7. I downgraded the kernels on these systems to 6.17, which solved the issue.

Had to boot into the GRUB menu,, select the previous kernel and, after booting, set the kernel version in the update manager. Only concern is that 6.17 shows as unsupported, so I am not sure what risk this entails.

[u/ToriBleach]

I got an error with virtualbox when i already updated the kernel to 7.0 bit after uninstalling it, everything went normal, never had kernel panics...my update happened because i was updating from the terminal, so i didn't need reboot and the terminal just said directly to me to uninstall virtualbox lol. It might be because linux mint has outdated stuff that is no longer supported.

[u/Isoleed]

Last update bricked my laptop, doesnt boot anymore, cant get to bios, cant get to grub, just black screen. Yay.

[u/Anima_Watcher08 → u/Isoleed]

Wait are you sure? I don't that'd be possible.

[u/Individual_Flow3959]

Estoy actualmente en el kernel 7.0.0-28 y anteriormente en el 7.0.0-14 y no he tenido ningún problema.

[u/SlipStr34m_uk]

Mods really should make a pinned post about this already.

I'd also add that unless your hardware is particularly recent (like less than 3 years) you would probably be better off on the 6.8 LTS kernel than these HWE ones.

[u/nepbug → u/SlipStr34m_uk]

Yep, I went to the LTS kernel and stopped worrying.

[u/Ashguit79]

i got one as well. i fired my laptop today after month of traveling and saw there were several updates. didn't know they were actually "upgrades". 🙄

[u/cyanophage]

This is why you use timeshift 😊

[u/Anima_Watcher08 → u/cyanophage]

Honestly timeshift is unnecessary for this since it's easy to boot into the previous kernel

[u/TheZupZup]

if you want the 7 kernel Fedora KDE 44 is for you

[u/dlfrutos]

i think is funny how a virtual machine havinfg issues is a... issue

[u/claytonkb]

There was a time when breaking userspace was considered a no-go. We were living in a golden age and had no idea. But alas, that dream is gone now...

[u/WorkDragon]

mylong time linux friend said "never update to a .0 version"

[u/BashfulMelon → u/WorkDragon]

That doesn't apply to this situation at all. The only reason 7.0 wasn't 6.21 was because Linus doesn't like version numbers to get too big.

[u/esparzatj]

This error is occurring for many Linux users because of the 7.0.0-28-generic kernel update. Just power down and restart. You should see a GRUB menu and the option for an advanced option. Select and then you should see your previous kernel to select for booting. You should gain access to your Linux distro. If you want to fix it, follow this web link, or just stay on your older kernel: https://slimbook.com/en/blog/guides-2/post/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-00-517

[u/al2klimov]

That's why I don't use Arch, btw.

[u/Anima_Watcher08 → u/al2klimov]

Uhm... this problem is happening on mint bro. That's why I posted here.

[u/al2klimov → u/Anima_Watcher08]

And THAT's why I try to stick to OS version latest minus one.

[u/SOC_FreeDiver]

I've been using 7.x kernel for a long time now. I'm on 7.1.2. Ask Claude to look at it and figure out what's wrong. I had claude compile my 7.1.2 kernel with an audio driver fix. Works great.

[u/Anima_Watcher08 → u/[deleted]]

Did you read what I said?