Answer in brief
CVE-2025-40070 records a Unknown severity vulnerability in pps: fix warning in pps_register_cdev when register device fail. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=785c78ed0d39d1717cca3ef931d3e51337b5e90e <38c7bb10aae5118dd48fa7a82f7bf93839bcc320 || >=1a7735ab2cb9747518a7416fb5929e85442dec62 <2a194707ca27a3b0523023fa8b446e5ec922dc51 || >=c4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7 <125527db41805693208ee1aacd7f3ffe6a3a489c || >=91932db1d96b2952299ce30c1c693d834d10ace6 <4cbd7450a22c5ee4842fc4175ad06c0c82ea53a8 || >=cd3bbcb6b3a7caa5ce67de76723b6d8531fb7f64 <cf71834a0cfc394c72d62fd6dbb470ee13cf8f5e || >=7e5ee3281dc09014367f5112b6d566ba36ea2d49 <f01fa3588e0b3cb1540f56d2c6bd99e5b3810234 || >=c79a39dc8d060b9e64e8b0fa9d245d44befeefbe <0f97564a1fb62f34b3b498e2f12caffbe99c004a || >=c79a39dc8d060b9e64e8b0fa9d245d44befeefbe <b0531cdba5029f897da5156815e3bdafe1e9b88d || 85241f7de216f8298f6e48540ea13d7dcd100870 || >=5.4.291 <5.4.301 || >=5.10.235 <5.10.246 || >=5.15.179 <5.15.195 || >=6.1.129 <6.1.156 || >=6.6.76 <6.6.112 || >=6.12.13 <6.12.53 || >=6.13.2 <6.14 | 38c7bb10aae5118dd48fa7a82f7bf93839bcc320, 2a194707ca27a3b0523023fa8b446e5ec922dc51, 125527db41805693208ee1aacd7f3ffe6a3a489c, 4cbd7450a22c5ee4842fc4175ad06c0c82ea53a8, cf71834a0cfc394c72d62fd6dbb470ee13cf8f5e, f01fa3588e0b3cb1540f56d2c6bd99e5b3810234, 0f97564a1fb62f34b3b498e2f12caffbe99c004a, b0531cdba5029f897da5156815e3bdafe1e9b88d, 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Oct 28, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.