# CVE-2025-68253: linux: In the Linux kernel, the following vulnerability has been resolved:  mm: don't spin in add_stack_record when gfp flag...

CVE-2025-68253 is fixed in linux on 1 platform by DEBIAN-CVE-2025-68253 (version 6.17.6-1), released December 16, 2025. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2025-68253
- Priority: Routine
- CVSS: n/a
- EPSS: 0.0017
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Dec 16, 2025

## Description

In the Linux kernel, the following vulnerability has been resolved:  mm: don't spin in add_stack_record when gfp flags don't allow  syzbot was able to find the following path:   add_stack_record_to_list mm/page_owner.c:182 [inline]   inc_stack_record_count mm/page_owner.c:214 [inline]   __set_page_owner+0x2c3/0x4a0 mm/page_owner.c:333   set_page_owner include/linux/page_owner.h:32 [inline]   post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851   prep_new_page mm/page_alloc.c:1859 [inline]   get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858   alloc_pages_nolock_noprof+0x94/0x120 mm/page_alloc.c:7554  Don't spin in add_stack_record_to_list() when it is called from *_nolock() context.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 6.17.6-1 | [DEBIAN-CVE-2025-68253](https://patchblox.com/security/data/fix/linux/debian-cve-2025-68253.md) | Dec 16, 2025 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.