In the Linux kernel, the following vulnerability has been resolved: scsi: sd_zbc: Reject disks with too many zones sd_zbc_read_zones() computes the… (CVE-2026-98634)
Description
A vulnerability in the Linux kernel's SCSI subsystem (sd_zbc) was resolved that involved improper handling of disks reporting an excessively large number of zones. The function sd_zbc_read_zones() used 64-bit arithmetic but stored the result in a 32-bit unsigned integer, causing silent truncation of zone counts exceeding 32 bits. Additionally, sd_zbc_report_zones() used a signed integer to count zones, which could overflow if the device reported more than INT_MAX zones. The fix rejects devices reporting more than INT_MAX zones at scan time, as such devices are unrealistic and cause inconsistent zone bookkeeping.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's scsi: sd_zbc component arises from integer truncation and overflow issues when handling disks with a very large number of zones. Specifically, sd_zbc_read_zones() computes the number of zones using 64-bit arithmetic but stores the count in a 32-bit unsigned int, truncating values that exceed 32 bits. This truncated count is then used to allocate per-zone resources, which can lead to inconsistencies if the actual number of zones is larger. Furthermore, sd_zbc_report_zones() uses a signed int to count zones, which overflows if the zone count exceeds INT_MAX. The vulnerability is mitigated by rejecting devices that report more than INT_MAX zones during scanning, preventing inconsistent zone bookkeeping. This issue affects the Linux kernel's SCSI zoned block device handling and has been resolved by rejecting unrealistic devices at scan time.
Potential Impact
Devices reporting an excessively large number of zones can cause silent truncation and integer overflow in zone counting, leading to inconsistent zone bookkeeping within the kernel. This could potentially cause incorrect resource allocation or kernel misbehavior when handling such devices. However, devices with more than INT_MAX zones are not realistic for current storage media, limiting practical impact.
Mitigation Recommendations
The vulnerability has been resolved by rejecting devices that report more than INT_MAX zones at scan time. No further action is required for realistic devices. Users should ensure their Linux kernel is updated to a version containing this fix to prevent inconsistent zone bookkeeping with malformed or unrealistic devices.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gc5v-q6x9-gww4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-98634"]
Threat ID: 6ad520ad2cdf04f656993a67
Added to database: 10/18/2026, 19:40:29 UTC
Last enriched: 10/18/2026, 21:34:04 UTC
Last updated: 10/19/2026, 00:08:18 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.