GHSA-65W6-RWF9-587R
Vulnerability from github – Published: 2026-01-14 15:33 – Updated: 2026-01-14 15:33
VLAI?
Details
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.
{
"affected": [],
"aliases": [
"CVE-2025-71106"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-14T15:15:59Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs: PM: Fix reverse check in filesystems_freeze_callback()\n\nThe freeze_all_ptr check in filesystems_freeze_callback() introduced by\ncommit a3f8f8662771 (\"power: always freeze efivarfs\") is reverse which\nquite confusingly causes all file systems to be frozen when\nfilesystem_freeze_enabled is false.\n\nOn my systems it causes the WARN_ON_ONCE() in __set_task_frozen() to\ntrigger, most likely due to an attempt to freeze a file system that is\nnot ready for that.\n\nAdd a logical negation to the check in question to reverse it as\nappropriate.",
"id": "GHSA-65w6-rwf9-587r",
"modified": "2026-01-14T15:33:00Z",
"published": "2026-01-14T15:33:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-71106"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/222047f68e8565c558728f792f6fef152a1d4d51"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b107196729ff6b9d6cde0a71f49c1243def43328"
}
],
"schema_version": "1.4.0",
"severity": []
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…