17 matches found
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-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...
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...
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...
PT-2026-72576
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock Since dma fence objects can be shared with other subsystems, they may be accessed from hardirq context in those drivers, and we have to take that into...
kernel: writeback: avoid use-after-free after removing device
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdiunregister gets called to stop further writeback and wait for associated delayed work to complete. However, wbinodewritebackend may schedule bandwid...
CVE-2024-47935
Improper Validation of Integrity Check Value vulnerability in TXOne Networks StellarProtect Legacy Mode, StellarEnforce, and Safe Lock allows an attacker to escalate their privileges in the victim’s device. The attacker needs to hijack the DLL file in advance. This issue affects StellarProtect...
CVE-2024-47935
Improper Validation of Integrity Check Value vulnerability in TXOne Networks StellarProtect Legacy Mode, StellarEnforce, and Safe Lock allows an attacker to escalate their privileges in the victim’s device. The attacker needs to hijack the DLL file in advance. This issue affects StellarProtect...
CVE-2024-47935 TXOne Networks StellarProtect (Legacy Mode), StellarEnforce, and Safe Lock Improper Validation of Integrity Check Value Vulnerability
Improper Validation of Integrity Check Value vulnerability in TXOne Networks StellarProtect Legacy Mode, StellarEnforce, and Safe Lock allows an attacker to escalate their privileges in the victim’s device. The attacker needs to hijack the DLL file in advance. This issue affects StellarProtect...
CVE-2024-47935 TXOne Networks StellarProtect (Legacy Mode), StellarEnforce, and Safe Lock Improper Validation of Integrity Check Value Vulnerability
Improper Validation of Integrity Check Value vulnerability in TXOne Networks StellarProtect Legacy Mode, StellarEnforce, and Safe Lock allows an attacker to escalate their privileges in the victim’s device. The attacker needs to hijack the DLL file in advance. This issue affects StellarProtect...
TXOne多款产品 安全漏洞
TXOne StellarProtect and others are products of TXOne Inc.TXOne StellarProtect is an application.TXOne StellarEnforce is an application.TXOne Safe Lock is a security lock application. A security vulnerability exists in a number of TXOne products, which stems from the presence of improper integrit...
PT-2025-6700 · Txone Networks · Stellarprotect +2
Name of the Vulnerable Software and Affected Versions: StellarProtect Legacy Mode versions prior to 3.2 StellarEnforce versions prior to 3.2 Safe Lock versions 3.0.0 through 3.1.1076 Description: The issue is related to improper validation of the integrity check value in TXOne Networks products,...
CVE-2024-47935: Improper Validation of Integrity Check Value
Improper Validation of Integrity Check Value vulnerability in TXOne Networks StellarProtect Legacy Mode, StellarEnforce, and Safe Lock allows an attacker to escalate their privileges in the victim’s device. The attacker needs to hijack the DLL file in advance. This issue affects StellarProtect...
kernel: writeback: avoid use-after-free after removing device
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdiunregister gets called to stop further writeback and wait for associated delayed work to complete. However, wbinodewritebackend may schedule bandwid...
kernel: writeback: avoid use-after-free after removing device
In the Linux kernel, the following vulnerability has been resolved: writeback: avoid use-after-free after removing device When a disk is removed, bdiunregister gets called to stop further writeback and wait for associated delayed work to complete. However, wbinodewritebackend may schedule bandwid...