Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/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.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 030ce919e114a111e83b7976ecb3597cefd33f26, 32af9c289234990752281c805500dfe03c5b2b8f, 379cd990dfe752b38fcf46034698a9a150626c7a; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.1-1.

Low priority for now. Upgrade to Linux Linux 030ce919e114a111e83b7976ecb3597cefd33f26, 32af9c289234990752281c805500dfe03c5b2b8f, 379cd990dfe752b38fcf46034698a9a150626c7a; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.1-1 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: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping The stmmac platform drivers that do not open-code the clk_ptp_rate value after having retrieved the default one from the device-tree can end up with 0 in clk_ptp_rate (as clk_get_rate can return 0). It will eventually propagate up to PTP initialization when bringing up the interface, leading to a divide by 0: Division by zero in kernel. CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.30-00001-g48313bd5768a #22 Hardware name: STM32 (Device Tree Support) Call trace: unwind_backtrace from show_stack+0x18/0x1c show_stack from dump_stack_lvl+0x6c/0x8c dump_stack_lvl from Ldiv0_64+0x8/0x18 Ldiv0_64 from stmmac_init_tstamp_counter+0x190/0x1a4 stmmac_init_tstamp_counter from stmmac_hw_setup+0xc1c/0x111c stmmac_hw_setup from __stmmac_open+0x18c/0x434 __stmmac_open from stmmac_open+0x3c/0xbc stmmac_open from __dev_open+0xf4/0x1ac __dev_open from __dev_change_flags+0x1cc/0x224 __dev_change_flags from dev_change_flags+0x24/0x60 dev_change_flags from ip_auto_config+0x2e8/0x11a0 ip_auto_config from do_one_initcall+0x84/0x33c do_one_initcall from kernel_init_freeable+0x1b8/0x214 kernel_init_freeable from kernel_init+0x24/0x140 kernel_init from ret_from_fork+0x14/0x28 Exception stack(0xe0815fb0 to 0xe0815ff8) Prevent this division by 0 by adding an explicit check and error log about the actual issue. While at it, remove the same check from stmmac_ptp_register, which then becomes duplicate

Published
Jul 3, 2025
Updated
Nov 5, 2026
EPSS
0.1% · 9th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-38126

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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.

VendorProduct
linuxlinux kernel
debiandebian linux

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

    • 4.5affected
    • 19d857c9038e5c07db8f8cc02b5ad0cd0098714f and later · before 32af9c289234990752281c805500dfe03c5b2b8faffected · git
    • 19d857c9038e5c07db8f8cc02b5ad0cd0098714f and later · before b263088ee8ab14563817a8be3519af8e25225793affected · git
    • 19d857c9038e5c07db8f8cc02b5ad0cd0098714f and later · before bb033c6781ce1b0264c3993b767b4aa9021959c2affected · git
    • 19d857c9038e5c07db8f8cc02b5ad0cd0098714f and later · before 379cd990dfe752b38fcf46034698a9a150626c7aaffected · git
    • 19d857c9038e5c07db8f8cc02b5ad0cd0098714f and later · before 030ce919e114a111e83b7976ecb3597cefd33f26affected · git
    • before 4.5not affected · semver
    • 6.1.142 and later · up to and including 6.1.*not affected · semver
    • 6.6.94 and later · up to and including 6.6.*not affected · semver
    • 6.12.34 and later · up to and including 6.12.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.147-16.1.147-1
Debian:13linuxbefore 6.12.35-16.12.35-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38122Jul 3, 2025 · gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO
    22Monitor
  • ← EarlierCVE-2025-38125Jul 3, 2025 · net: stmmac: make sure that ptp_rate is not 0 before configuring EST
    22Monitor
  • Later →CVE-2025-38127Jul 3, 2025 · ice: fix Tx scheduler error handling in XDP callback
    22Monitor

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 Linux030ce919e114a111e83b7976ecb3597cefd33f26Vendor (CNA)
Linux Linux32af9c289234990752281c805500dfe03c5b2b8fVendor (CNA)
Linux Linux379cd990dfe752b38fcf46034698a9a150626c7aVendor (CNA)
Linux Linuxb263088ee8ab14563817a8be3519af8e25225793Vendor (CNA)
Linux Linuxbb033c6781ce1b0264c3993b767b4aa9021959c2Vendor (CNA)
azl3 kernel 6.6.92.2-2 on Azure Linux 3.06.6.96.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.96.1-1 on Azure Linux 3.06.6.96.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.147-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.

Variant candidates

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

  • CVE-2024-26945428 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case
    33Monitor
  • CVE-2025-382051 days apartdrm/amd/display: Avoid divide by zero by initializing dummy pitch to 1
    22Monitor
  • CVE-2025-382977 days apartPM: EM: Fix potential division-by-zero error in em_compute_costs()
    22Monitor
  • CVE-2025-383127 days apartfbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod()
    22Monitor
  • CVE-2022-4997815 days apartfbdev: fb_pm2fb: Avoid potential divide by zero error
    22Monitor
  • CVE-2022-5010215 days apartvideo: fbdev: arkfb: Fix a divide-by-zero bug in ark_set_pixclock()
    22Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-369 · Divide By Zero

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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.

References

All records