FKIE_CVE-2025-68736

Vulnerability from fkie_nvd - Published: 2025-12-24 13:16 - Updated: 2026-10-16 15:16
Severity
8.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: landlock: Fix handling of disconnected directories Disconnected files or directories can appear when they are visible and opened from a bind mount, but have been renamed or moved from the source of the bind mount in a way that makes them inaccessible from the mount point (i.e. out of scope). Previously, access rights tied to files or directories opened through a disconnected directory were collected by walking the related hierarchy down to the root of the filesystem, without taking into account the mount point because it couldn't be found. This could lead to inconsistent access results, potential access right widening, and hard-to-debug renames, especially since such paths cannot be printed. For a sandboxed task to create a disconnected directory, it needs to have write access (i.e. FS_MAKE_REG, FS_REMOVE_FILE, and FS_REFER) to the underlying source of the bind mount, and read access to the related mount point. Because a sandboxed task cannot acquire more access rights than those defined by its Landlock domain, this could lead to inconsistent access rights due to missing permissions that should be inherited from the mount point hierarchy, while inheriting permissions from the filesystem hierarchy hidden by this mount point instead. Landlock now handles files and directories opened from disconnected directories by taking into account the filesystem hierarchy when the mount point is not found in the hierarchy walk, and also always taking into account the mount point from which these disconnected directories were opened. This ensures that a rename is not allowed if it would widen access rights [1]. The rationale is that, even if disconnected hierarchies might not be visible or accessible to a sandboxed task, relying on the collected access rights from them improves the guarantee that access rights will not be widened during a rename because of the access right comparison between the source and the destination (see LANDLOCK_ACCESS_FS_REFER). It may look like this would grant more access on disconnected files and directories, but the security policies are always enforced for all the evaluated hierarchies. This new behavior should be less surprising to users and safer from an access control perspective. Remove a wrong WARN_ON_ONCE() canary in collect_domain_accesses() and fix the related comment. Because opened files have their access rights stored in the related file security properties, there is no impact for disconnected or unlinked files.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/426d5b681b2f3339ff04da39b81d71176dc8c87c
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/49c9e09d961025b22e61ef9ad56aa1c21b6ce2f1
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/4f5cdc82a6c7e22cfd9a92d203cec13a52a3f363
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/cadb28f8b3fd6908e3051e86158c65c3a8e1c907
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/fbf718d5afe21057694a0c0223a18b0c7a5960b6
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "security/landlock/errata/abi-1.h",
            "security/landlock/fs.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4f5cdc82a6c7e22cfd9a92d203cec13a52a3f363",
              "status": "affected",
              "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d",
              "versionType": "git"
            },
            {
              "lessThan": "fbf718d5afe21057694a0c0223a18b0c7a5960b6",
              "status": "affected",
              "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d",
              "versionType": "git"
            },
            {
              "lessThan": "426d5b681b2f3339ff04da39b81d71176dc8c87c",
              "status": "affected",
              "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d",
              "versionType": "git"
            },
            {
              "lessThan": "cadb28f8b3fd6908e3051e86158c65c3a8e1c907",
              "status": "affected",
              "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d",
              "versionType": "git"
            },
            {
              "lessThan": "49c9e09d961025b22e61ef9ad56aa1c21b6ce2f1",
              "status": "affected",
              "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "security/landlock/errata/abi-1.h",
            "security/landlock/fs.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.13"
            },
            {
              "lessThan": "5.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.189",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.143",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.80",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nlandlock: Fix handling of disconnected directories\n\nDisconnected files or directories can appear when they are visible and\nopened from a bind mount, but have been renamed or moved from the source\nof the bind mount in a way that makes them inaccessible from the mount\npoint (i.e. out of scope).\n\nPreviously, access rights tied to files or directories opened through a\ndisconnected directory were collected by walking the related hierarchy\ndown to the root of the filesystem, without taking into account the\nmount point because it couldn\u0027t be found. This could lead to\ninconsistent access results, potential access right widening, and\nhard-to-debug renames, especially since such paths cannot be printed.\n\nFor a sandboxed task to create a disconnected directory, it needs to\nhave write access (i.e. FS_MAKE_REG, FS_REMOVE_FILE, and FS_REFER) to\nthe underlying source of the bind mount, and read access to the related\nmount point.   Because a sandboxed task cannot acquire more access\nrights than those defined by its Landlock domain, this could lead to\ninconsistent access rights due to missing permissions that should be\ninherited from the mount point hierarchy, while inheriting permissions\nfrom the filesystem hierarchy hidden by this mount point instead.\n\nLandlock now handles files and directories opened from disconnected\ndirectories by taking into account the filesystem hierarchy when the\nmount point is not found in the hierarchy walk, and also always taking\ninto account the mount point from which these disconnected directories\nwere opened.  This ensures that a rename is not allowed if it would\nwiden access rights [1].\n\nThe rationale is that, even if disconnected hierarchies might not be\nvisible or accessible to a sandboxed task, relying on the collected\naccess rights from them improves the guarantee that access rights will\nnot be widened during a rename because of the access right comparison\nbetween the source and the destination (see LANDLOCK_ACCESS_FS_REFER).\nIt may look like this would grant more access on disconnected files and\ndirectories, but the security policies are always enforced for all the\nevaluated hierarchies.  This new behavior should be less surprising to\nusers and safer from an access control perspective.\n\nRemove a wrong WARN_ON_ONCE() canary in collect_domain_accesses() and\nfix the related comment.\n\nBecause opened files have their access rights stored in the related file\nsecurity properties, there is no impact for disconnected or unlinked\nfiles."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nlandlock: Correcci\u00f3n del manejo de directorios desconectados\n\nArchivos o directorios desconectados pueden aparecer cuando son visibles y se abren desde un montaje de enlace, pero han sido renombrados o movidos desde el origen del montaje de enlace de una manera que los hace inaccesibles desde el punto de montaje (es decir, fuera de alcance).\n\nAnteriormente, los derechos de acceso vinculados a archivos o directorios abiertos a trav\u00e9s de un directorio desconectado se recopilaban recorriendo la jerarqu\u00eda relacionada hasta la ra\u00edz del sistema de archivos, sin tener en cuenta el punto de montaje porque no se pod\u00eda encontrar. Esto podr\u00eda llevar a resultados de acceso inconsistentes, una posible ampliaci\u00f3n de los derechos de acceso y renombramientos dif\u00edciles de depurar, especialmente porque tales rutas no pueden imprimirse.\n\nPara que una tarea en sandbox cree un directorio desconectado, necesita tener acceso de escritura (es decir, FS_MAKE_REG, FS_REMOVE_FILE y FS_REFER) al origen subyacente del montaje de enlace, y acceso de lectura al punto de montaje relacionado. Debido a que una tarea en sandbox no puede adquirir m\u00e1s derechos de acceso que los definidos por su dominio Landlock, esto podr\u00eda llevar a derechos de acceso inconsistentes debido a permisos faltantes que deber\u00edan heredarse de la jerarqu\u00eda del punto de montaje, mientras que, en su lugar, hereda permisos de la jerarqu\u00eda del sistema de archivos oculta por este punto de montaje.\n\nLandlock ahora maneja archivos y directorios abiertos desde directorios desconectados teniendo en cuenta la jerarqu\u00eda del sistema de archivos cuando el punto de montaje no se encuentra en el recorrido de la jerarqu\u00eda, y tambi\u00e9n siempre teniendo en cuenta el punto de montaje desde el cual se abrieron estos directorios desconectados. Esto asegura que no se permite un renombramiento si ampliara los derechos de acceso [1].\n\nLa raz\u00f3n es que, incluso si las jerarqu\u00edas desconectadas podr\u00edan no ser visibles o accesibles para una tarea en sandbox, confiar en los derechos de acceso recopilados de ellas mejora la garant\u00eda de que los derechos de acceso no se ampliar\u00e1n durante un renombramiento debido a la comparaci\u00f3n de derechos de acceso entre el origen y el destino (ver LANDLOCK_ACCESS_FS_REFER). Podr\u00eda parecer que esto otorgar\u00eda m\u00e1s acceso a archivos y directorios desconectados, pero las pol\u00edticas de seguridad siempre se aplican para todas las jerarqu\u00edas evaluadas. Este nuevo comportamiento deber\u00eda ser menos sorprendente para los usuarios y m\u00e1s seguro desde una perspectiva de control de acceso.\n\nEliminar un canary WARN_ON_ONCE() incorrecto en collect_domain_accesses() y corregir el comentario relacionado.\n\nDebido a que los archivos abiertos tienen sus derechos de acceso almacenados en las propiedades de seguridad de archivo relacionadas, no hay impacto para archivos desconectados o desvinculados."
    }
  ],
  "id": "CVE-2025-68736",
  "lastModified": "2026-10-16T15:16:52.470",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 8.8,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.0,
        "impactScore": 6.0,
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-68736",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-10-16T15:04:56.596972Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2025-12-24T13:16:28.550",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/426d5b681b2f3339ff04da39b81d71176dc8c87c"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/49c9e09d961025b22e61ef9ad56aa1c21b6ce2f1"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/4f5cdc82a6c7e22cfd9a92d203cec13a52a3f363"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/cadb28f8b3fd6908e3051e86158c65c3a8e1c907"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/fbf718d5afe21057694a0c0223a18b0c7a5960b6"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Deferred"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.