GHSA-GC5V-Q6X9-GWW4

Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31
VLAI
Details

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 number of zones with 64-bit arithmetic and stores the result in the unsigned int nr_zones field of struct zoned_disk_info, silently truncating counts that exceed 32 bits. The truncated count is later used to size per-zone resources, while the device may still report more zones than fit.

Moreover, sd_zbc_report_zones() counts the reported zones with a signed int zone_idx, which overflows past INT_MAX. Reject devices reporting more than INT_MAX zones at scan time; such a device is not realistic for any medium that exists today, and accepting it produces inconsistent zone bookkeeping.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-98634"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-18T16:17:16Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sd_zbc: Reject disks with too many zones\n\nsd_zbc_read_zones() computes the number of zones with 64-bit arithmetic and\nstores the result in the unsigned int nr_zones field of struct\nzoned_disk_info, silently truncating counts that exceed 32 bits. The\ntruncated count is later used to size per-zone resources, while the device\nmay still report more zones than fit.\n\nMoreover, sd_zbc_report_zones() counts the reported zones with a signed int\nzone_idx, which overflows past INT_MAX. Reject devices reporting more than\nINT_MAX zones at scan time; such a device is not realistic for any medium\nthat exists today, and accepting it produces inconsistent zone bookkeeping.",
  "id": "GHSA-gc5v-q6x9-gww4",
  "modified": "2026-10-18T18:31:57Z",
  "published": "2026-10-18T18:31:57Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98634"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0af16d8be3ec7ff28bb56a0da79c9aed66ac2c3b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3ddf8383b54456f19fd73d3cebed81bd250c7388"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b6ec0f79745967c751c85df373062c8d15e45fc4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d8791ae55d85dfaeafa20ea48365482a0cc5a107"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…