Bug 2554929 (CVE-2026-98635) - CVE-2026-98635 kernel: scsi: block: Fix zones_cond out-of-bounds write on zone report
Summary: CVE-2026-98635 kernel: scsi: block: Fix zones_cond out-of-bounds write on zon...
Keywords:
Status: NEW
Alias: CVE-2026-98635
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-18 15:33 UTC by OSIDB Bzimport
Modified: 2026-10-21 15:47 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-18 15:33:21 UTC
In the Linux kernel, the following vulnerability has been resolved:

scsi: block: Fix zones_cond out-of-bounds write on zone report

blk_revalidate_disk_zones() sizes the zones_cond array from the disk
capacity and zone size, but the index used by blk_revalidate_zone_cond()
comes from the device-driven report_zones() walk and is never checked
against the array size. A device reporting more zones than fit the array
makes blk_zone_set_cond() write out of bounds.

One way to reach this is a zone count exceeding 32 bits: both
blk_revalidate_zone_args.nr_zones and struct zoned_disk_info.nr_zones are
unsigned int, so a disk advertising more than UINT_MAX zones (e.g.  2^32 +
1024 zones of one 512-byte logical block) gets its zone count truncated to
a small value, undersizing the array while the report walk keeps counting
upward.

Check the index against the array size before storing the zone condition,
and refuse to revalidate when the zone count does not fit 32 bits.


Note You need to log in before you can comment on or make changes to this bug.