Debian LightDM Repair: Keep the Release Branch and the Desktop Session in View
LightDM sits at an awkward point in desktop maintenance. The login manager needs Debian’s new security repair, yet restarting it can take somebody’s working session down with it. Save the work first. Debian published the advisory on November 16; the repair belongs in the next planned update, with the interruption made clear to the person at the keyboard.
The flaw, CVE-2026-129246, lives in a Debian-specific patch. It gives a malicious process running under the greeter’s lightdm identity a route through a writable directory. The root service can be induced to alter file permissions and ownership. Nothing about the visible login screen establishes whether the vulnerable code is still there.
The package number has a Debian ending
For a trixie machine, look for 1.32.0-6+deb13u1. A bookworm machine has a different fixed build: 1.26.0-8+deb12u1. Debian’s advisory supplies the trixie version and its security tracker records both branches. There is no need to replace bookworm with trixie merely to get the larger upstream number.
That trailing Debian revision is doing real work. Trixie’s 1.32.0-6 is marked vulnerable in the tracker. Both it and the repaired build begin with 1.32.0, so a shortened version check misses the change.
Use apt-cache policy lightdm to see the package state. Installed tells you what is on disk. Candidate is a proposal from APT. If those lines differ, do not mistake the available repair for an installed one. Refresh the package information and apply the update through the normal Debian security repositories. A candidate that remains too old calls for a look at the release’s security repository, holds and pinning, rather than another unchanged upgrade run.
Whose login manager is it?
There is one more question before the restart: is LightDM actually the display manager in use? The command systemctl status display-manager answers that. A desktop change can leave an old package installed, and its presence alone does not identify the service handling the current graphical login.
Once the appropriate package is installed and the open work is saved, arrange a reboot. Restarting the display manager directly can terminate the graphical sessions it manages. An unexpected return to the greeter is a particularly unhelpful way for a user to discover that maintenance has begun.
Back at the desktop, check the installed revision and active service again. As with Debian’s OpenEXR library update, package state and the software using that package are separate things to establish. Here that distinction has a human consequence as well: the person’s unsaved work.
Your Best Solution to all Linux Based Problems