{
  "slug": "sticky-bit",
  "term": "Sticky bit",
  "aliases": [
    "directory sticky bit",
    "restricted deletion flag"
  ],
  "definition": "The sticky bit on a Linux directory limits entry removal and renaming to the file owner, directory owner or a suitably privileged process.",
  "note": "Directory rule: S_ISVTX is octal 01000. It adds an ownership check when removing or renaming entries; it does not replace directory write and pathname search checks. CAP_FOWNER can bypass the sticky check, but passing that check alone does not authorize the operation. [sticky-inode] [sticky-unlink] [sticky-capabilities]\n\nRename: The source entry is checked against its parent directory. Replacing an existing destination also requires satisfying that destination's sticky restriction. Owning the source file does not by itself authorize replacing another owner's destination. [sticky-rename]\n\nPayload: The bit is not a general read-only flag for contained files. File-content access is separate from permission to remove a name. Linux protected_regular and protected_fifos settings add conditional restrictions on O_CREAT opens of existing objects in writable sticky directories; these are separate policies, not the sticky rule alone. [sticky-inode] [sticky-hardening]\n\nRecovery: Matching file bytes and ordinary rwx permissions does not establish an equivalent directory-entry policy. Directory mode, directory ownership and target ownership also matter; read-only filesystems and immutable flags can independently prevent removal. [sticky-unlink]",
  "advantages": [],
  "limitations": [
    "The described ownership rule is Linux-scoped; it is not a complete cross-platform authorization model."
  ],
  "related": [
    "directory",
    "unlink",
    "posix-access-control-list"
  ],
  "status": "shipping",
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-15",
  "citations": [
    {
      "id": "sticky-inode",
      "title": "Linux man-pages: inode(7), S_ISVTX and directory mode",
      "url": "https://man7.org/linux/man-pages/man7/inode.7.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "sticky-unlink",
      "title": "Linux man-pages: unlink(2), directory access and sticky restrictions",
      "url": "https://man7.org/linux/man-pages/man2/unlink.2.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "sticky-rename",
      "title": "Linux man-pages: rename(2), source and destination restrictions",
      "url": "https://man7.org/linux/man-pages/man2/rename.2.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "sticky-capabilities",
      "title": "Linux man-pages: capabilities(7), CAP_FOWNER versus access overrides",
      "url": "https://man7.org/linux/man-pages/man7/capabilities.7.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "sticky-hardening",
      "title": "Linux kernel documentation: protected_regular and protected_fifos",
      "url": "https://www.kernel.org/doc/html/latest/admin-guide/sysctl/fs.html",
      "accessed": "2026-11-15"
    }
  ],
  "provenance": [
    "Primary-source synthesis of Linux directory semantics, not a new permission experiment or a claim about historical sticky-bit uses on executable files.",
    "Recovery guidance is an engineering inference from the documented checks, not a measured backup outcome.",
    "Human context: https://hesela.com/analyses/posix-acl-restore-permissions/#sticky-directory"
  ]
}
