# CVE-2026-74596: fs,fsverity: remove check for fsverity being enabled in setattr_prepare()

> A local attacker can bypass fs-verity integrity checks on files by exploiting a missing validation in the Linux kernel's setattr_prepare function.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-74596, GHSA-f86r-w2jg-m648, UBUNTU-CVE-2026-74596

## What is CVE-2026-74596?

CVE-2026-74596 is a vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

fs,fsverity: remove check for fsverity being enabled in setattr_prepare()

The check that fs-verity is available in the kernel is not necessary
here. Filesystems could have fsverity files even without fs-verity
enabled. In that case, truncate on fsverity file will succeed, what this
check is trying to prevent.

## Which versions are affected by CVE-2026-74596?


## How do I fix CVE-2026-74596?

Apply the vendor's patch.

## Is CVE-2026-74596 being exploited?

There is no known exploitation of CVE-2026-74596 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74596 and fix it if it is affected.

What it is: CVE-2026-74596 is a vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74596 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74596/ (Markdown: https://insights.sbomify.com/CVE-2026-74596/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74596
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74596
- OSV: https://osv.dev/vulnerability/CVE-2026-74596

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74596/
Summaries are generated and may contain mistakes; the official description above is the record.