Menu

Star on GitHub · 3.2k

CVE-2025-68253

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…

Published Dec 16, 2025EPSS 0.17%

Overview

CVE-2025-68253 is a known-severity vulnerability. It was published on December 16, 2025.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-68253?

CVE-2025-68253 is a known-severity vulnerability. It was published on December 16, 2025.

How severe is CVE-2025-68253?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-68253?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-68253?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68253 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.