
Canonical published Ubuntu Security Notice USN-9151-1 on November 18, 2026 (07:33:31 UTC), disclosing and patching a local privilege escalation vulnerability tracked as CVE-2026-124757 in the needrestart package. Security researcher Armaan Sandhu discovered that the utility did not properly handle systemd cgroup paths and process names, creating a flaw that could allow a local attacker to run programs as an administrator.
Because needrestart checks which system daemons need to be restarted after library upgrades, the patch spans seven Ubuntu releases: 26.10, 26.04 LTS, 24.04 LTS, 22.04 LTS, 20.04 LTS, 18.04 LTS, and 16.04 LTS. Standard updates resolve the issue on active interim and recent Long Term Support distributions, while older LTS branches receive fixes through Ubuntu Pro ESM channels.
Core announcement and operational scope
USN-9151-1 addresses a privilege boundary failure in how needrestart inspects running services on Ubuntu hosts. In standard Linux administration, package management workflows invoke needrestart with administrative privileges after shared libraries are upgraded so it can examine active processes and identify daemons still referencing older library files in memory.
When an unprivileged local user can influence process attributes that a privileged diagnostic tool later parses, improper validation turns routine system inspection into an escalation risk. According to Canonical's summary, the vulnerability could enable a local attacker to execute programs with administrator privileges. The notice confines the threat model to local access rather than remote network exploitation, making multi-user Linux servers, shared developer workstations, and build hosts the primary environments at risk.
Affected components, systemd integration, and patched versions
The advisory names needrestart as the single affected package and attributes the vulnerability to two specific implementation gaps identified by Armaan Sandhu: improper handling of systemd cgroup paths and improper handling of process names. Both mechanisms sit at the center of how needrestart correlates kernel process table entries with managed systemd service units following library updates.
Canonical published patched builds across seven Ubuntu releases, spanning multiple upstream version lineages from 2.6 through 3.11. System administrators should verify that upgraded hosts install at least the package versions specified in USN-9151-1:
- Ubuntu 26.10 (stonking):
needrestart3.11-1ubuntu2.26.10.1 - Ubuntu 26.04 LTS (resolute):
needrestart3.11-1ubuntu2.26.04.1 - Ubuntu 24.04 LTS (noble):
needrestart3.6-7ubuntu4.6 - Ubuntu 22.04 LTS (jammy):
needrestart3.5-5ubuntu2.6 - Ubuntu 20.04 LTS (focal):
needrestart3.4-6ubuntu0.1+esm4(Ubuntu Pro via ESM Apps) - Ubuntu 18.04 LTS (bionic):
needrestart3.1-1ubuntu0.1+esm4(Ubuntu Pro via ESM Apps) - Ubuntu 16.04 LTS (xenial):
needrestart2.6-1ubuntu0.1~esm4(ESM)
The advisory lists no additional affected packages, kernel dependencies, or hardware-specific restrictions. Canonical also states that in general, a standard system update will make all the necessary changes on configured machines.
Integration and developer workflow impact
For DevOps engineers, infrastructure maintainers, and Linux developers, deploying the fix requires minimal operational disruption because updating needrestart does not alter service unit configurations or mandate a full host reboot. Teams managing fleets across Ubuntu 22.04 LTS, 24.04 LTS, 26.04 LTS, and 26.10 can roll out the patched package through standard APT maintenance windows, golden-image rebuilds, and unattended-upgrade pipelines.
In software development and continuous integration environments, the incident serves as a reminder that post-upgrade daemon checkers operate across user-space boundaries where unprivileged accounts control their own process names. Organizations running shared build runners, testbeds, or multi-user research nodes should prioritize updating needrestart before scheduled library maintenance executes under elevated privileges. Where automated tooling parses restart advisories, administrators should confirm that package repositories are synced to pull the November 18, 2026 builds.
Deployment caveats, ESM limits, and disclosure boundaries
Operational rollout depends on each system's support tier and subscription status. While Ubuntu 26.10, 26.04 LTS, 24.04 LTS, and 22.04 LTS receive standard repository updates, Canonical explicitly notes that fixes for Ubuntu 20.04 LTS and Ubuntu 18.04 LTS are available with Ubuntu Pro via ESM Apps, adding that a community fix might become publicly available in the future. Ubuntu 16.04 LTS similarly ships an ~esm4 build tied to extended maintenance.
Canonical states that Ubuntu Pro provides ten-year security coverage across more than 25,000 packages in the Main and Universe repositories and is free for up to five machines, meaning larger unsubscribed deployments on legacy LTS releases will remain unpatched unless upgraded or enrolled. Finally, USN-9151-1 provides no CVSS score, proof-of-concept details, or performance metrics, and no independent testing was conducted for this report; administrators can track updates directly on the Ubuntu Security Notices page.
Automated Vertex AI (gemini-4-hydrogen) primary-source report; reviewed 2026-11-19.



