Debian GNU/Linux · Boot & system hardening

Protect symbolic links in world-writable sticky directories

When it fails: Symbolic links in shared temporary directories are followed for any user. An attacker can plant a symlink in /tmp and make a privileged program overwrite an arbitrary file.

CB-DEB-BOOT-006mediumdraftautomatedautomated fixprofile core

Status draft: not part of any release yet, may still change.

Description

With fs.protected_symlinks = 1, the kernel only follows a symbolic link located in a world-writable sticky directory (such as /tmp) when the process following it owns the link, or when the link owner also owns the directory.

Debian enables it by default: through /usr/lib/sysctl.d/99-protect-links.conf (procps) on Debian 12, and through /usr/lib/sysctl.d/50-default.conf (linux-sysctl-defaults) on Debian 13.

Rationale

A classic attack plants a symbolic link in /tmp with the name a privileged program is about to create, pointing to a sensitive file. When the program writes "its" file, it overwrites the target instead. This setting blocks the whole class of time-of-check to time-of-use races based on symlinks in shared directories.

Impact

None known for normal use. Programs that rely on following other users' symlinks in /tmp are rare and already unsafe.

Setting

Locationsysctl `fs.protected_symlinks`, persisted in `/etc/sysctl.d/`
Default1
Recommended1

Audit

Run sysctl fs.protected_symlinks. The value must be 1. Then check that no sysctl configuration file sets it to 0.

Automated: every check must pass. Scanners report each check by its id.

running

Running value of fs.protected_symlinks.

key: fs.protected_symlinks
value: 1

Remediation

Create /etc/sysctl.d/60-cirsec.conf containing fs.protected_symlinks = 1, remove any other assignment of this key, then run sysctl --system.

Restartnone
Disruptionnone

Rollback

Remove the line from /etc/sysctl.d/60-cirsec.conf and run sysctl --system.

set

Generated from check running: the engine writes the fix for every output, it sets the expected value and the check runs again after.

Each release turns these fixes into remediate.sh and an Ansible role per profile: dry run by default, a fix runs only when its check fails.

References

Mappings

FrameworkIDRelationNote
ANSSI-BP-028 - Recommandations de configuration d'un système GNU/Linux2.0R14partialR14 lists several filesystem settings; this control covers fs.protected_symlinks.
NIST SP 800-53 Rev. 55.1.1AC-6related

How this control relates to the other framework's: equivalent, stricter, looser, partial or related.

Threats mitigated

People and lifecycle

Authors
Verified2026-10-18 by Sn0wAlice on 12, Proxmox VM, Debian 12 genericcloud image, kernel 6.1.0-54-cloud-amd64. Generated check, fix and check again for profiles core and server-hardened; values kept after reboot; fix idempotent.
Verified2026-10-18 by Sn0wAlice on 13, Proxmox VM, Debian 13 genericcloud image, kernel 6.12.113+deb13-cloud-amd64. Generated check, fix and check again for profiles core and server-hardened; values kept after reboot; fix idempotent.
Introduced inv0.1.0
Created, updated2026-10-18, 2026-10-18
Translationsfr