92 matches found
SUSE CVE-2026-98094
In the Linux kernel, the following vulnerability has been resolved: staging: fbtft: make dirtylock IRQ-safe fbtftmkdirty can be reached from the fbcon rendering path while processing printk in hardirq context. Meanwhile, dirtylock is also taken by fbtftdeferredio in workqueue context with local...
UBUNTU-CVE-2026-98094
In the Linux kernel, the following vulnerability has been resolved: staging: fbtft: make dirtylock IRQ-safe fbtftmkdirty can be reached from the fbcon rendering path while processing printk in hardirq context. Meanwhile, dirtylock is also taken by fbtftdeferredio in workqueue context with local...
CVE-2026-98094 staging: fbtft: make dirty_lock IRQ-safe
In the Linux kernel, the following vulnerability has been resolved: staging: fbtft: make dirtylock IRQ-safe fbtftmkdirty can be reached from the fbcon rendering path while processing printk in hardirq context. Meanwhile, dirtylock is also taken by fbtftdeferredio in workqueue context with local...
Linux Distros Unpatched Vulnerability : CVE-2026-98094
"The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - staging: fbtft: make dirtylock IRQ-safe fbtftmkdirty can be reached from the fbcon rendering path while processing printk in hardirq context. Meanwhile,...
PT-2026-98757
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An IRQ lock inversion exists in the fbtft staging driver. The fbtft mkdirty function can be accessed via the fbcon rendering path during printk processing within a hardirq context...
CVE-2026-98094: Undefined Security Weakness
In the Linux kernel, the following vulnerability has been resolved: staging: fbtft: make dirtylock IRQ-safe fbtftmkdirty can be reached from the fbcon rendering path while processing printk in hardirq context. Meanwhile, dirtylock is also taken by fbtftdeferredio in workqueue context with local...
PT-2026-93516
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the media TI VPE component where the vip stop streaming function fails to synchronize the hardirq handler or disable recovery work. This can lead to a use-after-free...
Astra Linux – Vulnerability found in Linux 5.10, Linux 6.1, Linux, Linux 5.15
In the Linux kernel, the following vulnerability has been resolved: BPF, sockmap: Prevent lock inversion deadlock in mapdeleteelem operation. The syzkaller started using corpuses where a BPF tracing program deletes elements from a sockmap/sockhash map. Since BPF tracing programs can be invoked fr...
Astra Linux – Vulnerability in Linux 6.1
In the Linux kernel, the following vulnerability has been resolved: flexproportions: making fpropnewperiod safe from hardirq issues. Bernd reported a deadlock issue in the flexible proportions code, which essentially complained about the following race conditions: runtimersoftirq – we’re in a...
SUSE CVE-2026-72388
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dmafence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...
CVE-2026-80562
CVE-2026-80562 affects the Linux kernel 's gpio: ml-ioh driver. The driver's ioh_irq_type(), ioh_irq_enable(), and ioh_irq_disable() callbacks acquire chip->spinlock via spin_lock_irqsave(), but they are invoked while the caller already holds desc->lock (a raw_spinlock_t) with hardirqs disa...
CVE-2026-80562 gpio: ml-ioh: use raw_spinlock_t for the register lock
In the Linux kernel, the following vulnerability has been resolved: gpio: ml-ioh: use rawspinlockt for the register lock iohirqtype is registered as the irqchip .irqsettype callback and takes chip-spinlock with spinlockirqsave. This callback is reached from setupirq - irqsettrigger -...
Astra Linux – Vulnerability in Linux 5.10
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock. Since DMAfence objects can be shared with other subsystems, they may be accessed from the hardirq context in those drivers. We must take that into accoun...
CVE-2026-72388
A flaw was found in the Linux kernel's drm/panthor component. This vulnerability arises from the incorrect acquisition of fence locks, where an IRQ-safe variant was not consistently used for dmafence objects. Since these objects can be accessed from hard interrupt hardirq context by other drivers...
CVE-2026-72388
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dmafence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...
UBUNTU-CVE-2026-72388
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dmafence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...
CVE-2026-72388
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dmafence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...
EUVD-2026-59287
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dmafence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...
CVE-2026-72388 drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dmafence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...
CVE-2026-72388
The CVE-2026-72388 entry concerns the Linux kernel DRM/Panthor driver. Root cause: when acquiring the dma_fence lock, drivers can be reached from hardirq context, requiring the IRQ-safe variant and a guard-model switch. Affected component is drm/panthor in the kernel’s fence handling; fix involve...