Today we're happy to release OSMC's November 2025 update for all supported devices. The nights are drawing in and it's getting colder. So we want to keep your OSMC experience running smoothly. This update brings you Kodi v21.3 with a number of improvements.
It’s probably time to upgrade my Vero 4k+ for a Vero V.
Before I buy one: Which Linux kernel does the Vero V run now?
I hope it’s a version officially supported at https://kernel.org/
Thanks
Still 4.9, but we started work on a newer kernel.
If you have a specific need for an upstream LTS kernel then you may be better off with x86_x64.
Thanks. My “specific need” is to use software that’s supported.
Linux 4.9 has been end-of-life for almost three years now:
This kernel is now END-OF-LIFE and you should move to 4.14.y at the least, 6.1.y is the better option.
That means it’s bitrotting bugs and security vulnerabilities that are not getting fixed.
See the end-of-life message for Linux 4.19:
As a “fun” proof that this one is finished (and that any company saying they care about it really should have their statements validated with facts), I looked at the “unfixed” CVEs from this kernel release. Currently it is a list 983 CVEs long, too long to list here.
Linux 4.9 reached end-of-life January 2023. Vero V was released in November 2023.
Can you say which newer kernel you are working on? And provide an ETA when it will be available?
Thanks for your work on OSMC/Vero. I’m pretty happy otherwise. But this is a blocker for me.
Hi Sam,
After update all of my movies doesn’t work correctly. they are playing but in mega slow motion. They are constantly buffering. HDR and Dolby vision doesn’t trigger 
It is unwatchable anymore
I don’t know what to do
EDIT: I Installed once more by ssh by command sudo apt-get dist-upgrade and now it is ok.
EDIT2: CEC (LG B2) stopped working I will test it more and give feedback
Best regards
As mentioned before, it is still supported and maintained by OSMC downstream.
The next planned kernel is 5.15.
Try power everything down at the mains for five minutes then resume.
Sam
Thx Sam. Now everything is working great
I don’t understand. The upstream developers said that Linux 4.9 is end-of-life, it has bugs and security vulnerabilities and it should not be used any more.
What does this mean? Did OSMC take over maintainance for the entire Linux 4.9 code, fix bugs and vulnerabilities, and effectively provide long-term-support after the Linux maintainers stoped providing long-term-support? I find that hard to believe.
Could you point me to your repository of the kernel that you are “supporting and maintaining”?
I look forward to seeing 5.15 (or any other officially supported kernel) on Vero.
Yes, there is a repository at GitHub - osmc/vero3-linux.
We have always maintained the kernel in a downstream kernel for OSMC, regardless of device. 100% Upstream support isn’t practical, even on other ARM devices or you won’t get feature parity.
There are some patches upstreamed to support mainline support but you won’t get feature parity in terms of media playback
Similar way to how Red Hat will support kernels that may be considered traditionally EOL.
Sam
Thanks for the link. The kernel in that repo is version 3.14.29. It was released in Jan 2015. 3.14 has been end-of-life since Sep 2016. It has 2.277 open CVEs.
I reached out Linux kernel developer Greg Kroah-Hartman, who maintained and released all these kernels. He sais, maintaining old kernels is “a very hard thing to do properly”. He adds:
I see right now:
Total Vulnerable CVE's in 4.9.337 : 2375and that was the last 4.9 release.
I doubt they have fixed that many CVEs in their repo since a huge majority of them showed up after 2020.
I’m not sure where he got that number. CVE Details lists 3.745 open CVEs for Linux 4.9.337.
Can you link to commits fixing CVEs after upstream declared it end-of-life?
If your most important criteria is a CVE free kernel, you should install Linux and run Kodi on that. You won’t get all the features OSMC includes (like Dolby Vision support), but it’ll meet your apparent number one criteria. I personally treat my Vero V as an appliance and don’t expose it to the internet. If someone gets on my internal network, I have a load of other problems to deal with before worrying about whether someone can hack my media player.
You are looking at the wrong branch. We moved away from 3.14 years ago. I believe we have had this discussion before.
This is the most realistic and largest attack surface (physical access or accidental port forward).
Whereas I totally agree with previous commenter about Vero being an appliance and not exactly the biggest threat at home, I find your opaqueness, or should I say gaslighting somewhat annoying. You posted a link to obsolete repo. With all due respect you really should post the link to current branch and answer the legitimate questions in true open source spirit.
And no, I don’t mean the repo that responds with “This repository is empty.”
The latest source code is under Tags Tags · osmc/vero3-linux · GitHub
What is the correct branch? This one has Linux 4.9.269, which is the one OSMC/Vero currently runs. But the branch has only a single commit. The repo does have some tags, but they don’t explain any changes.
It would be okay to say: “We use an EOL kernel, which is unsupported by upstream. We don’t fix CVEs. Our threat model does not cover internet reachability or kernel bugs.” I get the feeling this might be what you’re doing.
But it’s not what you are saying. You say, you are “supporting and maintaining” Linux 4.9. I would like to know what that means. So I can assess my threat level.
Although I am quite security minded, I asked these questions before as well, do you ask these questions to every product owner of the devices you have or want in your network(s)?
Think about all your network devices, smart appliances, avr, nas and your devices you physically use daily, like your tablet, phone and computer.
I long gave up on this and segment my network accordingly, so the devices can only get access to devices they need.
Getting an update notice on my 4k+
Is this also still for that device? It still works for what it needs to do. Will replace it when it dies on me.