CVE-2026-31567
Last modified
CVE-2026-31567 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: PM: sleep: Drop spurious WARN_ON() from pm_restore_gfp_mask() Commit 35e4a69b2003f ("PM: sleep: Allow pm_restrict_gfp_mask() stacking") introduced refcount-based GFP mask management that warns when pm_restore_gfp_mask() is called with saved_gfp_count == 0. Some hibernation paths call pm_restore_gfp_mask() defensively where the GFP mask may or may not be restricted depending on the execution path. For example, the uswsusp interface invokes it in SNAPSHOT_CREATE_IMAGE, SNAPSHOT_UNFREEZE, and snapshot_release(). Before the stacking change this was a silent no-op; it now triggers a spurious WARNING. Remove the WARN_ON() wrapper from the !saved_gfp_count check while retaining the check itself, so that defensive calls remain harmless without producing false warnings. [ rjw: Subject tweak ]. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: PM: sleep: Drop spurious WARN_ON() from pm_restore_gfp_mask() Commit 35e4a69b2003f ("PM: sleep: Allow pm_restrict_gfp_mask() stacking") introduced refcount-based GFP mask management that warns when pm_restore_gfp_mask() is called with saved_gfp_count == 0. Some hibernation paths call pm_restore_gfp_mask() defensively where the GFP mask may or may not be restricted depending on the execution path. For example, the uswsusp interface invokes it in SNAPSHOT_CREATE_IMAGE, SNAPSHOT_UNFREEZE, and snapshot_release(). Before the stacking change this was a silent no-op; it now triggers a spurious WARNING. Remove the WARN_ON() wrapper from the !saved_gfp_count check while retaining the check itself, so that defensive calls remain harmless without producing false warnings. [ rjw: Subject tweak ]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.17.8, < 6.18 | — |
| Linux | Linux Kernel | >= 6.18.1, < 6.18.21 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.11 | — |
| Linux | Linux Kernel | 6.18 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31567?
How severe is CVE-2026-31567?
How do I fix CVE-2026-31567?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31561In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31562In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31563In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-31564In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31565In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31566In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31568In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-31569In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-3157IBM Sterling B2B Integrator 6.2.0.0 through 6.2.0.5_2, 6.2.1…4.3
- CVE-2026-31570In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-31571In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31572In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2026-31567?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
