Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98888: arm64: kprobes: Allow reentering kprobes while single-stepping

—No exploit Fix available

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.18% (FIRST EPSS).
  • Fixed version: Linux Linux 1f342b3e44c3035a837b53b217d816f7511c0d0a, 23f851ac0078a908bf3422d6467ebc1db5828c46, 68774caca799e9695db56d426c69acebd041c2ed; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1f342b3e44c3035a837b53b217d816f7511c0d0a, 23f851ac0078a908bf3422d6467ebc1db5828c46, 68774caca799e9695db56d426c69acebd041c2ed; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.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: arm64: kprobes: Allow reentering kprobes while single-stepping A kprobe can be hit while another kprobe is in KPROBE_HIT_SS state. This can happen when tracing or perf code runs from the debug exception path while the first kprobe is preparing or executing its out-of-line single-step instruction. Currently arm64 treats a kprobe hit in KPROBE_HIT_SS as unrecoverable, the same as a hit in KPROBE_REENTER. This is too strict. A hit in KPROBE_HIT_SS is still a one-level reentry and can be handled by saving the current kprobe state and setting up single-step for the new probe, just like reentry from KPROBE_HIT_ACTIVE or KPROBE_HIT_SSDONE. The truly unrecoverable case is hitting another kprobe while already in KPROBE_REENTER, because the reentry save area has already been consumed. Move KPROBE_HIT_SS to the recoverable reentry cases and leave KPROBE_REENTER as the unrecoverable nested reentry case. This change also requires saving saved_irqflag in struct prev_kprobe. When a nested kprobe calls kprobes_save_local_irqflag(), it overwrites kcb->saved_irqflag with the currently masked DAIF value, losing the outer kprobe's original DAIF state. Without this fix, when the outer kprobe's single-step finishes, kprobes_restore_local_irqflag() applies the wrong DAIF mask and leaves interrupts permanently disabled. Extend struct prev_kprobe with a saved_irqflag field and save/restore it alongside kp and status. This ensures the outer kprobe's original interrupt state is preserved across reentry. This mirrors the x86 fix in commit 6a5022a56ac3 ("kprobes/x86: Allow to handle reentered kprobe on single-stepping").

Published
Oct 23, 2026
Updated
Oct 26, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2026-98888

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

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 help

Affected 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

    • 4.8affected
    • 2dd0e8d2d2a157dbc83295a78336c2217110f2f8 and later · before bb0fe9121aa0824211aafa33c7d0151fd25ddb75affected · git
    • 2dd0e8d2d2a157dbc83295a78336c2217110f2f8 and later · before f96a0606de6bcc8d937b80e6470fd7a174c17e26affected · git
    • 2dd0e8d2d2a157dbc83295a78336c2217110f2f8 and later · before 1f342b3e44c3035a837b53b217d816f7511c0d0aaffected · git
    • 2dd0e8d2d2a157dbc83295a78336c2217110f2f8 and later · before c8e84e292ed4cfc199824146da71bb4397b02a1faffected · git
    • 2dd0e8d2d2a157dbc83295a78336c2217110f2f8 and later · before 68774caca799e9695db56d426c69acebd041c2edaffected · git
    • 2dd0e8d2d2a157dbc83295a78336c2217110f2f8 and later · before a21bf9cb893126e8d9730995708d0be5eb167652affected · git
    • 2dd0e8d2d2a157dbc83295a78336c2217110f2f8 and later · before 23f851ac0078a908bf3422d6467ebc1db5828c46affected · git
    • before 4.8not affected · semver
    • 5.10.271 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98886Oct 23, 2026 · drm/gma500: return errors from Oaktrail HDMI I2C reads
    0Monitor
  • ← EarlierCVE-2026-98887Oct 23, 2026 · wifi: mac80211_hwsim: reject undersized HWSIM_ATTR_TX_INFO
    0Monitor
  • Later →CVE-2026-98889Oct 23, 2026 · wifi: iwlwifi: mvm: fix sched scan IE sizing
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1f342b3e44c3035a837b53b217d816f7511c0d0aVendor (CNA)
Linux Linux23f851ac0078a908bf3422d6467ebc1db5828c46Vendor (CNA)
Linux Linux68774caca799e9695db56d426c69acebd041c2edVendor (CNA)
Linux Linuxa21bf9cb893126e8d9730995708d0be5eb167652Vendor (CNA)
Linux Linuxbb0fe9121aa0824211aafa33c7d0151fd25ddb75Vendor (CNA)
Linux Linuxc8e84e292ed4cfc199824146da71bb4397b02a1fVendor (CNA)
Linux Linuxf96a0606de6bcc8d937b80e6470fd7a174c17e26Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.159.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package 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.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 13, 2026+21 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records