CVE-2026-97573Hinoki check available

Unspecified impact via ignored RX allocation failure

Published Sep 25, 2026 · Updated Sep 25, 2026

Improper error handling in Linux 5.10 allows attackers to cause unspecified impact after a bnxt_en receive-ring allocation failure. bnxt_rx_ring_reset ignores an allocation error, re-enables TPA with partially unallocated rx_tpa entries, and can give the device a zero DMA address. The condition requires bnxt_en hardware, TPA, and an allocation failure during an RX ring reset; the public record does not state the resulting impact.

CVSS severityUnavailable
Unscored
EPSS probability0.60%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Improper error handling in Linux 5.10 allows attackers to cause unspecified impact after a bnxt_en receive-ring allocation failure. bnxt_rx_ring_reset ignores an allocation error, re-enables TPA with partially unallocated rx_tpa entries, and can give the device a zero DMA address. The condition requires bnxt_en hardware, TPA, and an allocation failure during an RX ring reset; the public record does not state the resulting impact.

The record

CVE
CVE-2026-97573
Published
Sep 25, 2026
Updated
Sep 25, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 25, 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.10
  2. Affected versionversion=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <1a3670b6a6b5679fe56c5890157b344f091e64f8
  3. Affected versionversion=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <4a17c73c83798c2fa9c7920ad5a98803adce3e01
  4. Affected versionversion=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <8b2fd5c0aeda935294159206af9d6179282d425a
  5. Affected versionversion=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <961e2a17c5e3559b3f8654d2daabdd25a42e770a

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=5.10; version=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <1a3670b6a6b5679fe56c5890157b344f091e64f8; version=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <4a17c73c83798c2fa9c7920ad5a98803adce3e01; version=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <8b2fd5c0aeda935294159206af9d6179282d425a; version=8fbf58e17dce8f250dda9ad6b0a49b3041f0af14 <961e2a17c5e3559b3f8654d2daabdd25a42e770a

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.

Activity data is delayed. The latest report is Sep 28, 2026.

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

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

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

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started