CVE-2026-99789Public exploit

Kernel memory overread via unrestored I/O iterator

Published Nov 20, 2026 · Updated Nov 20, 2026

Out-of-bounds reading in Linux 7.3 block I/O allows local users to trigger a kernel memory overread via crafted writev() calls. In block/bio.c, bio_iov_iter_get_pages() rejects a misaligned bio without restoring the advanced iterator, so iomap buffered-I/O fallback reexpands its count beyond the remaining iovec array. Triggering requires access to the affected file-I/O path; the reported result is an incorrect write length and a KASAN-detected overread, not demonstrated data disclosure or privilege escalation.

CVSS severityUnavailable
Unscored
EPSS probability0.14%
Next 30 days · Nov 22, 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.

Contact us

Summary

What happened

Out-of-bounds reading in Linux 7.3 block I/O allows local users to trigger a kernel memory overread via crafted writev() calls. In block/bio.c, bio_iov_iter_get_pages() rejects a misaligned bio without restoring the advanced iterator, so iomap buffered-I/O fallback reexpands its count beyond the remaining iovec array. Triggering requires access to the affected file-I/O path; the reported result is an incorrect write length and a KASAN-detected overread, not demonstrated data disclosure or privilege escalation.

The record

CVE
CVE-2026-99789
Published
Nov 20, 2026
Updated
Nov 20, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Nov 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Nov 20, 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=14b007e178811db72fbb1ebb3535160db6ec1e6a <3a6381f254ed81d36f3896f61dcd5d830e08861d
  2. Affected versionversion=14b007e178811db72fbb1ebb3535160db6ec1e6a <40d070cbb1906896d6fd65c39722d2411830ed9f
  3. Affected versionversion=7.2.4 <7.3
  4. Affected versionversion=7.3
  5. Affected versionversion=d44a97a3b1c00cc571245124e23e5ceb0a0225a0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=14b007e178811db72fbb1ebb3535160db6ec1e6a <3a6381f254ed81d36f3896f61dcd5d830e08861d; version=14b007e178811db72fbb1ebb3535160db6ec1e6a <40d070cbb1906896d6fd65c39722d2411830ed9f; version=7.2.4 <7.3; version=7.3; version=d44a97a3b1c00cc571245124e23e5ceb0a0225a0

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.

Activity data is delayed. The latest report is Sep 28, 2026.

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

No observations available

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

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

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

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us