CVE-2026-98655: perf: Require kernel access for text poke events
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 0e26d44b7c64b045adebcf5d614140f811f09752, 357e8a77a501d96c9517f01f4a211eed5e9c9184, 4d8fc6290d14aa9e4c3b620fe3e5dc8ba3bea7e3; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 0e26d44b7c64b045adebcf5d614140f811f09752, 357e8a77a501d96c9517f01f4a211eed5e9c9184, 4d8fc6290d14aa9e4c3b620fe3e5dc8ba3bea7e3; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.9affected
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before 4d8fc6290d14aa9e4c3b620fe3e5dc8ba3bea7e3affected · git
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before c30886396eb1c0e9fdc4296398dea0db0ab37610affected · git
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before 0e26d44b7c64b045adebcf5d614140f811f09752affected · git
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before 8c38cb055f6a9651198780e4e4d5283de4039f79affected · git
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before 8473f44db9f710ea6f8cafb22f2e3ba6cb8ca9a7affected · git
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before e506333d1b9f42f1e402acebf1283af3c44a3809affected · git
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before 677d0b51ac1a0db55d768c4c6399210b3de0795baffected · git
- e17d43b93e544f5016c0251d2074c15568d5d963 and later · before 357e8a77a501d96c9517f01f4a211eed5e9c9184affected · git
- before 5.9not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98652Oct 18, 2026 · KVM: s390: Add missing srcu in kvm_s390_set_irq_state()0Monitor
- ← EarlierCVE-2026-98653Oct 18, 2026 · KVM: s390: Fix _gaccess_shadow_fault()0Monitor
- Later →CVE-2026-98656Oct 18, 2026 · iio: trigger: cancel reenable_work before freeing trigger0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0e26d44b7c64b045adebcf5d614140f811f09752 | Vendor (CNA) |
| Linux Linux | 357e8a77a501d96c9517f01f4a211eed5e9c9184 | Vendor (CNA) |
| Linux Linux | 4d8fc6290d14aa9e4c3b620fe3e5dc8ba3bea7e3 | Vendor (CNA) |
| Linux Linux | 677d0b51ac1a0db55d768c4c6399210b3de0795b | Vendor (CNA) |
| Linux Linux | 8473f44db9f710ea6f8cafb22f2e3ba6cb8ca9a7 | Vendor (CNA) |
| Linux Linux | 8c38cb055f6a9651198780e4e4d5283de4039f79 | Vendor (CNA) |
| Linux Linux | c30886396eb1c0e9fdc4296398dea0db0ab37610 | Vendor (CNA) |
| Linux Linux | e506333d1b9f42f1e402acebf1283af3c44a3809 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/357e8a77a501d96c9517f01f4a211eed5e9c9184
- git.kernel.org/stable/c/4d8fc6290d14aa9e4c3b620fe3e5dc8ba3bea7e3
- git.kernel.org/stable/c/677d0b51ac1a0db55d768c4c6399210b3de0795b
- git.kernel.org/stable/c/8473f44db9f710ea6f8cafb22f2e3ba6cb8ca9a7
- git.kernel.org/stable/c/8c38cb055f6a9651198780e4e4d5283de4039f79
- git.kernel.org/stable/c/c30886396eb1c0e9fdc4296398dea0db0ab37610
- git.kernel.org/stable/c/e506333d1b9f42f1e402acebf1283af3c44a3809
Vendor advisories and official records. Exploit/PoC links are deliberately left out.