Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2025-40048— uio_hv_generic: Let userspace take care of interrupt mask

EPSS 0.04% · P13
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-40048

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
uio_hv_generic: Let userspace take care of interrupt mask
Source: NVD (National Vulnerability Database)
Vulnerability Description
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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于中断掩码控制不当,可能导致中断丢失和系统挂起。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 95096f2fbd10186d3e78a328b327afc71428f65f ~ 540aac117eaea5723cef5e4cbf3035c4ac654d92 -
LinuxLinux 4.10 -

II. Public POCs for CVE-2025-40048

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-40048

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-10-28 · 58 CVEs total

CVE-2025-40064smc: Fix use-after-free in __pnet_find_base_ndev().
CVE-2025-40075tcp_metrics: use dst_dev_net_rcu()
CVE-2025-40078bpf: Explicitly check accesses to bpf_sock_addr
CVE-2025-40079riscv, bpf: Sign extend struct ops return values properly
CVE-2025-40077f2fs: fix to avoid overflow while left shift operation
CVE-2025-40081perf: arm_spe: Prevent overflow in PERF_IDX2OFF()
CVE-2025-40068fs: ntfs3: Fix integer overflow in run_unpack()
CVE-2025-40067fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist
CVE-2025-40066wifi: mt76: mt7996: Check phy before init msta_link in mt7996_mac_sta_add_links()
CVE-2025-40065RISC-V: KVM: Write hgatp register with valid mode bits
CVE-2025-40069drm/msm: Fix obj leak in VM_BIND error path
CVE-2025-40063crypto: comp - Use same definition of context alloc and free ops
CVE-2025-40062crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs
CVE-2025-40061RDMA/rxe: Fix race in do_task() when draining
CVE-2025-40060coresight: trbe: Return NULL pointer for allocation failures
CVE-2025-40058iommu/vt-d: Disallow dirty tracking if incoherent page walk
CVE-2025-40059coresight: Fix incorrect handling for return value of devm_kzalloc
CVE-2025-40057ptp: Add a upper bound on max_vclocks
CVE-2025-40056vhost: vringh: Fix copy_to_iter return value check
CVE-2025-40055ocfs2: fix double free in user_cluster_connect()

Showing top 20 of 58 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2025-40048

No comments yet


Leave a comment