Answer in brief
CVE-2025-37885 records a Unknown severity vulnerability in KVM: x86: Reset IRTE to host control if *new* route isn't postable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-37885 records a Unknown severity vulnerability in KVM: x86: Reset IRTE to host control if *new* route isn't postable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=efc644048ecde54f016011fe10110addd0de348f <e5f2dee9f7fcd2ff4b97869f3c66a0d89c167769 || >=efc644048ecde54f016011fe10110addd0de348f <116c7d35b8f72eac383b9fd371d7c1a8ffc2968b || >=efc644048ecde54f016011fe10110addd0de348f <023816bd5fa46fab94d1e7917fe131b79ed1fb41 || >=efc644048ecde54f016011fe10110addd0de348f <3481fd96d801715942b6f69fe251133128156f30 || >=efc644048ecde54f016011fe10110addd0de348f <b5de7ac74f69603ad803c524b840bffd36368fc3 || >=efc644048ecde54f016011fe10110addd0de348f <3066ec21d1a33896125747f68638725f456308db || >=efc644048ecde54f016011fe10110addd0de348f <9bcac97dc42d2f4da8229d18feb0fe2b1ce523a2 | e5f2dee9f7fcd2ff4b97869f3c66a0d89c167769, 116c7d35b8f72eac383b9fd371d7c1a8ffc2968b, 023816bd5fa46fab94d1e7917fe131b79ed1fb41, 3481fd96d801715942b6f69fe251133128156f30, b5de7ac74f69603ad803c524b840bffd36368fc3, 3066ec21d1a33896125747f68638725f456308db, 9bcac97dc42d2f4da8229d18feb0fe2b1ce523a2 |
| Linux/Linuxgeneric | 4.4 | Not reported |
Published upstream
May 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Reset IRTE to host control if *new* route isn't postable Restore an IRTE back to host control (remapped or posted MSI mode) if the *new* GSI route prevents posting the IRQ directly to a vCPU, regardless of the GSI routing type. Updating the IRTE if and only if the new GSI is an MSI results in KVM leaving an IRTE posting to a vCPU. The dangling IRTE can result in interrupts being incorrectly delivered to the guest, and in the worst case scenario can result in use-after-free, e.g. if the VM is torn down, but the underlying host IRQ isn't freed.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=efc644048ecde54f016011fe10110addd0de348f <e5f2dee9f7fcd2ff4b97869f3c66a0d89c167769 || >=efc644048ecde54f016011fe10110addd0de348f <116c7d35b8f72eac383b9fd371d7c1a8ffc2968b || >=efc644048ecde54f016011fe10110addd0de348f <023816bd5fa46fab94d1e7917fe131b79ed1fb41 || >=efc644048ecde54f016011fe10110addd0de348f <3481fd96d801715942b6f69fe251133128156f30 || >=efc644048ecde54f016011fe10110addd0de348f <b5de7ac74f69603ad803c524b840bffd36368fc3 || >=efc644048ecde54f016011fe10110addd0de348f <3066ec21d1a33896125747f68638725f456308db || >=efc644048ecde54f016011fe10110addd0de348f <9bcac97dc42d2f4da8229d18feb0fe2b1ce523a2 | e5f2dee9f7fcd2ff4b97869f3c66a0d89c167769, 116c7d35b8f72eac383b9fd371d7c1a8ffc2968b, 023816bd5fa46fab94d1e7917fe131b79ed1fb41, 3481fd96d801715942b6f69fe251133128156f30, b5de7ac74f69603ad803c524b840bffd36368fc3, 3066ec21d1a33896125747f68638725f456308db, 9bcac97dc42d2f4da8229d18feb0fe2b1ce523a2 |
| Linux/Linuxgeneric | 4.4 | Not reported |
Published upstream
May 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Reset IRTE to host control if *new* route isn't postable Restore an IRTE back to host control (remapped or posted MSI mode) if the *new* GSI route prevents posting the IRQ directly to a vCPU, regardless of the GSI routing type. Updating the IRTE if and only if the new GSI is an MSI results in KVM leaving an IRTE posting to a vCPU. The dangling IRTE can result in interrupts being incorrectly delivered to the guest, and in the worst case scenario can result in use-after-free, e.g. if the VM is torn down, but the underlying host IRQ isn't freed.
Quoted source text, attributed separately from HOL analysis.