« Volver al listado

CVE-2026-72368

Estado: RecibidaAlta (7.8)—

In the Linux kernel, the following vulnerability has been resolved:

cachefiles: Fix double unlock in nomem_d_alloc error path

When start_creating() fails and returns -ENOMEM, it has already released the parent directory lock in __start_dirop():

However, the nomem_d_alloc error path in cachefiles_get_directory() unconditionally calls inode_unlock(d_inode(dir)) again, causing a double unlock that corrupts the rwsem state.

This is a leftover from commit 7ab96df840e60 which replaced manual locking with start_creating() but failed to update the nomem_d_alloc path (while correctly updating mkdir_error and lookup_error paths).

Detalles técnicos trazas, registros y código del informe original
    static struct dentry *__start_dirop(...)
    {
        ...
        inode_lock_nested(dir, I_MUTEX_PARENT);
        dentry = lookup_one_qstr_excl(name, parent, lookup_flags);
        if (IS_ERR(dentry))
            inode_unlock(dir);  <-- Lock released on error
        return dentry;
    }

CVSS

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

Acceso local sin interacción del usuario (AV:L, UI:N, PR:L) permite a un usuario local con privilegios menores causar corrupción de estado del kernel mediante double unlock, resultando en denegación de servicio o corrupción de datos del sistema de ficheros.

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Threat Intelligence ProgramRestrict File and Directory PermissionsRemote Data StorageFilter Network TrafficExecution PreventionEncrypt Sensitive Information

Tecnologías afectadas (1)

⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.

Linux — Linux KernelAI

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2026-72368",
  "cveTags": [],
  "metrics": {
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.8,
          "attackVector": "LOCAL",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 1.8
      }
    ]
  },
  "affected": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "affectedData": [
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7ab96df840e60eb933abfe65fc5fe44e72f16dc0",
              "lessThan": "26757dac15175f2a42e3537f1ba86e62456d48f1",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "7ab96df840e60eb933abfe65fc5fe44e72f16dc0",
              "lessThan": "8c256fba2b46020004201c500b2a1fbc707a33ef",
              "versionType": "git"
            }
          ],
          "programFiles": [
            "fs/cachefiles/namei.c"
          ],
          "defaultStatus": "unaffected"
        },
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.19"
            },
            {
              "status": "unaffected",
              "version": "0",
              "lessThan": "6.19",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver",
              "lessThanOrEqual": "7.1.*"
            },
            {
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix",
              "lessThanOrEqual": "*"
            }
          ],
          "programFiles": [
            "fs/cachefiles/namei.c"
          ],
          "defaultStatus": "affected"
        }
      ]
    }
  ],
  "published": "2026-08-15T06:22:10.227",
  "references": [
    {
      "url": "https://git.kernel.org/stable/c/26757dac15175f2a42e3537f1ba86e62456d48f1",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/8c256fba2b46020004201c500b2a1fbc707a33ef",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "vulnStatus": "Received",
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncachefiles: Fix double unlock in nomem_d_alloc error path\n\nWhen start_creating() fails and returns -ENOMEM, it has already\nreleased the parent directory lock in __start_dirop():\n\n    static struct dentry *__start_dirop(...)\n    {\n        ...\n        inode_lock_nested(dir, I_MUTEX_PARENT);\n        dentry = lookup_one_qstr_excl(name, parent, lookup_flags);\n        if (IS_ERR(dentry))\n            inode_unlock(dir);  <-- Lock released on error\n        return dentry;\n    }\n\nHowever, the nomem_d_alloc error path in cachefiles_get_directory()\nunconditionally calls inode_unlock(d_inode(dir)) again, causing a\ndouble unlock that corrupts the rwsem state.\n\nThis is a leftover from commit 7ab96df840e60 which replaced manual\nlocking with start_creating() but failed to update the nomem_d_alloc\npath (while correctly updating mkdir_error and lookup_error paths)."
    }
  ],
  "lastModified": "2026-08-17T06:18:41.010",
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}