CVE-2024-26932: usb: typec: tcpm: fix double-free issue in tcpm_port_unregister_pd()
First published: Wed May 01 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: fix double-free issue in tcpm_port_unregister_pd() When unregister pd capabilitie in tcpm, KASAN will capture below double -free issue. The root cause is the same capabilitiy will be kfreed twice, the first time is kfreed by pd_capabilities_release() and the second time is explicitly kfreed by tcpm_port_unregister_pd(). [ 3.988059] BUG: KASAN: double-free in tcpm_port_unregister_pd+0x1a4/0x3dc [ 3.995001] Free of addr ffff0008164d3000 by task kworker/u16:0/10 [ 4.001206] [ 4.002712] CPU: 2 PID: 10 Comm: kworker/u16:0 Not tainted 6.8.0-rc5-next-20240220-05616-g52728c567a55 #53 [ 4.012402] Hardware name: Freescale i.MX8QXP MEK (DT) [ 4.017569] Workqueue: events_unbound deferred_probe_work_func [ 4.023456] Call trace: [ 4.025920] dump_backtrace+0x94/0xec [ 4.029629] show_stack+0x18/0x24 [ 4.032974] dump_stack_lvl+0x78/0x90 [ 4.036675] print_report+0xfc/0x5c0 [ 4.040289] kasan_report_invalid_free+0xa0/0xc0 [ 4.044937] __kasan_slab_free+0x124/0x154 [ 4.049072] kfree+0xb4/0x1e8 [ 4.052069] tcpm_port_unregister_pd+0x1a4/0x3dc [ 4.056725] tcpm_register_port+0x1dd0/0x2558 [ 4.061121] tcpci_register_port+0x420/0x71c [ 4.065430] tcpci_probe+0x118/0x2e0 To fix the issue, this will remove kree() from tcpm_port_unregister_pd().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >6.8<6.8.3 | |
| Linux Kernel | =6.9-rc1 | |
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.10-1 6.12.11-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/242e425ed580b2f4dbcb86c8fc03a410a4084a69
- https://git.kernel.org/stable/c/b63f90487bdf93a4223ce7853d14717e9d452856
- https://launchpad.net/bugs/cve/CVE-2024-26932
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26932
- https://nvd.nist.gov/vuln/detail/CVE-2024-26932
- https://security-tracker.debian.org/tracker/CVE-2024-26932
- https://ubuntu.com/security/CVE-2024-26932
- https://git.kernel.org/linus/b63f90487bdf93a4223ce7853d14717e9d452856
Frequently Asked Questions
What is the severity of CVE-2024-26932?
The severity of CVE-2024-26932 has not been explicitly stated, but it involves a double-free vulnerability in the Linux kernel that could lead to potential exploitation.
How do I fix CVE-2024-26932?
To fix CVE-2024-26932, users should upgrade to a patched version of the Linux kernel, such as 6.8.3 or higher.
What versions of the Linux kernel are affected by CVE-2024-26932?
CVE-2024-26932 affects Linux kernel versions between 6.8 and 6.9-rc1.
Is CVE-2024-26932 a critical vulnerability?
CVE-2024-26932 may be considered critical due to the potential for double-free errors that can compromise system stability and security.
What systems are primarily at risk for CVE-2024-26932?
Systems running vulnerable versions of the Linux kernel, particularly Debian-based distributions, are primarily at risk for CVE-2024-26932.
- agent/title
- agent/type
- agent/weakness
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- agent/severity
- collector/usn-cve
- source/Ubuntu
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/event
- agent/last-modified-date
- agent/references
- agent/trending
- agent/source
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- agent/softwarecombine
- agent/tags
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.9-rc1
- package-manager/debian