Linux kernel: block: restore the iterator when rejecting a misaligned bio
- Exploited
- No known exploitation
- Fix
- Fixed in 7.3
- Who is exposed
- Not reported
Summary
In the Linux kernel, the following vulnerability has been resolved:
block: restore the iterator when rejecting a misaligned bio
bio_iov_iter_get_pages() can extract some iovecs before encountering a misaligned one. It releases the pages and rejects the entire bio, but leaves the supplied iterator advanced.
An iomap direct-I/O caller may subsequently reexpand the iterator's byte count and fall back to buffered I/O. The reexpanded count then includes bytes before the iterator's current segment, potentially causing iterate_iovec() to read beyond the imported iovec array.
In a reproducer using an initial empty iovec followed by 10-byte and 1015-byte segments, writev() returned 1015 instead of 1025 and KASAN reported an 8-byte read beyond the nine-element iovec allocation. Saving and restoring the iterator on the rejected-bio path makes writev() return 1025 and eliminates the KASAN report.
Restore the entire iterator rather than reverting a byte count: advancing past an empty segment changes its position without consuming any bytes.
Leave successful and partially accepted bio paths unchanged.
What to do
Upgrade to a fixed version: 7.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99789 (block: restore the iterator when rejecting a misaligned bio), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99789 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 7.2.4, fixed in 7.3
- Linux Linux: versions 7.3
Fixed versions: 7.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99789 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99789 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/3a6381f254ed81d36f3896f61dcd5d830e08861d
- https://git.kernel.org/stable/c/40d070cbb1906896d6fd65c39722d2411830ed9f
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99789
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99789"}.Affected versions
- Linux LinuxFrom 7.2.4 · fixed in 7.3
- Linux Linux7.3
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99789 |
| Record | NVD · CVE-2026-99789 |
| Other links 2 | |
| Link | git.kernel.org · stable/c/3a6381f254ed81d36f3896f61dcd5d830e08861d |
| Link | git.kernel.org · stable/c/40d070cbb1906896d6fd65c39722d2411830ed9f |
Questions about CVE-2026-99789
Is CVE-2026-99789 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99789?
Linux: from 7.2.4 before 7.3. Linux: version 7.3.
Source: cve.now feed data
How do I fix CVE-2026-99789?
Upgrade to a fixed version: 7.3.
Source: cve.now feed data
Related
- CVE-2026-99795cxl/features: Ensure that count is set before access to ent[] __counted_by()
- CVE-2026-99794Bluetooth: L2CAP: Reject signalling responses in invalid states
- CVE-2026-99793Bluetooth: L2CAP: Only accept connection responses to outstanding requests
- CVE-2026-99792smb/server: prevent file publication after tree disconnect
- CVE-2026-99791xfs: improve dirent bounds checking in scrub and repair
- CVE-2026-99790NFSD: stop registering with rpcbind after a failure in listener_set
No corrections so far. Something wrong on this page? Report an error.