CVE-2024-26866: spi: lpspi: Avoid potential use-after-free in probe()
First published: Wed Apr 17 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: spi: lpspi: Avoid potential use-after-free in probe() fsl_lpspi_probe() is allocating/disposing memory manually with spi_alloc_host()/spi_alloc_target(), but uses devm_spi_register_controller(). In case of error after the latter call the memory will be explicitly freed in the probe function by spi_controller_put() call, but used afterwards by "devm" management outside probe() (spi_unregister_controller() <- devm_spi_unregister() below). Unable to handle kernel NULL pointer dereference at virtual address 0000000000000070 ... Call trace: kernfs_find_ns kernfs_find_and_get_ns sysfs_remove_group sysfs_remove_groups device_remove_attrs device_del spi_unregister_controller devm_spi_unregister release_nodes devres_release_all really_probe driver_probe_device __device_attach_driver bus_for_each_drv __device_attach device_initial_probe bus_probe_device deferred_probe_work_func process_one_work worker_thread kthread ret_from_fork
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux kernel | >=4.10<6.6.23 | |
| Linux kernel | >=6.7<6.7.11 | |
| Linux kernel | >=6.8<6.8.2 | |
| Linux Kernel | >=4.10<6.6.23 | |
| Linux Kernel | >=6.7<6.7.11 | |
| Linux Kernel | >=6.8<6.8.2 | |
| debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.123-1<=6.1.128-1 | 6.12.17-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/1543418e82789cc383cd36d41469983c64e3fc7f
- https://git.kernel.org/stable/c/2ae0ab0143fcc06190713ed81a6486ed0ad3c861
- https://git.kernel.org/stable/c/996ce839606afd0fef91355627868022aa73eb68
- https://git.kernel.org/stable/c/da83ed350e4604b976e94239b08d8e2e7eaee7ea
- https://launchpad.net/bugs/cve/CVE-2024-26866
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26866
- https://nvd.nist.gov/vuln/detail/CVE-2024-26866
- https://security-tracker.debian.org/tracker/CVE-2024-26866
- https://ubuntu.com/security/CVE-2024-26866
- https://git.kernel.org/linus/2ae0ab0143fcc06190713ed81a6486ed0ad3c861
Frequently Asked Questions
What is the severity of CVE-2024-26866?
CVE-2024-26866 has a severity rating that indicates a medium risk due to the potential use-after-free vulnerability.
How do I fix CVE-2024-26866?
To fix CVE-2024-26866, update to the Linux kernel versions 6.12.12-1 or 6.12.13-1 or apply the appropriate patches.
What versions of Linux are affected by CVE-2024-26866?
CVE-2024-26866 affects Linux kernel versions from 4.10 up to, but not including, 6.6.23, as well as specific versions between 6.7.0 and 6.7.11 and 6.8.0 to 6.8.2.
Is CVE-2024-26866 remotely exploitable?
CVE-2024-26866 is primarily a local vulnerability and is not considered to be remotely exploitable.
What is the impact of CVE-2024-26866 on system security?
The impact of CVE-2024-26866 includes potential memory corruption issues which can lead to denial of service or escalation of privileges if exploited.
- agent/weakness
- agent/title
- agent/type
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/severity
- agent/last-modified-date
- agent/remedy
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- collector/nvd-cve
- vendor/linux
- canonical/linux kernel
- version/linux kernel/4.10
- version/linux kernel/6.7
- version/linux kernel/6.8
- package-manager/debian