CVE-2025-21810

Source
https://nvd.nist.gov/vuln/detail/CVE-2025-21810
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-21810.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-21810
Downstream
Related
Published
2025-02-27T20:16:03Z
Modified
2025-03-10T05:00:05Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved:

driver core: class: Fix wild pointer dereferences in API classdeviter_next()

There are a potential wild pointer dereferences issue regarding APIs classdeviter_(init|next|exit)(), as explained by below typical usage:

// All members of @iter are wild pointers. struct classdeviter iter;

// classdeviterinit(@iter, @class, ...) checks parameter @class for // potential classtosubsys() 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 classdeviternext(@iter) even if // @iter still contains wild pointers. classdeviter_init(&iter, ...);

// Dereference these wild pointers in @iter here once suffer the error. while (dev = classdeviter_next(&iter)) { ... };

// Also dereference these wild pointers here. classdeviter_exit(&iter);

Actually, all callers of these APIs have such usage pattern in kernel tree. Fix by: - Initialize output parameter @iter by memset() in classdeviterinit() and give callers prompt by prcrit() for the error. - Check if @iter is valid in classdeviter_next().

References

Affected packages

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.12.13-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}