Количество 4
Количество 4
CVE-2026-90316
(In the Linux kernel, the following vulnerability has been resolved: d ...)
CVE-2026-90316
In the Linux kernel, the following vulnerability has been resolved: drm/omap: dsi: Do not copy isr table To be able to unregister stuff from isrs, the corresponding table was copied. Nobody seems to unregister stuff that way, so it does not help. But there are stack-allocated objects passed to these isrs giving chances of UAF of these objects if irqs are unregistered while they are handled, so better do not copy that table.
CVE-2026-90316
In the Linux kernel, the following vulnerability has been resolved: d ...
GHSA-gxgq-hfgr-pjxw
In the Linux kernel, the following vulnerability has been resolved: drm/omap: dsi: Do not copy isr table To be able to unregister stuff from isrs, the corresponding table was copied. Nobody seems to unregister stuff that way, so it does not help. But there are stack-allocated objects passed to these isrs giving chances of UAF of these objects if irqs are unregistered while they are handled, so better do not copy that table.
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2026-90316 (In the Linux kernel, the following vulnerability has been resolved: d ...) | CVSS3: 7.8 | 0% Низкий | 4 дня назад |
 | CVE-2026-90316 In the Linux kernel, the following vulnerability has been resolved: drm/omap: dsi: Do not copy isr table To be able to unregister stuff from isrs, the corresponding table was copied. Nobody seems to unregister stuff that way, so it does not help. But there are stack-allocated objects passed to these isrs giving chances of UAF of these objects if irqs are unregistered while they are handled, so better do not copy that table. | CVSS3: 7.8 | 0% Низкий | 4 дня назад |
| CVE-2026-90316 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 7.8 | 0% Низкий | 4 дня назад |
| GHSA-gxgq-hfgr-pjxw In the Linux kernel, the following vulnerability has been resolved: drm/omap: dsi: Do not copy isr table To be able to unregister stuff from isrs, the corresponding table was copied. Nobody seems to unregister stuff that way, so it does not help. But there are stack-allocated objects passed to these isrs giving chances of UAF of these objects if irqs are unregistered while they are handled, so better do not copy that table. | CVSS3: 7.8 | 0% Низкий | 4 дня назад |
Уязвимостей на страницу