CVE-2026-72030

Kernel memory corruption via invalid ATA range count

Published Aug 15, 2026 · Updated Aug 15, 2026

Buffer overflow in the Linux kernel allows physically proximate attackers to corrupt memory via invalid ATA range metadata. ata_dev_config_cpr() trusts buf[0] and walks 32-byte descriptors without bounding the count to the returned log or fixed response buffer. Triggering requires an ATA device that reports an oversized count; published material establishes out-of-bounds kernel reads and writes but no further consequence.

CVSS severityUnavailable
Unscored
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Buffer overflow in the Linux kernel allows physically proximate attackers to corrupt memory via invalid ATA range metadata. ata_dev_config_cpr() trusts buf[0] and walks 32-byte descriptors without bounding the count to the returned log or fixed response buffer. Triggering requires an ATA device that reports an oversized count; published material establishes out-of-bounds kernel reads and writes but no further consequence.

The record

CVE
CVE-2026-72030
Published
Aug 15, 2026
Updated
Aug 15, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1200
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 15, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 15, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.16
  2. Affected versionversion=fe22e1c2f705676a705d821301fc52eecc2fe055 <4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4
  3. Affected versionversion=fe22e1c2f705676a705d821301fc52eecc2fe055 <4cb4b4dd8853c4ab3057efe238b2c34277772176
  4. Affected versionversion=fe22e1c2f705676a705d821301fc52eecc2fe055 <533a0b940f901c15e5cbbd4b5d66e871c209e8ce
  5. Affected versionversion=fe22e1c2f705676a705d821301fc52eecc2fe055 <b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1
  6. Affected versionversion=fe22e1c2f705676a705d821301fc52eecc2fe055 <d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.16; version=fe22e1c2f705676a705d821301fc52eecc2fe055 <4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4; version=fe22e1c2f705676a705d821301fc52eecc2fe055 <4cb4b4dd8853c4ab3057efe238b2c34277772176; version=fe22e1c2f705676a705d821301fc52eecc2fe055 <533a0b940f901c15e5cbbd4b5d66e871c209e8ce; version=fe22e1c2f705676a705d821301fc52eecc2fe055 <b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1; version=fe22e1c2f705676a705d821301fc52eecc2fe055 <d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1200Hardware Additions

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo