Fairphone 5 and earlier have end-of-life Linux kernel branches without security support. Those lag multiple years behind on providing full Android security updates. The 1-2 month delays for partial security backports is compared to the Android security bulletins and is actually a much longer delay compared to when the patches are made available to ship by OEMs.
And yes all the Linux side of things is still missing.
Linux does not mean glibc, systemd, Bash, GNU coreutils, Wayland/X11, Pulseaudio/Pipewire, etc. Android distributions are Linux distributions and are not missing what makes it Linux. The same goes for embedded and server Linux distributions without those components.
It is very much a real thing. You can build AOSP from sources and install it on a phone. Many Android devices run that (e.g. drone controllers).
> Is certainly much better than my Samsung flagship
Oh yeah, that's for sure. To share my experience, in terms of updates for me it has been GrapheneOS >>> Stock Android > /e/OS. I was running LineageOS/Cyanogen a decade ago but I don't remember and it was a different time anyway.
There are many vendors that are even worse than /e/OS in terms of updates. This is one of several reasons why Play Integrity is a farce, it has very little to do with security when vendors can be months late with critical vulnerabilities and still get to pass Play Integrity.
Basically anything that is not GrapheneOS, Pixel, or Samsung is in a deplorable state (Samsung not only rolls out security patches during the embargo period, they also do QPR2s).
Fairphone is 1-2 months behind the Android security bulletins which are themselves 2-4 months behind the security preview patches. Fairphone takes a year to port to a new OS version shortly after launch and then ends up taking increasingly more time.
Sure that might be enough for very basic hardware like your drone controller example but not a phone
What comes from AOSP goes into GrapheneOS, LineageOS and Certified Google Android. So obviously it makes sense to compare them.
It's just a low level technical building block nowadays and everybody is chosing the parts they want.
Comparing your OS to AOSP itself made sense in 2016, it doesn't anymore in 2026.
It make sense to compare the OS between each other, what you can actually install and use on the phone.
Assuming they share a big part of the security model, how would it "not make sense" to compare them? If AOSP is the baseline, saying that /e/OS is often weakening the security model and GrapheneOS is hardening it is a way to compare them. That makes complete sense to me.
Yes I would say that most of the security decisions are not baked into AOSP and every rom brings their own decisions.