# CVE-2026-74592: ima: Instantiate file_truncate and path_truncate hooks

> Missing IMA hook instantiation allows files to bypass re-measurement after truncation, potentially hiding unauthorized modifications from integrity checks.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-97362, BELL-CVE-2026-74592, DEBIAN-CVE-2026-74592, GHSA-hgmq-24pq-jx89, UBUNTU-CVE-2026-74592

## What is CVE-2026-74592?

CVE-2026-74592 is a high-severity vulnerability in Linux, published on 22 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

ima: Instantiate file_truncate and path_truncate hooks

Instantiate the file_truncate and path_truncate LSM hooks to reset the
action cache flags (IMA_DONE_MASK) as soon as truncation is requested,
so the file, based on policy, is re-collected, re-measured, re-audited,
and re-appraised on next access.

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


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

Apply the vendor's patch.

## Is CVE-2026-74592 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74592 is a high-severity vulnerability in Linux, published on 22 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74592 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-74592/ (Markdown: https://insights.sbomify.com/CVE-2026-74592/index.md)
```

## Sources

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

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