ALSA: caiaq: Handle probe errors properly
In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Handle probe errors properly The probe procedure of setup_card() in caiaq driver doesn't treat the error cases gracefully, e.g. the error from snd_card_register() calls snd_card_free() but continues. This would lead to a UAF for the further calls like snd_usb_caiaq_control_init(), as Berk suggested in another patch in the link below. However, the problem is not only that; in general, this function drops the all error handlings (as it's a void function) although its caller can propagate an error to snd_probe(), which eventually calls snd_card_free() as a proper error path. That said, we should treat each error case in setup_card(), and just return the error code promptly, which is then handled later as a fatal error in snd_probe(). This patch achieves it by changing the setup_card() to return an error code. Also, the superfluous snd_card_free() call is removed, too. Note that card->private_free can be set still safely at returning an error. All called functions in card_free() have checks of the unassigned resources or NULL checks.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.258, 5.15.209, 6.1.175, 6.12.86, 6.18.27, 6.6.140, 7.0.4
- CVEs
- CVE-2026-46004
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 14:46 UTC · Revision 1
Source evidence
In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Handle probe errors properly The probe procedure of setup_card() in caiaq driver doesn't treat the error cases gracefully, e.g. the error from snd_card_register() calls snd_card_free() but continues. This would lead to a UAF for the further calls like snd_usb_caiaq_control_init(), as Berk suggested in another patch in the link below. However, the problem is not only that; in general, this function drops the all error handlings (as it's a void function) although its caller can propagate an error to snd_probe(), which eventually calls snd_card_free() as a proper error path. That said, we should treat each error case in setup_card(), and just return the error code promptly, which is then handled later as a fatal error in snd_probe(). This patch achieves it by changing the setup_card() to return an error code. Also, the superfluous snd_card_free() call is removed, too. Note that card->private_free can be set still safely at returning an error. All called functions in card_free() have checks of the unassigned resources or NULL checks.
osv:CVE-2026-46004
Kernel
Fixed versions: 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4
Complete source record
{
"id": "850650c9e7da78df0c22bca7e81b65c99a1521eb25d5c118194e5c649aa19064",
"url": "https://osv.dev/vulnerability/CVE-2026-46004",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ALSA: caiaq: Handle probe errors properly",
"summary": "In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Handle probe errors properly The probe procedure of setup_card() in caiaq driver doesn't treat the error cases gracefully, e.g. the error from snd_card_register() calls snd_card_free() but continues. This would lead to a UAF for the further calls like snd_usb_caiaq_control_init(), as Berk suggested in another patch in the link below. However, the problem is not only that; in general, this function drops the all error handlings (as it's a void function) although its caller can propagate an error to snd_probe(), which eventually calls snd_card_free() as a proper error path. That said, we should treat each error case in setup_card(), and just return the error code promptly, which is then handled later as a fatal error in snd_probe(). This patch achieves it by changing the setup_card() to return an error code. Also, the superfluous snd_card_free() call is removed, too. Note that card->private_free can be set still safely at returning an error. All called functions in card_free() have checks of the unassigned resources or NULL checks.",
"evidence": "osv:CVE-2026-46004",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.258",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.209",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.175",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.140",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.86",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.27",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-46004",
"aliases": [
"CVE-2026-46004"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8e3cd08ed8e590952aa9a656758cb24d4ba898f8"
},
{
"fixed": "da938aa9fc7826901921dcea225948ab21a97e45"
},
{
"fixed": "09616e25f502080ba684fc7fcf959d1376ab756d"
},
{
"fixed": "b956e48371f2ff72b76be9a829800ecec963bd45"
},
{
"fixed": "f537e3ad69609f6924a4db6b4a7f6561f5288bdd"
},
{
"fixed": "6251e3e256337a30160ef59ab1580dde4d1acd28"
},
{
"fixed": "e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056"
},
{
"fixed": "096dd8519cf2f768e9e14f224b627f7aaee1a9c5"
},
{
"fixed": "28abd224db4a49560b452115bca3672a20e45b2f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46004.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "2.6.25"
},
{
"fixed": "5.10.258"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.209"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.175"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.140"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.86"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.27"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46004.json"
}
}
],
"modified": "2026-10-28T02:30:29.823774630Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/09616e25f502080ba684fc7fcf959d1376ab756d",
"https://git.kernel.org/stable/c/096dd8519cf2f768e9e14f224b627f7aaee1a9c5",
"https://git.kernel.org/stable/c/28abd224db4a49560b452115bca3672a20e45b2f",
"https://git.kernel.org/stable/c/6251e3e256337a30160ef59ab1580dde4d1acd28",
"https://git.kernel.org/stable/c/b956e48371f2ff72b76be9a829800ecec963bd45",
"https://git.kernel.org/stable/c/da938aa9fc7826901921dcea225948ab21a97e45",
"https://git.kernel.org/stable/c/e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056",
"https://git.kernel.org/stable/c/f537e3ad69609f6924a4db6b4a7f6561f5288bdd",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46004.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-46004",
"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/46xxx/CVE-2026-46004.json"
}
},
"related_cves": [
{
"value": "CVE-2026-46004",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 496492,
"published_at": "2026-05-27T12:56:01.851+00:00"
}