Menu

Star on GitHub · 3.2k

CVE-2025-40070

In the Linux kernel, the following vulnerability has been resolved: pps: fix warning in pps_register_cdev when register device fail Similar to previous commit 2a934fdb01db ("media: v4l2-dev: fix…

Published Oct 28, 2025EPSS 0.24%

Overview

CVE-2025-40070 is a known-severity vulnerability. It was published on October 28, 2025.

Technical description

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

pps: fix warning in pps_register_cdev when register device fail

Similar to previous commit 2a934fdb01db ("media: v4l2-dev: fix error

handling in __video_register_device()"), the release hook should be set

before device_register(). Otherwise, when device_register() return error

and put_device() try to callback the release function, the below warning

may happen.

------------[ cut here ]------------

WARNING: CPU: 1 PID: 4760 at drivers/base/core.c:2567 device_release+0x1bd/0x240 drivers/base/core.c:2567

Modules linked in:

CPU: 1 UID: 0 PID: 4760 Comm: syz.4.914 Not tainted 6.17.0-rc3+ #1 NONE

RIP: 0010:device_release+0x1bd/0x240 drivers/base/core.c:2567

Call Trace:

<TASK>

kobject_cleanup+0x136/0x410 lib/kobject.c:689

kobject_release lib/kobject.c:720 [inline]

kref_put include/linux/kref.h:65 [inline]

kobject_put+0xe9/0x130 lib/kobject.c:737

put_device+0x24/0x30 drivers/base/core.c:3797

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

CVE-2025-40070 is a known-severity vulnerability. It was published on October 28, 2025.

How severe is CVE-2025-40070?

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

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

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