Resguardo inicial

This commit is contained in:
lastdragon
2026-09-06 12:53:21 -06:00
parent 662efe3c2a
commit ad2088d178
94853 changed files with 43200404 additions and 0 deletions
@@ -0,0 +1,24 @@
/* SPDX-License-Identifier: GPL-2.0-only */
/**
* DOC: erratum_3
*
* Erratum 3: Disconnected directory handling
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*
* This fix addresses an issue with disconnected directories that occur when a
* directory is moved outside the scope of a bind mount. The change ensures
* 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. This prevents access right widening through rename or link
* actions.
*
* 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. This could allow privilege
* escalation in complex mount scenarios where directories become disconnected
* from their original mount points.
*/
LANDLOCK_ERRATUM(3)
@@ -0,0 +1,22 @@
/* SPDX-License-Identifier: GPL-2.0-only */
/**
* DOC: erratum_1
*
* Erratum 1: TCP socket identification
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*
* This fix addresses an issue where IPv4 and IPv6 stream sockets (e.g., SMC,
* MPTCP, or SCTP) were incorrectly restricted by TCP access rights during
* :manpage:`bind(2)` and :manpage:`connect(2)` operations. This change ensures
* that only TCP sockets are subject to TCP access rights, allowing other
* protocols to operate without unnecessary restrictions.
*
* Impact:
*
* 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.
*/
LANDLOCK_ERRATUM(1)
@@ -0,0 +1,29 @@
/* SPDX-License-Identifier: GPL-2.0-only */
/**
* DOC: erratum_2
*
* Erratum 2: Scoped signal handling
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*
* This fix addresses an issue where signal scoping was overly restrictive,
* preventing sandboxed threads from signaling other threads within the same
* process if they belonged to different domains. Because threads are not
* security boundaries, user space might assume that all threads within the same
* process can send signals between themselves (see :manpage:`nptl(7)` and
* :manpage:`libpsx(3)`). Consistent with :manpage:`ptrace(2)` behavior, direct
* interaction between threads of the same process should always be allowed.
* This change ensures that any thread is allowed to send signals to any other
* thread within the same process, regardless of their domain.
*
* Impact:
*
* This problem only manifests when the userspace process is itself using
* :manpage:`libpsx(3)` or an equivalent mechanism to enforce a Landlock policy
* on multiple already-running threads at once. Programs which enforce a
* Landlock policy at startup time and only then become multithreaded are not
* affected. Without this fix, signal scoping could break multi-threaded
* applications that expect threads within the same process to freely signal
* each other.
*/
LANDLOCK_ERRATUM(2)