21 matches found
SUSE CVE-2026-64292
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
SUSE CVE-2026-64293
In the Linux kernel, the following vulnerability has been resolved: iommufd: Use sizeofhdr instead of sizeofhdr in veventq read The bound-check in iommufdveventqfopsread for the normal vEVENT path uses sizeofhdr where the surrounding code uses sizeofhdr: if !veventforlosteventsheadercur &&...
CVE-2026-64293
In the Linux kernel, the following vulnerability has been resolved: iommufd: Use sizeofhdr instead of sizeofhdr in veventq read The bound-check in iommufdveventqfopsread for the normal vEVENT path uses sizeofhdr where the surrounding code uses sizeofhdr: if !veventforlosteventsheadercur &&...
CVE-2026-64292
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
UBUNTU-CVE-2026-64292
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
CVE-2026-64292
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
EUVD-2026-49004
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
CVE-2026-64292 iommufd: Move vevent memory allocation outside spinlock
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
CVE-2026-64292
CVE-2026-64292 : In the Linux kernel, the iommufd component is vulnerable due to veventq memory allocation happening inside a spinlock, enabling a local user to exhaust atomic memory reserves by creating large queues and trigger a DoS. The fix moves the veventq memory allocation outside the spinl...
CVE-2026-64292 iommufd: Move vevent memory allocation outside spinlock
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
PT-2026-64512
In the Linux kernel, the following vulnerability has been resolved: iommufd: Set veventq depth upper bound iommufd veventq alloc accepts any !0 veventq depth from userspace, with an upper bound at U32 MAX. This leaves a vulnerability where userspace can allocate excessively large queues to exhaus...
Linux Distros Unpatched Vulnerability : CVE-2026-64292
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space,...
PT-2026-64513
In the Linux kernel, the following vulnerability has been resolved: iommufd: Move vevent memory allocation outside spinlock The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queu...
PT-2026-64514
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the iommufd veventq fops read function where a bound-check for the normal vEVENT path incorrectly uses sizeofhdr instead of sizeofhdr. Because hdr is a pointer,...
MS Outlook iCal Meeting Request VEVENT Record Memory Corruption (MS07-003; CVE-2007-0033)
Microsoft provides server and client side implementations of email protocols such as SMTP, POP3 and IMAP. The widely used Microsoft Outlook product is an implementation of an email client capable of handling most standard Internet protocols as well as numerous proprietary Microsoft protocols and...
Microsoft Outlook VEVENT记录远程代码执行漏洞（MS07-003）
Microsoft Outlook是Office套件所捆绑的邮件客户端。 Microsoft Outlook在处理畸形VEVENT记录时存在漏洞，远程攻击者可能利用此漏洞控制用户机器。 攻击可以通过处理包含畸形VEVENT记录的.ics（iCal）文件来利用此漏洞，如果用户使用管理用户权限登录，成功利用此漏洞的攻击者便可完全控制受影响的系统。攻击者可随后安装程序；查看、更改或删除数据；或者创建拥有完全用户权限的新帐户。那些帐户被配置为拥有较少系统用户权限的用户比具有管理用户权限的用户受到的影响要小。 Microsoft Outlook 2003 Microsoft Outlook 200...
Design/Logic Flaw
Microsoft Outlook 2002 and 2003 allows user-assisted remote attackers to execute arbitrary code via a malformed VEVENT record in an .iCal meeting request or ICS file...
CVE-2007-0033
Microsoft Outlook 2002 and 2003 allows user-assisted remote attackers to execute arbitrary code via a malformed VEVENT record in an .iCal meeting request or ICS file...
CVE-2007-0033
CVE-2007-0033 is a memory corruption/remote code execution vulnerability in Microsoft Outlook 2002 and 2003 triggered by parsing a malformed VEVENT record in an iCalendar (.ics) file or meeting request. The flaw arises from inadequate validation when processing VEVENT data, enabling a user-assist...