# CVE-2026-99476: fsverity: Set S_VERITY only after rollback is no longer possible

Status: published. Published: 2026-11-19. Updated: 2026-11-22.

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

fsverity: Set S_VERITY only after rollback is no longer possible

Commit f77f281b6118 ("fsverity: use a hashtable to find the
fsverity_info") changed the implementation of FS_IOC_ENABLE_VERITY to
make concurrent reads start going through fsverity verification slightly
earlier than they did before.

Instead of it happening when enable_verity() calls fsverity_set_info(),
it now happens when ->end_enable_verity() sets S_VERITY.

However, ext4 and btrfs can roll back verity after they set S_VERITY,
causing a use-after-free.

Fix that by making ext4 and btrfs set S_VERITY only after rollback is no
longer possible.  On failure, don't roll back S_VERITY, but do roll back
the filesystem-specific verity flag.

Also update enable_verity() to handle any future instances of this bug
more safely by warning and *not* freeing the fsverity_info.

Finally, tweak some comments.  Clarify one, and move information from
another to its proper place in the comment for ->end_enable_verity().

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ f77f281b61183a5c0b87e6a4d101c70bd32c1c79; < 10c13801ea38e4ced23c59052ce45acb07c5deda (affected, git); ≥ f77f281b61183a5c0b87e6a4d101c70bd32c1c79; < c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b (affected, git). Source: CNA: Linux
- Linux / Linux: 7.0 (affected); ≥ 0; < 7.0 (unaffected, semver); ≥ 7.3.2; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.16% as of 2026-11-21; percentile 4.74%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/10c13801ea38e4ced23c59052ce45acb07c5deda (CNA: Linux)

- https://git.kernel.org/stable/c/c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b (CNA: Linux)

- https://git.kernel.org/stable/c/10c13801ea38e4ced23c59052ce45acb07c5deda (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/c349b233d6ab0fc3517401a1e2d36f5f90eb8c9b (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99476; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99476; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99476; retrieved 2026-11-22; source updated Not reported

Revision: 7a7bfd34c13243352f20537dc14be562a5c697a49e328df5e053ce0859af640d

Canonical: https://y2.dev/cve/CVE-2026-99476

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.