GhostLock-Galaxy

GhostLock-Galaxy English: README.md 本仓库单独维护，是因为当前路线需要 Android shell 权限（通过 adb shell 或 Shizuku 获取）。YuKongA 的原项目 不使用 shell 权限，采用的是另一条执行路线；两者的运行要求和代码路径并不相同， 不能直接互换。 当前支持设备 设备| Kernel ---|--- Samsung Galaxy Z Fold6（SM-F9560 / q6q）| 6.1.145-android14-11-3254009-abF9560ZCS4DZG3 启动时按 uname -r 精确匹配 offse...

EUVD-2025-6283

Malicious code in bioql PyPI...

Astra Linux – Vulnerability found in Linux 6.1, Linux 6.12

In the Linux kernel, the following vulnerabilities have been resolved: powerpc/code-patching: Fixed a KASAN vulnerability by not marking the text patching area as a VMALLOC. Erhard reported the following KASAN vulnerabilities while booting his PowerMac G4 with a KASAN-enabled kernel 6.13-rc6: -...

powerpc/code-patching: Fix KASAN hit by not flagging text patching area as VM_ALLOC

...

DEBIAN-CVE-2025-21866

In the Linux kernel, the following vulnerability has been resolved: powerpc/code-patching: Fix KASAN hit by not flagging text patching area as VMALLOC Erhard reported the following KASAN hit while booting his PowerMac G4 with a KASAN-enabled kernel 6.13-rc6: BUG: KASAN: vmalloc-out-of-bounds in...

CVE-2025-21866

In the Linux kernel, the following vulnerability has been resolved: powerpc/code-patching: Fix KASAN hit by not flagging text patching area as VMALLOC Erhard reported the following KASAN hit while booting his PowerMac G4 with a KASAN-enabled kernel 6.13-rc6: BUG: KASAN: vmalloc-out-of-bounds in...

CVE-2025-21866 powerpc/code-patching: Fix KASAN hit by not flagging text patching area as VM_ALLOC

In the Linux kernel, the following vulnerability has been resolved: powerpc/code-patching: Fix KASAN hit by not flagging text patching area as VMALLOC Erhard reported the following KASAN hit while booting his PowerMac G4 with a KASAN-enabled kernel 6.13-rc6: BUG: KASAN: vmalloc-out-of-bounds in...

CVE-2025-21866

CVE-2025-21866 : In the Linux kernel, PowerPC text patching infrastructure allocated a virtual area and marked it VM_ALLOC, which is inappropriate since that memory is not vmalloc’d and isn’t initialized until __vmalloc_node_range() is called. This caused KASAN: vmalloc-out-of-bounds when booting...