Missing Release of Resource after Effective Lifetime The advisory has been revoked - it doesn't affect any version of package perf (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-PERF-20528959
- published6 Oct 2026
- disclosed17 Sept 2026
Introduced: 17 Sep 2026
CVE-2026-90424 (opens in a new tab)Amendment
The Centos security team deemed this advisory irrelevant for Centos:10.
NVD Description
Note: Versions mentioned in the description apply only to the upstream perf package and not the perf package as distributed by Centos.
In the Linux kernel, the following vulnerability has been resolved:
iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path
tegra241_cmdqv_init_structures() allocates VINTF0 with kzalloc_obj(), inits it, and preallocates its logical VCMDQs. Two of its error paths leak.
When tegra241_cmdqv_init_vintf() fails it returns before VINTF0 reaches the cmdqv->vintfs[] array, so the devres unwind on probe failure cannot reach it; free it directly there.
A later VCMDQ preallocation failure instead leaves VINTF0 published, and so this time the unwind does reach tegra241_cmdqv_remove_vintf(), which then frees it from vintf->hyp_own. But tegra241_vintf_hw_init() sets that flag only afterward, from a HW read-back, so the still-uninited VINTF0 reads as guest-owned and leaks, with mutex_destroy() and ida_destroy() run on fields it never set up.
Decide ownership from vintf->idx instead, the index assigned when its id is allocated: idx 0 is the kernel-owned VINTF0, while idx >= 1 marks a guest VINTF. So the in-kernel free decision in tegra241_cmdqv_remove_vintf() and tegra241_vintf_free_lvcmdq() now keys on idx too, and hyp_own stays a pure HW-readback state.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2536235
- https://access.redhat.com/security/cve/CVE-2026-90424
- https://git.kernel.org/stable/c/1d2271d7df5230e4ce36bdafd17524bd004f3b3f
- https://git.kernel.org/stable/c/417190bde0fda4ee857999a722ca90163fbec587
- https://git.kernel.org/stable/c/f40f3144477314b489e4bc209c06cb51679fe82b
- https://git.kernel.org/stable/c/05a1405d0cba3d8253261b02eb65e5cd3ca09ab3