CVE-2026-97972Hinoki check available

Kernel resource leak via unreleased MDIO node reference

Published Sep 25, 2026 · Updated Sep 25, 2026

Resource leak in the Linux kernel 6.13 macb driver allows local administrators to accumulate device-tree node references. On each successful macb_mii_init() probe, of_get_child_by_name() increments the mdio child reference, but the success path omits of_node_put() after macb_mdiobus_register() takes its own reference. Triggering requires repeated successful probes of MACB hardware with an mdio child; the observed consequence is a growing reference-count leak during overlay removal.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
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

Resource leak in the Linux kernel 6.13 macb driver allows local administrators to accumulate device-tree node references. On each successful macb_mii_init() probe, of_get_child_by_name() increments the mdio child reference, but the success path omits of_node_put() after macb_mdiobus_register() takes its own reference. Triggering requires repeated successful probes of MACB hardware with an mdio child; the observed consequence is a growing reference-count leak during overlay removal.

The record

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

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=6.13
  2. Affected versionversion=8a6631f1cece09047fa44608d21d520ca65ce7d8 <382a373d9ea7a6ac4de9c022385b6217f65ae3cc
  3. Affected versionversion=8a6631f1cece09047fa44608d21d520ca65ce7d8 <5fba30080d298edb742396073372385c961578d3
  4. Affected versionversion=8a6631f1cece09047fa44608d21d520ca65ce7d8 <7d60dc7ff85b73a2119d582ca2d4456b30960380

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

The Linux Kernel Organization · Linuxversion=6.13; version=8a6631f1cece09047fa44608d21d520ca65ce7d8 <382a373d9ea7a6ac4de9c022385b6217f65ae3cc; version=8a6631f1cece09047fa44608d21d520ca65ce7d8 <5fba30080d298edb742396073372385c961578d3; version=8a6631f1cece09047fa44608d21d520ca65ce7d8 <7d60dc7ff85b73a2119d582ca2d4456b30960380

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)
Vectorlocal
Privilegesadmin
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