Not sure why this is saying it isn’t patched, they released the notice including fix for 14.4 yesterday?
irishcoffee•May 21, 2026
Maybe they're not up to snuff on yesterday? They published this yesterday.
> The bug was silently fixed in the main branch on 2025-11-27 (commit 000d5b52c19ff3858a6f0cbb405d47713c4267a4) as a side effect of a broader function refactoring. The fix has not been backported to stable/14 or releng/14.4. FreeBSD 14.4-RELEASE remains vulnerable.
> FreeBSD 15.0 still carries the sizeof(*groups) typo and is therefore vulnerable, but the surrounding code differs enough from 14.4 that the chain primitives developed here do not lift the overflow into a working LPE on that branch. On 15.0 the bug remains a kernel panic triggered by any unprivileged user.
turkeyboi•May 21, 2026
Why does this need to be a whole ass website
dragontamer•May 21, 2026
What?
Is there something in this website that feels unnecessary? It seems like a good format of sharing high quality information.
This looks like a full bug into a complete root escalation of a kernel. That's hard to do and deserving of praise. The fact that we have a writeup organized like this is awesome.
-------
This is sort of the expert level stuff that I thought HackerNews would most enjoy.
cryo32•May 21, 2026
You're not going to get anywhere in the security sector unless you gain notoriety i.e. are noticed.
This appears to come from dressing up like Elton John in a feather suit and hiring a marketing team.
tptacek•May 21, 2026
It's a wall of text about a kernel stack overflow. I'm not sure where the "Elton John" part is. Is it... that they used an accent color?
866-RON-0-FEZ•May 21, 2026
Maybe the researcher was wearing windshield-wiper spectacles when he discovered the vulnerability.
I don't understand why you're being so defensive about this.
tptacek•May 21, 2026
Because it's a tiresome, tropey, and ultimately invalid complaint. Look downthread at the person who said the FreeBSD commit log was better than this page, despite being inscrutable to security practitioners who don't work in the kernel and not saying a word about proven exploit vectors.
These complaints aren't about what's better or worse for the user community; they're about people trying to put vulnerability researchers in their place.
866-RON-0-FEZ•May 21, 2026
While I believe whimsical names will always be silly, I do concede that commit log is effectively useless to 99% of eyeballs.
tptacek•May 21, 2026
It's not even a complete description of the vulnerability. It's what the kernel maintainers need to know to understand and fix the bug in the code. The claim that it's superior to the branded vulnerability page gives away the whole game.
GoblinSlayer•May 21, 2026
Buffer overflow.
tptacek•May 21, 2026
Why not? This weird complaint has been happening since ~2010 and it has never made any sense. You are strictly better off with the website than without it. When it was vulnerability researchers getting all peevish about the status competition they were running, I at least understood where the complaint was coming from, but even among practitioners, branded vulnerabilities are so much the norm at this point that there's no status implication anymore.
themafia•May 21, 2026
> You are strictly better off with the website than without it.
It details the actual problem instead of showing off tired stack exploit tricks.
tptacek•May 21, 2026
No, that commit log is obviously not better than the page explaining the vulnerability and the exploit vectors.
Case in point: what's "tired" about the stack exploitation techniques they're using here?
And, while you're not right, even stipulating that you were, what would that matter? How is anyone better off with less explanation of a vulnerability?
themafia•May 21, 2026
The website explains an exploit. I've seen exploits before. The commit explains the unique issue.
I'm more interested in the why than the how.
I suppose people with different overall goals will see that differently.
tptacek•May 21, 2026
You didn't answer my question. What's "tired" about the exploit technique here?
tom_•May 21, 2026
Is that even the fix though? The problem sizeof*groups expression has already been removed by that point. This fixes something but it's not obviously related to the vulnerability description.
Have you not done anything remotely interesting for you that you want to build a website so the whole world can see it?
866-RON-0-FEZ•May 21, 2026
It gives legitimacy to whatever whimsical name was given to a vulnerability by registering the domain.
CVE numbers are for boring professionals.
elkrapo•May 21, 2026
The cool kiddies wait and time their disclosures on the cool numbers.
djha-skin•May 21, 2026
TrueNAS is on FreeBSD, as well as lots of network equipment. This does affect us more than we think as operators.
ActionHank•May 21, 2026
Possibly Playstation as well.
sbankowi•May 21, 2026
Also Netgate's devices running PFSense.
anygivnthursday•May 21, 2026
And OPNSense boxes
loeg•May 21, 2026
PlayStation 4 was a fork of FreeBSD 9, and is immune to this bug introduced in 14. Sony also changes a LOT, I'm not sure anything dealing with unix credentials even exists in this fork. It's not clear how much FreeBSD is even used in PlayStation 5 (2020), but it would be based off 12 or earlier (also immune to this bug from 14) (13 was released in 2021).
yjftsjthsd-h•May 21, 2026
I would think that pure-storage NAS or network equipment
was effectively completely immune to local privilege escalation. I'll give you the NAS where it might be running untrusted containers or such, but that's it.
1over137•May 21, 2026
Alas, TrueNAS actually switched to Linux a couple of years ago.
sbankowi•May 21, 2026
FreeBSD was the reason I chose TrueNAS Core. Unfortunately, you are right, TrueNAS Scale (Linux) is where they are focusing all their attention.
At this point I will not purchase additional TrueNAS equipment as I feel I was "rug pulled." I get that they are going after more of the Docker container/app market, but I just want a solid ZFS w/excellent networking NAS device. Linux is close to this ideal, but it isn't as "Set and Forget" as FreeBSD (IMO).
BadBadJellyBean•May 21, 2026
You usually don't really interact with the OS underneath at all so I don't think it makes much of a difference unless you are very fond of Jails.
I mean that is the whole point of a NAS OS. It gives you a GUI and you don't have to worry about the rest.
866-RON-0-FEZ•May 21, 2026
Juniper JunOS is based on FreeBSD IIRC.
sophacles•May 21, 2026
They've been moving their NOSes to a linux based platform.
doublerabbit•May 21, 2026
TrueNAS was, but they now use Linux as the main distribution.
badgersnake•May 21, 2026
LPEs are really not impressive enough to warrant names and websites.
4 Comments
> The bug was silently fixed in the main branch on 2025-11-27 (commit 000d5b52c19ff3858a6f0cbb405d47713c4267a4) as a side effect of a broader function refactoring. The fix has not been backported to stable/14 or releng/14.4. FreeBSD 14.4-RELEASE remains vulnerable.
> FreeBSD 15.0 still carries the sizeof(*groups) typo and is therefore vulnerable, but the surrounding code differs enough from 14.4 that the chain primitives developed here do not lift the overflow into a working LPE on that branch. On 15.0 the bug remains a kernel panic triggered by any unprivileged user.
Is there something in this website that feels unnecessary? It seems like a good format of sharing high quality information.
This looks like a full bug into a complete root escalation of a kernel. That's hard to do and deserving of praise. The fact that we have a writeup organized like this is awesome.
-------
This is sort of the expert level stuff that I thought HackerNews would most enjoy.
This appears to come from dressing up like Elton John in a feather suit and hiring a marketing team.
I don't understand why you're being so defensive about this.
These complaints aren't about what's better or worse for the user community; they're about people trying to put vulnerability researchers in their place.
Why? This is a better resource in every way: https://cgit.freebsd.org/src/commit/?id=000d5b52c19ff3858a6f...
It details the actual problem instead of showing off tired stack exploit tricks.
Case in point: what's "tired" about the stack exploitation techniques they're using here?
And, while you're not right, even stipulating that you were, what would that matter? How is anyone better off with less explanation of a vulnerability?
I'm more interested in the why than the how.
I suppose people with different overall goals will see that differently.
git log -S suggests 4cd93df95e697942adf0ff038fc8f357cbb07cf9, which looks more likely: https://cgit.freebsd.org/src/commit/?id=4cd93df95e697942adf0... - though not to say you don't want the later commit too. I'm sure you do.
CVE numbers are for boring professionals.
I mean that is the whole point of a NAS OS. It gives you a GUI and you don't have to worry about the rest.