CVE-2026-43372 — net: dsa: microchip: Fix error path in PTP IRQ setup
In the Linux kernel, the following vulnerability has been resolved: net: dsa: microchip: Fix error path in PTP IRQ setup If request_threaded_irq() fails during the PTP message IRQ setup, the newly created IRQ mapping is never disposed. Indeed, the ksz_ptp_irq_setup()'s error path only frees the mappings that were successfully set up. Dispose the newly created mapping if the associated request_threaded_irq() fails at setup.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 3b5a6115d6ea45df1ea65dc9b832b23db5d593ba and < 3704ac6a0d9a78f66a187515a8ca3faedaf01cc5version 6.18≥ 6.17.11 and < 6.18≥ 6.12.61 and < 6.12.78≥ 6.6.119 and < 6.6.130version ae12e4e0ca231475bcef841c6a6722fa185fd520≥ d0b8fec8ae50525b57139393d0bb1f446e82ff7e and < 99c8c16a4aad0b37293cae213e15957c573cf79b≥ d0b8fec8ae50525b57139393d0bb1f446e82ff7e and < c2d1d41e0e8ec447d40a5752844fc5fb0b23db27 and 2 more≥ d0b8fec8ae50525b57139393d0bb1f446e82ff7e and < 6c58a9fdb0d0e1011aa02455d26d6ebea251979b≥ 1ba6da6ca3db76f6a39004fd33a9c990e428515e and < e80fef36c676c947072dabeb5803ae59d92ba493 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
≥ 6.6.119 and < 6.6.130version 7.0-rc3version 7.0-rc2version 7.0-rc1version 6.18≥ 6.19 and < 6.19.9≥ 6.18.1 and < 6.18.19≥ 6.17.11 and < 6.18 and 1 more≥ 6.12.61 and < 6.12.78 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.16%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
- git.kernel.org/stable/c/6c58a9fdb0d0e1011aa02455d26d6ebea251979b
- git.kernel.org/stable/c/3704ac6a0d9a78f66a187515a8ca3faedaf01cc5
- git.kernel.org/stable/c/99c8c16a4aad0b37293cae213e15957c573cf79b
- git.kernel.org/stable/c/c2d1d41e0e8ec447d40a5752844fc5fb0b23db27
- git.kernel.org/stable/c/e80fef36c676c947072dabeb5803ae59d92ba493
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 7h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 7h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-43372 is "net: dsa: microchip: Fix error path in PTP IRQ setup", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.16% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.