CVE-2025-40161: mailbox: zynqmp-ipi: Fix SGI cleanup on unbind
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.19% (FIRST EPSS).
- Fixed version: Linux Linux 1ee147efee68be00203b1fee6479911debb1edb2, 32bf7c6e01f5ba17a53ba236a770bd0274cefdf4, bb160e791ab15b89188a7a19589b8e11f681bef3.
Low priority for now. Upgrade to Linux Linux 1ee147efee68be00203b1fee6479911debb1edb2, 32bf7c6e01f5ba17a53ba236a770bd0274cefdf4, bb160e791ab15b89188a7a19589b8e11f681bef3 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: mailbox: zynqmp-ipi: Fix SGI cleanup on unbind The driver incorrectly determines SGI vs SPI interrupts by checking IRQ number < 16, which fails with dynamic IRQ allocation. During unbind, this causes improper SGI cleanup leading to kernel crash. Add explicit irq_type field to pdata for reliable identification of SGI interrupts (type-2) and only clean up SGI resources when appropriate.
- Published
- Nov 12, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.10affected
- 6ffb1635341bec50fa9540ae7827d1e5d75ae0b0 and later · before 1ee147efee68be00203b1fee6479911debb1edb2affected · git
- 6ffb1635341bec50fa9540ae7827d1e5d75ae0b0 and later · before 32bf7c6e01f5ba17a53ba236a770bd0274cefdf4affected · git
- 6ffb1635341bec50fa9540ae7827d1e5d75ae0b0 and later · before bb160e791ab15b89188a7a19589b8e11f681bef3affected · git
- before 6.10not affected · semver
- 6.12.54 and later · up to and including 6.12.*not affected · semver
- 6.17.4 and later · up to and including 6.17.*not affected · semver
- 6.18 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.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-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-2025-40159Nov 12, 2025 · xsk: Harden userspace-supplied xdp_desc validation31Monitor
- ← EarlierCVE-2025-40160Nov 12, 2025 · xen/events: Return -EEXIST for bound VIRQs0Monitor
- Later →CVE-2025-40162Nov 12, 2025 · ASoC: amd/sdw_utils: avoid NULL deref when devm_kasprintf() fails0Monitor
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 | 1ee147efee68be00203b1fee6479911debb1edb2 | Vendor (CNA) |
| Linux Linux | 32bf7c6e01f5ba17a53ba236a770bd0274cefdf4 | Vendor (CNA) |
| Linux Linux | bb160e791ab15b89188a7a19589b8e11f681bef3 | Vendor (CNA) |
| debian:linux | 6.12.57-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.
Not on record for this CVE: EPSS history · 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 (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.