CVE-2026-89522Hinoki check available

Kernel memory corruption via orphaned async notifier

Published Sep 11, 2026 · Updated Sep 11, 2026

Use-after-free in the IPU7 ISYS driver in Linux 6.17 allows attackers to corrupt kernel notifier-list state during a failed device probe. On the isys_probe() error path, isys_unregister_devices() frees the enclosing ipu7_isys object without unregistering the notifier added by isys_notifier_init(), leaving a stale entry in the global notifier_list. The condition requires a later probe step to fail and the notifier list to be walked again; the public record identifies list corruption and use-after-free but no attacker-controlled trigger or additional impact.

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

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in the IPU7 ISYS driver in Linux 6.17 allows attackers to corrupt kernel notifier-list state during a failed device probe. On the isys_probe() error path, isys_unregister_devices() frees the enclosing ipu7_isys object without unregistering the notifier added by isys_notifier_init(), leaving a stale entry in the global notifier_list. The condition requires a later probe step to fail and the notifier list to be walked again; the public record identifies list corruption and use-after-free but no attacker-controlled trigger or additional impact.

The record

CVE
CVE-2026-89522
Published
Sep 11, 2026
Updated
Sep 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
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.17
  2. Affected versionversion=a516d36bdc3d8373f904af57c95e76d6f921cf1c <2a8dd9fd12f3f6b21207cec8f50c92cd428e6b81
  3. Affected versionversion=a516d36bdc3d8373f904af57c95e76d6f921cf1c <323c411fb63122e8cef5b833032d69d59a838559
  4. Affected versionversion=a516d36bdc3d8373f904af57c95e76d6f921cf1c <d7f48aa7d60c65d3e6d5312c27f17d5525a245fb

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=6.17; version=a516d36bdc3d8373f904af57c95e76d6f921cf1c <2a8dd9fd12f3f6b21207cec8f50c92cd428e6b81; version=a516d36bdc3d8373f904af57c95e76d6f921cf1c <323c411fb63122e8cef5b833032d69d59a838559; version=a516d36bdc3d8373f904af57c95e76d6f921cf1c <d7f48aa7d60c65d3e6d5312c27f17d5525a245fb

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)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

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