CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping
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
- CWE
- CWE-369
Report tools
Action score
22
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_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
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel4.5 and later · before 6.1.142
- linux linux kernel6.2 and later · before 6.6.94
- linux linux kernel6.7 and later · before 6.12.34
- linux linux kernel6.13 and later · before 6.15.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.35-1 | 6.12.35-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
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 DQO22Monitor
- ← EarlierCVE-2025-38125Jul 3, 2025 · net: stmmac: make sure that ptp_rate is not 0 before configuring EST22Monitor
- Later →CVE-2025-38127Jul 3, 2025 · ice: fix Tx scheduler error handling in XDP callback22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 030ce919e114a111e83b7976ecb3597cefd33f26 | Vendor (CNA) |
| Linux Linux | 32af9c289234990752281c805500dfe03c5b2b8f | Vendor (CNA) |
| Linux Linux | 379cd990dfe752b38fcf46034698a9a150626c7a | Vendor (CNA) |
| Linux Linux | b263088ee8ab14563817a8be3519af8e25225793 | Vendor (CNA) |
| Linux Linux | bb033c6781ce1b0264c3993b767b4aa9021959c2 | Vendor (CNA) |
| azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.147-1 · Debian:12 | Package 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 case33Monitor
- CVE-2025-382051 days apartdrm/amd/display: Avoid divide by zero by initializing dummy pitch to 122Monitor
- 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 error22Monitor
- 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 ZeroCVSS 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.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/32af9c289234990752281c805500dfe03c5b2b8f
- git.kernel.org/stable/c/379cd990dfe752b38fcf46034698a9a150626c7a
- git.kernel.org/stable/c/b263088ee8ab14563817a8be3519af8e25225793
- git.kernel.org/stable/c/bb033c6781ce1b0264c3993b767b4aa9021959c2
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.