Menu

Star on GitHub · 3.2k

CVE-2025-68237

In the Linux kernel, the following vulnerability has been resolved: mtdchar: fix integer overflow in read/write ioctls The "req.start" and "req.len" variables are u64 values that come from the us…

Published Dec 16, 2025EPSS 0.19%

Overview

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

Technical description

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

mtdchar: fix integer overflow in read/write ioctls

The "req.start" and "req.len" variables are u64 values that come from the

user at the start of the function. We mask away the high 32 bits of

"req.len" so that's capped at U32_MAX but the "req.start" variable can go

up to U64_MAX which means that the addition can still integer overflow.

Use check_add_overflow() to fix this bug.

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

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

How severe is CVE-2025-68237?

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

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

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