{"api_version":"1","generated_at":"2026-07-27T06:07:21+00:00","cve":"CVE-2026-64292","urls":{"html":"https://cve.report/CVE-2026-64292","api":"https://cve.report/api/cve/CVE-2026-64292.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64292","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64292"},"summary":{"title":"iommufd: Move vevent memory allocation outside spinlock","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Move vevent memory allocation outside spinlock\n\nThe veventq memory allocation happens inside the spinlock. Given its depth\nis decided by the user space, this leaves a vulnerability, where userspace\ncan allocate large queues to exhaust atomic memory reserves.\n\nMove the allocation outside the spinlock and use GFP_NOWAIT, which can fail\nfast under memory pressure without dipping into the GFP_ATOMIC reserves or\ndirect-reclaiming from the threaded IRQ handler. On allocation failure,\nqueue the lost_events_header (so userspace learns of the drop) and return\n-ENOMEM so the caller learns of the kernel-side memory pressure.\n\nThis is intentionally distinct from the queue-overflow path, which also\nqueues the lost_events_header but returns 0: a full queue is an expected\nuserspace-pacing condition rather than a kernel error.\n\nA subsequent change will cap the upper bound of the veventq_depth.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-25 10:17:09","updated_at":"2026-07-25 10:17:09"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/6c5fc40200cd0a87d66a368eee00df4d1cca946e","name":"https://git.kernel.org/stable/c/6c5fc40200cd0a87d66a368eee00df4d1cca946e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/47443565d10c51366c9382dbc8597cd6c460b8a2","name":"https://git.kernel.org/stable/c/47443565d10c51366c9382dbc8597cd6c460b8a2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/779480ea79551c31964e74b9aef0e730faa3aa11","name":"https://git.kernel.org/stable/c/779480ea79551c31964e74b9aef0e730faa3aa11","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64292","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64292","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e36ba5ab808ef6237c3148d469c8238674230e2b 779480ea79551c31964e74b9aef0e730faa3aa11 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e36ba5ab808ef6237c3148d469c8238674230e2b 6c5fc40200cd0a87d66a368eee00df4d1cca946e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e36ba5ab808ef6237c3148d469c8238674230e2b 47443565d10c51366c9382dbc8597cd6c460b8a2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.4 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64292","cve":"CVE-2026-64292","epss":"0.001980000","percentile":"0.098580000","score_date":"2026-07-26","updated_at":"2026-07-27 00:02:03"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/iommu/iommufd/driver.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"779480ea79551c31964e74b9aef0e730faa3aa11","status":"affected","version":"e36ba5ab808ef6237c3148d469c8238674230e2b","versionType":"git"},{"lessThan":"6c5fc40200cd0a87d66a368eee00df4d1cca946e","status":"affected","version":"e36ba5ab808ef6237c3148d469c8238674230e2b","versionType":"git"},{"lessThan":"47443565d10c51366c9382dbc8597cd6c460b8a2","status":"affected","version":"e36ba5ab808ef6237c3148d469c8238674230e2b","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/iommu/iommufd/driver.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.15"},{"lessThan":"6.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.40","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.4","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"6.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Move vevent memory allocation outside spinlock\n\nThe veventq memory allocation happens inside the spinlock. Given its depth\nis decided by the user space, this leaves a vulnerability, where userspace\ncan allocate large queues to exhaust atomic memory reserves.\n\nMove the allocation outside the spinlock and use GFP_NOWAIT, which can fail\nfast under memory pressure without dipping into the GFP_ATOMIC reserves or\ndirect-reclaiming from the threaded IRQ handler. On allocation failure,\nqueue the lost_events_header (so userspace learns of the drop) and return\n-ENOMEM so the caller learns of the kernel-side memory pressure.\n\nThis is intentionally distinct from the queue-overflow path, which also\nqueues the lost_events_header but returns 0: a full queue is an expected\nuserspace-pacing condition rather than a kernel error.\n\nA subsequent change will cap the upper bound of the veventq_depth."}],"providerMetadata":{"dateUpdated":"2026-07-25T08:49:31.325Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/779480ea79551c31964e74b9aef0e730faa3aa11"},{"url":"https://git.kernel.org/stable/c/6c5fc40200cd0a87d66a368eee00df4d1cca946e"},{"url":"https://git.kernel.org/stable/c/47443565d10c51366c9382dbc8597cd6c460b8a2"}],"title":"iommufd: Move vevent memory allocation outside spinlock","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64292","datePublished":"2026-07-25T08:49:31.325Z","dateReserved":"2026-07-19T15:36:31.778Z","dateUpdated":"2026-07-25T08:49:31.325Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-25 10:17:09","lastModifiedDate":"2026-07-25 10:17:09","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64292","Ordinal":"1","Title":"iommufd: Move vevent memory allocation outside spinlock","CVE":"CVE-2026-64292","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64292","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Move vevent memory allocation outside spinlock\n\nThe veventq memory allocation happens inside the spinlock. Given its depth\nis decided by the user space, this leaves a vulnerability, where userspace\ncan allocate large queues to exhaust atomic memory reserves.\n\nMove the allocation outside the spinlock and use GFP_NOWAIT, which can fail\nfast under memory pressure without dipping into the GFP_ATOMIC reserves or\ndirect-reclaiming from the threaded IRQ handler. On allocation failure,\nqueue the lost_events_header (so userspace learns of the drop) and return\n-ENOMEM so the caller learns of the kernel-side memory pressure.\n\nThis is intentionally distinct from the queue-overflow path, which also\nqueues the lost_events_header but returns 0: a full queue is an expected\nuserspace-pacing condition rather than a kernel error.\n\nA subsequent change will cap the upper bound of the veventq_depth.","Type":"Description","Title":"iommufd: Move vevent memory allocation outside spinlock"}]}}}