{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-99476","id":"CVE-2026-99476","title":"Linux kernel data integrity loss in fsverity enable rollback","description":"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 en","descriptionLong":"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 ->end_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 ->end_enable_verity().","published":"2026-11-19T14:43:08.574Z","updated":"2026-11-19T17:01:20.729692630Z","reserved":"2026-09-25T10:25:14.417Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"f77f281b61183a5c0b87e6a4d101c70bd32c1c79","lessThan":"10c13801ea38e4ced23c59052ce45acb07c5deda","status":"affected","versionType":"git"},{"version":"f77f281b61183a5c0b87e6a4d101c70bd32c1c79","lessThan":"c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"7.0","status":"affected"},{"version":"0","lessThan":"7.0","status":"unaffected","versionType":"semver"},{"version":"7.3.2","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/10c13801ea38e4ced23c59052ce45acb07c5deda","tags":["web"]},{"url":"https://git.kernel.org/stable/c/c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b","tags":["web"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99476.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99476","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":null,"epssPercentile":null,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-99476","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99476","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-99476","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-99476","ok":false,"note":"no score yet"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}