Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Fixed version: Linux Linux 0f97564a1fb62f34b3b498e2f12caffbe99c004a, 125527db41805693208ee1aacd7f3ffe6a3a489c, 2a194707ca27a3b0523023fa8b446e5ec922dc51.

Low priority for now. Upgrade to Linux Linux 0f97564a1fb62f34b3b498e2f12caffbe99c004a, 125527db41805693208ee1aacd7f3ffe6a3a489c, 2a194707ca27a3b0523023fa8b446e5ec922dc51 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 28, 2025
Updated
Oct 19, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40070

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 85241f7de216f8298f6e48540ea13d7dcd100870, 6.14affected
    • 785c78ed0d39d1717cca3ef931d3e51337b5e90e and later · before 38c7bb10aae5118dd48fa7a82f7bf93839bcc320affected · git
    • 1a7735ab2cb9747518a7416fb5929e85442dec62 and later · before 2a194707ca27a3b0523023fa8b446e5ec922dc51affected · git
    • c4041b6b0a7a3def8cf3f3d6120ff337bc4c40f7 and later · before 125527db41805693208ee1aacd7f3ffe6a3a489caffected · git
    • 91932db1d96b2952299ce30c1c693d834d10ace6 and later · before 4cbd7450a22c5ee4842fc4175ad06c0c82ea53a8affected · git
    • cd3bbcb6b3a7caa5ce67de76723b6d8531fb7f64 and later · before cf71834a0cfc394c72d62fd6dbb470ee13cf8f5eaffected · git
    • 7e5ee3281dc09014367f5112b6d566ba36ea2d49 and later · before f01fa3588e0b3cb1540f56d2c6bd99e5b3810234affected · git
    • c79a39dc8d060b9e64e8b0fa9d245d44befeefbe and later · before 0f97564a1fb62f34b3b498e2f12caffbe99c004aaffected · git
    • c79a39dc8d060b9e64e8b0fa9d245d44befeefbe and later · before b0531cdba5029f897da5156815e3bdafe1e9b88daffected · git
    • 5.4.291 and later · before 5.4.301affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40068Oct 28, 2025 · fs: ntfs3: Fix integer overflow in run_unpack()
    33Monitor
  • ← EarlierCVE-2025-40069Oct 28, 2025 · drm/msm: Fix obj leak in VM_BIND error path
    31Monitor
  • Later →CVE-2025-40071Oct 28, 2025 · tty: n_gsm: Don't block input queue by waiting MSC
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0f97564a1fb62f34b3b498e2f12caffbe99c004aVendor (CNA)
Linux Linux125527db41805693208ee1aacd7f3ffe6a3a489cVendor (CNA)
Linux Linux2a194707ca27a3b0523023fa8b446e5ec922dc51Vendor (CNA)
Linux Linux38c7bb10aae5118dd48fa7a82f7bf93839bcc320Vendor (CNA)
Linux Linux4cbd7450a22c5ee4842fc4175ad06c0c82ea53a8Vendor (CNA)
Linux Linux5.10.246Vendor (CNA)
Linux Linux5.15.195Vendor (CNA)
Linux Linux5.4.301Vendor (CNA)
Linux Linux6.1.156Vendor (CNA)
Linux Linux6.12.53Vendor (CNA)
Linux Linux6.14Vendor (CNA)
Linux Linux6.6.112Vendor (CNA)
Linux Linuxb0531cdba5029f897da5156815e3bdafe1e9b88dVendor (CNA)
Linux Linuxcf71834a0cfc394c72d62fd6dbb470ee13cf8f5eVendor (CNA)
Linux Linuxf01fa3588e0b3cb1540f56d2c6bd99e5b3810234Vendor (CNA)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records