What’s Vulnerable › Vulnerabilities
CVE-2026-98655: perf: Require kernel access for text poke events
- Severity: unknown
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-18 · updated 2026-10-30
Description
In the Linux kernel, the following vulnerability has been resolved: perf: Require kernel access for text poke events Perf events with exclude_kernel=1 can be opened without kernel perf access. However, exclude_kernel does not suppress text-poke sideband records. Every PERF_RECORD_TEXT_POKE is marked PERF_RECORD_MISC_KERNEL and contains a raw kernel instruction address. An unprivileged task can therefore open and mmap a task-local software event with text_poke=1. Both opening a count-only tracepoint event and configuring UDP GRO for ESP-in-UDP cause updates to inline static calls; the observer receives the relocated addresses of the modified instructions. For a known kernel image, any such address reveals the runtime kernel text base despite KASLR. Call perf_allow_kernel() whenever attr.text_poke is set, regardless of exclude_kernel. Events that neither monitor kernel execution nor request text-poke records retain their existing permissions.
Affected products
- Linux: 5.9 — fixed in 7.3
How to fix
Upgrade to a fixed version: Linux 7.3. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/0e26d44b7c64b045adebcf5d614140f811f09752
- https://git.kernel.org/stable/c/357e8a77a501d96c9517f01f4a211eed5e9c9184
- https://git.kernel.org/stable/c/4d8fc6290d14aa9e4c3b620fe3e5dc8ba3bea7e3
- https://git.kernel.org/stable/c/677d0b51ac1a0db55d768c4c6399210b3de0795b
- https://git.kernel.org/stable/c/8473f44db9f710ea6f8cafb22f2e3ba6cb8ca9a7
- https://git.kernel.org/stable/c/8c38cb055f6a9651198780e4e4d5283de4039f79
- https://git.kernel.org/stable/c/c30886396eb1c0e9fdc4296398dea0db0ab37610
- https://git.kernel.org/stable/c/e506333d1b9f42f1e402acebf1283af3c44a3809
Get alerted when CVE-2026-98655 or the next vulnerability affects your stack