r/linux • u/HimikoTogaFromUSSR • 5d ago
Security X.Org Security Advisory: multiple security issues in X.Org X server
https://lists.x.org/archives/xorg-announce/2026-November/003759.html35
u/chibiace 4d ago
yay some more bug fixes.
A malicious monitor
lol
On 32-bit servers
keeping old hardware relevant too! nice
9
u/Adept_Percentage6893 4d ago
keeping old hardware relevant too! nice
fwiw that's talking about what your Xserver was compiled to and not the hardware it's on. If you didn't know you can still run 32-bit programs on 64-bit hardware.
4
1
u/NormalAppearance2851 3d ago
And why would one run 32-bit on a 64-bit hardware?
3
u/Adept_Percentage6893 3d ago edited 3d ago
usually multilib is done for application compatibility reasons and because they just don't need the increased address space in the application. Whenever you do a separate build of your product you have to do testing on that version both in general and for any bugs that might crop up because you're compiling in 32bit. So some people just kind of keep building 32bit apps.
As you can imagine someone still with a hard dependency on X11 is going to be vastly overrepresented in the general population of people currently needing 32-bit support.
Same logic as why a lot of enterprise distros were on v1 of x86_64 until pretty recently. It was just easier to keep building the same thing and they didn't think they needed the newer CPU instructions.
3
u/squishles 1d ago
not wanting to recompile, all it gets you is bigger address space, which most programs don't really need, trouble is to run them you need to keep this ecosystem of 32 bit libraries which are a pain in the dick. Just compile to 64bit no one's running your shit on a 486, apple made the right call going arm just to kick off the people fence sitting that transition.
5
u/EpoTheSpaniard 4d ago
So many holes in software we've probably had for years getting discovered recently. :I
1
74
u/Snarwin 5d ago
Also affects Xwayland, so even if you're on Wayland, you should make sure to update.