Menu

Star on GitHub · 3.2k

CVE-2025-68239

In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: restore write access before closing files opened by open_exec() bm_register_write() opens an executable file using…

Published Dec 16, 2025EPSS 0.20%

Overview

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

Technical description

In the Linux kernel, the following vulnerability has been resolved:

binfmt_misc: restore write access before closing files opened by open_exec()

bm_register_write() opens an executable file using open_exec(), which

internally calls do_open_execat() and denies write access on the file to

avoid modification while it is being executed.

However, when an error occurs, bm_register_write() closes the file using

filp_close() directly. This does not restore the write permission, which

may cause subsequent write operations on the same file to fail.

Fix this by calling exe_file_allow_write_access() before filp_close() to

restore the write permission properly.

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-68239?

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

How severe is CVE-2025-68239?

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-68239?

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-68239?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68239 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.