CVE-2026-72394: hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 898ca04b096b9e4640300eab91468c826a1ec92b, a3f98bd397398e2d4a7f98e006b5aaf4d54ebdf3, fb8a5afe6f1f8aa7f19c6dda23d277dd6ae5d9e1.
Low priority for now. Upgrade to Linux Linux 898ca04b096b9e4640300eab91468c826a1ec92b, a3f98bd397398e2d4a7f98e006b5aaf4d54ebdf3, fb8a5afe6f1f8aa7f19c6dda23d277dd6ae5d9e1 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: hwmon: (aspeed-g6-pwm-tach) Guard fan RPM calculation against divide-by-zero Sashiko reports: In the aspeed-g6-pwm-tacho driver, the aspeed_tach_val_to_rpm() function calculates the fan RPM using the tachometer value. However, it does not check if the tachometer value is zero before performing the division. If the hardware reports a tachometer value of 0 (which can happen due to an extremely fast pulse, a stuck edge, or a hardware glitch), the calculated tach_div evaluates to 0. The subsequent call to do_div() with tach_div as the divisor triggers a divide-by-zero exception, leading to a kernel panic. Check the divisor against zero to fix the problem.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
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.
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.
—
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
- 6.9affected
- 7e1449cd15d1096157d1a9923b82e37602fb7eb0 and later · before a3f98bd397398e2d4a7f98e006b5aaf4d54ebdf3affected · git
- 7e1449cd15d1096157d1a9923b82e37602fb7eb0 and later · before 898ca04b096b9e4640300eab91468c826a1ec92baffected · git
- 7e1449cd15d1096157d1a9923b82e37602fb7eb0 and later · before fb8a5afe6f1f8aa7f19c6dda23d277dd6ae5d9e1affected · git
- 7e1449cd15d1096157d1a9923b82e37602fb7eb0 and later · before fe87b8dc67f1b2c64e76a66e78468c533d3c44caaffected · git
- before 6.9not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
- 7.1.5 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72391Aug 15, 2026 · net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy0Monitor
- ← EarlierCVE-2026-72393Aug 15, 2026 · eth: fbnic: don't cache shinfo across skb realloc39Monitor
- Later →CVE-2026-72399Aug 15, 2026 · net: enetc: check the number of BDs needed for xdp_frame39Monitor
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 | 898ca04b096b9e4640300eab91468c826a1ec92b | Vendor (CNA) |
| Linux Linux | a3f98bd397398e2d4a7f98e006b5aaf4d54ebdf3 | Vendor (CNA) |
| Linux Linux | fb8a5afe6f1f8aa7f19c6dda23d277dd6ae5d9e1 | Vendor (CNA) |
| Linux Linux | fe87b8dc67f1b2c64e76a66e78468c533d3c44ca | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.