erratum_1(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

erratum_1 πŸ’…

okay so this is from the Kernel API Manual bestie, and it's literally titled Erratum 1: TCP socket identification β€” yes we're reading errata for fun now, that's the energy we're bringing πŸŽ€


✨ NAME ✨

erratum_1 β€” Erratum 1: TCP socket identification πŸ¦‹


🌸 DESCRIPTION 🌸

okay so picture this: there was this issue πŸ™ˆ where IPv4 and IPv6 stream sockets β€” you know, the ones like SMC, MPTCP, or SCTP β€” were getting incorrectly restricted by TCP access rights during bind(2) and connect(2) operations. like, not them being dragged into TCP's business?? 😭

This fix addresses that whole situation. It ensures that only TCP sockets are subject to TCP access rights, which lets all the other protocols operate without unnecessary restrictions. slay for them honestly πŸ‘‘

πŸ”₯ Impact πŸ”₯

so here's the part you actually need to know, no cap:

In kernels without this fix, using LANDLOCK_ACCESS_NET_BIND_TCP or LANDLOCK_ACCESS_NET_CONNECT_TCP would incorrectly restrict non-TCP stream protocols (SMC, MPTCP, SCTP), potentially breaking applications that rely on these protocols while using Landlock network restrictions. yeah. that's the whole vibe check and it did not pass πŸ’€


πŸ‘€ SEE ALSO πŸ‘€

  • Kernel file ./security/landlock/errata/abi-4.h β€” go read it, iykyk πŸ“–

and that's the tea, bestie πŸ“ this one's from ./security/landlock/errata, dated October 2026, and it's giving very much "tiny errata page, big main character energy" ✨ mwah, go forth and Landlock responsibly πŸ’œ

πŸ“¦ where this page comes from