CVE-2026-89581

Kernel panic via misencoded extended BPF register

Published Sep 11, 2026 · Updated Sep 11, 2026

Incorrect register encoding in the x86 BPF JIT in Linux 6.10 allows attackers to cause a kernel panic via a GCC-built BPF program. The per-CPU address MOV uses add_1mod(), which sets REX.B instead of REX.R, so an extended ModRM.reg destination loses its high bit and the address is adjusted in the wrong register. The condition requires the x86 BPF JIT and compiler output that keeps per-CPU addresses in extended registers; dereferencing the unadjusted pointer can fault, while other aliases can corrupt frame or argument registers.

CVSS severityUnavailable
Unscored
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect register encoding in the x86 BPF JIT in Linux 6.10 allows attackers to cause a kernel panic via a GCC-built BPF program. The per-CPU address MOV uses add_1mod(), which sets REX.B instead of REX.R, so an extended ModRM.reg destination loses its high bit and the address is adjusted in the wrong register. The condition requires the x86 BPF JIT and compiler output that keeps per-CPU addresses in extended registers; dereferencing the unadjusted pointer can fault, while other aliases can corrupt frame or argument registers.

The record

CVE
CVE-2026-89581
Published
Sep 11, 2026
Updated
Sep 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 11, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.10
  2. Affected versionversion=7bdbf7446305cb65c510c16d57cde82bc76b234a <5bbbce02e500d47d8e259a45be5a7be9741d0533
  3. Affected versionversion=7bdbf7446305cb65c510c16d57cde82bc76b234a <638bc3aada8ecdece184d5c15b100d489c9cccd7
  4. Affected versionversion=7bdbf7446305cb65c510c16d57cde82bc76b234a <6886642414f59f928728802dc2c972a9859e6310
  5. Affected versionversion=7bdbf7446305cb65c510c16d57cde82bc76b234a <6a19b18d458881bf3269a357cc6dc6db5eef4369

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=6.10; version=7bdbf7446305cb65c510c16d57cde82bc76b234a <5bbbce02e500d47d8e259a45be5a7be9741d0533; version=7bdbf7446305cb65c510c16d57cde82bc76b234a <638bc3aada8ecdece184d5c15b100d489c9cccd7; version=7bdbf7446305cb65c510c16d57cde82bc76b234a <6886642414f59f928728802dc2c972a9859e6310; version=7bdbf7446305cb65c510c16d57cde82bc76b234a <6a19b18d458881bf3269a357cc6dc6db5eef4369

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo