CVE-2026-98273

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week

—

EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.

No CVSS published and no exploitation signals yet

CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

x86/kprobes: Fix crash when probing CS CALL instructions

When using eBPF to probe CS CALL instructions within a function, a crash can be triggered.

The eBPF tool probes offset 257 of the __hrtimer_run_queues() function:

<__hrtimer_run_queues+249>: nopl 0x0(%rax,%rax,1) <__hrtimer_run_queues+254>: mov %r14,%rdi <__hrtimer_run_queues+257>: cs call <__x86_indirect_thunk_r12> <__hrtimer_run_queues+263>: mov %eax,%r12d <__hrtimer_run_queues+266>: xchg %ax,%ax <__hrtimer_run_queues+268>: mov %r13,%rdi

Which triggers this crash:

BUG: unable to handle page fault for address: 00000000000f41c9 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI CPU: 1 PID: 0 Comm: swapper/1 Kdump: loaded Tainted: P RIP: 0010:__hrtimer_run_queues+0x106/0x230

Note that __hrtimer_run_queues+0x106 is __hrtimer_run_queues+262, which is at the 6th byte of the above CS CALL instruction. Since the CS CALL instruction occupies 6 bytes, the exception occurred in the middle of that call instruction.

The root cause is that when using eBPF tools to probe in the middle of a function, a kprobe with INT3 is used as the underlying implementation.

During single-step emulation of the original CALL instruction, int3_emulate_call() assumes that the probed CALL instruction is 5 bytes long. However, the actual CS-prefixed CALL instruction occupies 6 bytes, so it constructs an incorrect exception return address. When the CPU returns from the kprobe handler, the next instruction to be executed is at the address of the last byte of that CS CALL instruction. Coincidentally, starting from that address, the CPU fetches and decodes a completely different instruction, which ultimately triggers a kernel crash.

Fix the issue by using the actual instruction length obtained from the instruction decoder when constructing the exception return address, rather than relying on the hardcoded CALL_INSN_SIZE macro.

[ mingo: Refined the changelog ]

CVSS v3: —
EchelonGraph score: Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score: —
EG Risk: —
EPSS PROB: 0.2%
EPSS %ILE: 6th
KEV: Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 6, 2026

References (3)

Vendor Advisories for CVE-2026-98273(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)

Debian:12(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)	every version on: no fix on record	—

Debian:13(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)	every version on: no fix on record	—

Debian:14(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)	every version up to 7.2.8-1: fixed in 7.2.8-1	—

Data Freshness Timeline

(refreshed 16× in last 7d / 21× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-12 14:38 UTCEG score recompute
2026-10-12 03:26 UTCVendor advisory
2026-10-12 03:25 UTCGHSA enrichmentGHSA-c2vj-jp5r-v8vf
2026-10-11 19:10 UTCEG score recompute
2026-10-11 16:25 UTCEG score recompute
2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-11 13:37 UTCEG score recompute
2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-09 06:33 UTCEG score recompute
2026-10-09 06:33 UTCVendor advisory
2026-10-09 06:33 UTCGHSA enrichmentGHSA-c2vj-jp5r-v8vf
2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-06 09:39 UTCGHSA enrichmentGHSA-c2vj-jp5r-v8vf
2026-10-06 09:28 UTCNVD update
2026-10-06 08:54 UTCEG score recompute
2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-98273?

CVE-2026-98273 is a vulnerability whose severity is not yet rated; its CVE record was published on October 6, 2026. In the Linux kernel, the following vulnerability has been resolved: x86/kprobes: Fix crash when probing CS CALL instructions When using eBPF to probe CS CALL instructions within a function, a crash can be triggered. The eBPF tool probes offset 257 of the hrtimerrunqueues() function:…

When was the CVE record for CVE-2026-98273 published?

The CVE record for CVE-2026-98273 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.

Is CVE-2026-98273 actively exploited?

CVE-2026-98273 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).

How do I remediate CVE-2026-98273?

A fix for CVE-2026-98273 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98273 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98273

Explore →

Is Your Infrastructure Affected by CVE-2026-98273?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs

CVE-2026-98273

📅 Published

🔄 Last Modified

🔗 References (3)

📣 Vendor Advisories for CVE-2026-98273(2)