Review reviewHigh

CVE-2026-52992

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: fs/adfs: validate nzones in adfs_validate_bblk() Reject ADFS disc records with a zero zone count during boot block validation, before the disc record is used. When nzones is 0, adfs_read_map() passes it to kmalloc_array(0, ...) which returns ZERO_SIZE_PTR, and adfs_map_layout() then writes to dm[-1], causing an out-of-bounds write before the allocated buffer. adfs_validate_dr0() already rejects nzones != 1 for old-format images. Add the equivalent check to adfs_validate_bblk() for new-format images so that a crafted image w...

CVSS
7.8
EPSS
0.14%
3.68% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: fs/adfs: validate nzones in adfs_validate_bblk() Reject ADFS disc records with a zero zone count during boot block validation, before the disc record is used. When nzones is 0, adfs_read_map() passes it to kmalloc_array(0, ...) which returns ZERO_SIZE_PTR, and adfs_map_layout() then writes to dm[-1], causing an out-of-bounds write before the allocated buffer. adfs_validate_dr0() already rejects nzones != 1 for old-format images. Add the equivalent check to adfs_validate_bblk() for new-format images so that a crafted image w...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < 33aafd2418a59c96c0389d47ea09026661fa9ec6, >= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < 1f0ed0f57f0fc87e46fe19a05435c214dc464be2, >= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < 6ff8cca5cdb4f2e0ea6d28ecd78479dd3f221ebc, >= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < a11372a8b1ceaa5e950a84b3b5fbf8228f25e277, >= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < 1586bd2d2fb436a26df20a70e78b000d34a7d159, >= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < a3fd5dc1c7b0aae947a67dc2e2c037d57557a4de, >= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < 60d82592ac8b5637fbed871381eb0a16df0a492e, >= f6f14a0d71b0773a1d4147d1a3c33d537cd213ab < dd9d3e16c2d5fa166e13dce07413be51f42c8f5d, >= 5.6, >= 5.6 < 5.10.258, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787