The problem with the Chinese SBCs is lack of up-to-date LINUX support. Chip manufacturers are eager to provide Android support, but don't care a great deal about Linux support, which is, for them, a tiny niche market. Android will run on significantly out of date kernels, so the chip makers typically bump their kernels to the minimum Linux kernel version required to run a reasonable modern Android. Their Linux ports are based on Android kernels, so they lag significantly behind. And SBC manufacturers just use the kernels provided by the chipset manufacturer. The recent Orange Pi Rockwell-based SBCs, for example, shipped with a 4.x Linux kernel for their Linux port, at a point in time where Raspberry Pi OS was using a 6.x kernel.
Raspberry Pis do lag too, but they have significantly newer kernels, and are supported directly by several mainline distros.
I've chased a number of alternatives to Raspberry Pi in the interval where Rockwell SBCs were beating the pants off Pi 4s, only to find that they were shipping 4.x Linux kernels. My particular application uses USB audio devices, which don't really work prior to extensive rewrites of the USB audio stack in the 5.15 kernel. Raspberry Pi OS kernels are 6.1 or better. And Ubuntu on raspberry PI has later kernels than that (not sure which currently). Versions of Linux prior to 5.15 supported very old USB Audio 1.0 devices, but not currently available USB Audio 1.1 devices.
I imagine you would run into significant problems with video drivers being out of date on non-Pi devices as well. Raspberry Pi had to do their own Vulkan port, which seemed to require significant development effort.
I don't think that's likely to change soon. Rockwell doesn't really have a strong incentive to improve their kernel ports beyond what's necessary to support Android. And smaller SBC manufacturers aren't likely to have the resources to do a kernel port themselves.
You're not wrong.. but I also somehow doubt this is a dealbreaker. The reality is that nobody typically really cares about the kernel version they're running. It just rarely comes to bite you (like in your example). There are often vague security implications - but they always feel mostly theoretical
Furthermore if the platform is popular enough the community starts to step in. You can even see in the comments section of the previous link:
Furthermore, b/c unlike Broadcom/Rpi chips, these chips are widely available for commercial use - I'm gunna guess 3rd party companies are more likely to dedicate resources to maintain the software stack (even if the chip manufacturer is doing a crappy job of it)
Raspberry Pis do lag too, but they have significantly newer kernels, and are supported directly by several mainline distros.
I've chased a number of alternatives to Raspberry Pi in the interval where Rockwell SBCs were beating the pants off Pi 4s, only to find that they were shipping 4.x Linux kernels. My particular application uses USB audio devices, which don't really work prior to extensive rewrites of the USB audio stack in the 5.15 kernel. Raspberry Pi OS kernels are 6.1 or better. And Ubuntu on raspberry PI has later kernels than that (not sure which currently). Versions of Linux prior to 5.15 supported very old USB Audio 1.0 devices, but not currently available USB Audio 1.1 devices.
I imagine you would run into significant problems with video drivers being out of date on non-Pi devices as well. Raspberry Pi had to do their own Vulkan port, which seemed to require significant development effort.
I don't think that's likely to change soon. Rockwell doesn't really have a strong incentive to improve their kernel ports beyond what's necessary to support Android. And smaller SBC manufacturers aren't likely to have the resources to do a kernel port themselves.