CVE-2025-40070 — pps: fix warning in pps_register_cdev when register device fail
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 pps_register_cdev+0x2da/0x370 drivers/pps/pps.c:402 pps_register_source+0x2f6/0x480 drivers/pps/kapi.c:108 pps_tty_open+0x190/0x310 drivers/pps/clients/pps-ldisc.c:57 tty_ldisc_open+0xa7/0x120 drivers/tty/tty_ldisc.c:432 tty_set_ldisc+0x333/0x780 drivers/tty/tty_ldisc.c:563 tiocsetd drivers/tty/tty_io.c:2429 [inline] tty_ioctl+0x5d1/0x1700 drivers/tty/tty_io.c:2728 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:598 [inline] __se_sys_ioctl fs/ioctl.c:584 [inline] __x64_sys_ioctl+0x194/0x210 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x5f/0x2a0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e </TASK> Before commit c79a39dc8d06 ("pps: Fix a use-after-free"), pps_register_cdev() call device_create() to create pps->dev, which will init dev->release to device_create_release(). Now the comment is outdated, just remove it. Thanks for the reminder from Calvin Owens, 'kfree_pps' should be removed in pps_register_source() to avoid a double free in the failure case.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 85241f7de216f8298f6e48540ea13d7dcd100870version 6.14≥ 6.13.2 and < 6.14≥ 6.12.13 and < 6.12.53≥ 6.6.76 and < 6.6.112≥ 6.1.129 and < 6.1.156≥ 5.15.179 and < 5.15.195≥ 5.10.235 and < 5.10.246 and 9 more≥ 5.4.291 and < 5.4.301≥ 785c78ed0d39d1717cca3ef931d3e51337b5e90e and < 38c7bb10aae5118dd48fa7a82f7bf93839bcc320≥ c79a39dc8d060b9e64e8b0fa9d245d44befeefbe and < b0531cdba5029f897da5156815e3bdafe1e9b88d≥ c79a39dc8d060b9e64e8b0fa9d245d44befeefbe and < 0f97564a1fb62f34b3b498e2f12caffbe99c004a≥ 7e5ee3281dc09014367f5112b6d566ba36ea2d49 and < f01fa3588e0b3cb1540f56d2c6bd99e5b3810234≥ cd3bbcb6b3a7caa5ce67de76723b6d8531fb7f64 and < cf71834a0cfc394c72d62fd6dbb470ee13cf8f5e≥ 91932db1d96b2952299ce30c1c693d834d10ace6 and < 4cbd7450a22c5ee4842fc4175ad06c0c82ea53a8≥ c4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7 and < 125527db41805693208ee1aacd7f3ffe6a3a489c≥ 1a7735ab2cb9747518a7416fb5929e85442dec62 and < 2a194707ca27a3b0523023fa8b446e5ec922dc51 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.23%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
12 on the record
- git.kernel.org/stable/c/4cbd7450a22c5ee4842fc4175ad06c0c82ea53a8
- git.kernel.org/stable/c/125527db41805693208ee1aacd7f3ffe6a3a489c
- github.com/advisories/GHSA-24rq-hg3c-whf7
- git.kernel.org/stable/c/0f97564a1fb62f34b3b498e2f12caffbe99c004a
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- git.kernel.org/stable/c/cf71834a0cfc394c72d62fd6dbb470ee13cf8f5e
- git.kernel.org/stable/c/f01fa3588e0b3cb1540f56d2c6bd99e5b3810234
- git.kernel.org/stable/c/b0531cdba5029f897da5156815e3bdafe1e9b88d
- git.kernel.org/stable/c/38c7bb10aae5118dd48fa7a82f7bf93839bcc320
- nvd.nist.gov/vuln/detail/CVE-2025-40070
- git.kernel.org/stable/c/2a194707ca27a3b0523023fa8b446e5ec922dc51
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 6h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 6h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-40070 is "pps: fix warning in pps_register_cdev when register device fail", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.