{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "f77f281b61183a5c0b87e6a4d101c70bd32c1c79"
            },
            {
              "fixed": "10c13801ea38e4ced23c59052ce45acb07c5deda"
            },
            {
              "fixed": "c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "7.0.0"
            },
            {
              "fixed": "7.3.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99476.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfsverity: Set S_VERITY only after rollback is no longer possible\n\nCommit f77f281b6118 (\"fsverity: use a hashtable to find the\nfsverity_info\") changed the implementation of FS_IOC_ENABLE_VERITY to\nmake concurrent reads start going through fsverity verification slightly\nearlier than they did before.\n\nInstead of it happening when enable_verity() calls fsverity_set_info(),\nit now happens when -\u003eend_enable_verity() sets S_VERITY.\n\nHowever, ext4 and btrfs can roll back verity after they set S_VERITY,\ncausing a use-after-free.\n\nFix that by making ext4 and btrfs set S_VERITY only after rollback is no\nlonger possible.  On failure, don't roll back S_VERITY, but do roll back\nthe filesystem-specific verity flag.\n\nAlso update enable_verity() to handle any future instances of this bug\nmore safely by warning and *not* freeing the fsverity_info.\n\nFinally, tweak some comments.  Clarify one, and move information from\nanother to its proper place in the comment for -\u003eend_enable_verity().",
  "id": "CVE-2026-99476",
  "modified": "2026-11-19T16:45:39.843188199Z",
  "published": "2026-11-19T14:43:08.574Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/10c13801ea38e4ced23c59052ce45acb07c5deda"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99476.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99476"
    }
  ],
  "schema_version": "1.9.2",
  "summary": "fsverity: Set S_VERITY only after rollback is no longer possible"
}