CVE-2025-40048 — uio_hv_generic: Let userspace take care of interrupt mask
In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Let userspace take care of interrupt mask Remove the logic to set interrupt mask by default in uio_hv_generic driver as the interrupt mask value is supposed to be controlled completely by the user space. If the mask bit gets changed by the driver, concurrently with user mode operating on the ring, the mask bit may be set when it is supposed to be clear, and the user-mode driver will miss an interrupt which will cause a hang. For eg- when the driver sets inbound ring buffer interrupt mask to 1, the host does not interrupt the guest on the UIO VMBus channel. However, setting the mask does not prevent the host from putting a message in the inbound ring buffer. So let’s assume that happens, the host puts a message into the ring buffer but does not interrupt. Subsequently, the user space code in the guest sets the inbound ring buffer interrupt mask to 0, saying “Hey, I’m ready for interrupts”. User space code then calls pread() to wait for an interrupt. Then one of two things happens: * The host never sends another message. So the pread() waits forever. * The host does send another message. But because there’s already a message in the ring buffer, it doesn’t generate an interrupt. This is the correct behavior, because the host should only send an interrupt when the inbound ring buffer transitions from empty to not-empty. Adding an additional message to a ring buffer that is not empty is not supposed to generate an interrupt on the guest. Since the guest is waiting in pread() and not removing messages from the ring buffer, the pread() waits forever. This could be easily reproduced in hv_fcopy_uio_daemon if we delay setting interrupt mask to 0. Similarly if hv_uio_channel_cb() sets the interrupt_mask to 1, there’s a race condition. Once user space empties the inbound ring buffer, but before user space sets interrupt_mask to 0, the host could put another message in the ring buffer but it wouldn’t interrupt. Then the next pread() would hang. Fix these by removing all instances where interrupt_mask is changed, while keeping the one in set_event() unchanged to enable userspace control the interrupt mask by writing 0/1 to /dev/uioX.
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.6% (30-day exploitation probability)+7
- Technical severity (high)+6
- Automatable exploitation (SSVC)+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.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
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).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- 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 |
≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < 540aac117eaea5723cef5e4cbf3035c4ac654d92≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < 65d40acd911c7011745cbbd2aaac34eb5266d11e≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < a44f61f878f32071d6378e8dd7c2d47f9490c8f7≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < 01ce972e6f9974a7c76943bcb7e93746917db83a≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < 2af39ab5e6dc46b835a52e80a22d0cad430985e3≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < 37bd91f22794dc05436130d6983302cb90ecfe7e≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < e29587c07537929684faa365027f4b0d87521e1b≥ 95096f2fbd10186d3e78a328b327afc71428f65f and < b15b7d2a1b09ef5428a8db260251897405a19496 and 1 moreversion 4.10 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
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 |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.5 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.64%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.5
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
10 on the record
- git.kernel.org/stable/c/65d40acd911c7011745cbbd2aaac34eb5266d11e
- github.com/advisories/GHSA-hw92-4498-rgw4
- git.kernel.org/stable/c/540aac117eaea5723cef5e4cbf3035c4ac654d92
- git.kernel.org/stable/c/b15b7d2a1b09ef5428a8db260251897405a19496
- git.kernel.org/stable/c/37bd91f22794dc05436130d6983302cb90ecfe7e
- git.kernel.org/stable/c/e29587c07537929684faa365027f4b0d87521e1b
- git.kernel.org/stable/c/2af39ab5e6dc46b835a52e80a22d0cad430985e3
- nvd.nist.gov/vuln/detail/CVE-2025-40048
- git.kernel.org/stable/c/a44f61f878f32071d6378e8dd7c2d47f9490c8f7
- git.kernel.org/stable/c/01ce972e6f9974a7c76943bcb7e93746917db83a
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 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 fixed version, patch or mitigation documented.
- 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-2025-40048 is "uio_hv_generic: Let userspace take care of interrupt mask", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.64% 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.