rust: pwm: Fix potential memory leak on init error
In the Linux kernel, the following vulnerability has been resolved: rust: pwm: Fix potential memory leak on init error When initializing a PWM chip using pwmchip_alloc(), the allocated device owns an initial reference that must be released on all error paths. If __pinned_init() were to fail, the allocated pwm_chip would currently leak because the error path returns without calling pwmchip_put().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.19.4
- CVEs
- CVE-2026-45926
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 05:26 UTC · Revision 1
Source evidence
rust: pwm: Fix potential memory leak on init error
core-osv · Original sourcePublished 27 May 2026, 12:17 UTC
In the Linux kernel, the following vulnerability has been resolved: rust: pwm: Fix potential memory leak on init error When initializing a PWM chip using pwmchip_alloc(), the allocated device owns an initial reference that must be released on all error paths. If __pinned_init() were to fail, the allocated pwm_chip would currently leak because the error path returns without calling pwmchip_put().
osv:CVE-2026-45926
Kernel
Fixed versions: 6.19.4
Complete source record
{
"id": "2dfefc702268ce19135ff94bf79a7d286b2f7eca3c54aec4bdc3decadc29774d",
"url": "https://osv.dev/vulnerability/CVE-2026-45926",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "rust: pwm: Fix potential memory leak on init error",
"summary": "In the Linux kernel, the following vulnerability has been resolved: rust: pwm: Fix potential memory leak on init error When initializing a PWM chip using pwmchip_alloc(), the allocated device owns an initial reference that must be released on all error paths. If __pinned_init() were to fail, the allocated pwm_chip would currently leak because the error path returns without calling pwmchip_put().",
"evidence": "osv:CVE-2026-45926",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.19.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-45926",
"aliases": [
"CVE-2026-45926"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7b3dce814a15bc5d9fb6124cd945291012c4ebb9"
},
{
"fixed": "baa8b7097d9cc68ff85819cf683972a58c2ce32b"
},
{
"fixed": "a2633dc243c35754a0c2270131d8a199c987c9bf"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45926.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45926.json"
}
}
],
"modified": "2026-10-28T02:30:26.476221638Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/a2633dc243c35754a0c2270131d8a199c987c9bf",
"https://git.kernel.org/stable/c/baa8b7097d9cc68ff85819cf683972a58c2ce32b",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45926.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-45926",
"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/2026/45xxx/CVE-2026-45926.json"
}
},
"related_cves": [
{
"value": "CVE-2026-45926",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 492688,
"published_at": "2026-05-27T12:17:45.351+00:00"
}