erratum_3(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ erratum_3 ✨

okay so bestie, this is erratum_3(9) from the Kernel API Manual, and it's giving β€œimportant kernel erratum” energy β€” not me reading kernel docs for fun πŸ’…. Let's go, periodt πŸ’–

πŸŽ€ Erratum 3: Disconnected directory handling πŸŽ€

This fix is all about an issue with disconnected directories that occur when a directory is moved outside the scope of a bind mount. The change makes sure that evaluated access rights include both:

  • those from the disconnected file hierarchy down to its filesystem root, and
  • those from the related mount point hierarchy.

That combination is literally what prevents access right widening through rename or link actions β€” slay for not letting permissions glow up when they shouldn't πŸ”₯

πŸ’₯ Impact: πŸ’₯

Without this fix, it was possible to widen access rights through rename or link actions involving disconnected directories, potentially bypassing LANDLOCK_ACCESS_FS_REFER restrictions 😭. That could allow privilege escalation in complex mount scenarios where directories become disconnected from their original mount points. So yeah, this is not a cute little edge case β€” it's a real one, bestie 🫢

🌈 SEE ALSO 🌈

  • Kernel file ./security/landlock/errata/abi-1.h β€” and also erratum_4(9) for the next lore drop πŸ‘‘

okay that's the whole page, mwah πŸ’‹ β€” it comes from the source/path ./security/landlock/errata, dated October 2026, and this iconic page is erratum_3(9). bye bestie πŸ¦‹

πŸ“¦ where this page comes from