blob: 315ea7e0fe5049c0ae67a020de7a4bc5c24ebb2d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
/* 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)
/**
* DOC: erratum_4
*
* Erratum 4: Creation of whiteout objects
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*
* This fix changes the access rights required for the creation of whiteout
* objects through :manpage:`mknod(2)`, :manpage:`renameat2(2)`, or
* :manpage:`link(2)`. Creating whiteout objects is now guarded by
* ``LANDLOCK_ACCESS_FS_MAKE_REG`` instead of ``LANDLOCK_ACCESS_FS_MAKE_CHAR``.
*
* Whiteout objects are used in OverlayFS to mark the absence of a file in an
* upper file system. Despite being created with ``S_IFCHR``, whiteout objects
* do not count as character devices.
*
* Impact:
*
* Sandboxed programs that create OverlayFS whiteouts (such as fuse-overlayfs)
* now require ``LANDLOCK_ACCESS_FS_MAKE_REG`` instead of
* ``LANDLOCK_ACCESS_FS_MAKE_CHAR``.
*/
LANDLOCK_ERRATUM(4)
|
