driver core: class: Fix wild pointer dereferences in API class_dev_iter_next()
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().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.13, 6.13.2, 6.6.76
- CVEs
- CVE-2025-21810
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 14:31 UTC · Revision 1
Source evidence
driver core: class: Fix wild pointer dereferences in API class_dev_iter_next()
core-osv · Original sourcePublished 27 Feb 2025, 20:01 UTC
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().
osv:CVE-2025-21810
Kernel
Fixed versions: 6.6.76, 6.12.13, 6.13.2
Complete source record
{
"id": "a87c2b2607838fcffe5a46efa9d69c66ccbb2324feb702b7b6379d1e8f07165e",
"url": "https://osv.dev/vulnerability/CVE-2025-21810",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "driver core: class: Fix wild pointer dereferences in API class_dev_iter_next()",
"summary": "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().",
"evidence": "osv:CVE-2025-21810",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.76",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.13",
"evidence": "/affected/1/ranges"
},
{
"value": "6.13.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2025-21810",
"aliases": [
"CVE-2025-21810"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7b884b7f24b42fa25e92ed724ad82f137610afaf"
},
{
"fixed": "f4b9bc823b0cfdebfed479c0e87d6939c7562e87"
},
{
"fixed": "1614e75d1a1b63db6421c7a4bf37004720c7376c"
},
{
"fixed": "5c504e9767b947cf7d4e29b811c0c8b3c53242b7"
},
{
"fixed": "e128f82f7006991c99a58114f70ef61e937b1ac1"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-21810.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.4.0"
},
{
"fixed": "6.6.76"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.13"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.13.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-21810.json"
}
}
],
"modified": "2026-10-28T02:30:51.365066316Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1614e75d1a1b63db6421c7a4bf37004720c7376c",
"https://git.kernel.org/stable/c/5c504e9767b947cf7d4e29b811c0c8b3c53242b7",
"https://git.kernel.org/stable/c/e128f82f7006991c99a58114f70ef61e937b1ac1",
"https://git.kernel.org/stable/c/f4b9bc823b0cfdebfed479c0e87d6939c7562e87",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21810.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-21810",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21810.json"
}
},
"related_cves": [
{
"value": "CVE-2025-21810",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 519640,
"published_at": "2025-02-27T20:01:01.63+00:00"
}