CVE-2024-26653
What it is
In the Linux kernel, the following vulnerability has been resolved: usb: misc: ljca: Fix double free in error handling path When auxiliary_device_add() returns error and then calls auxiliary_device_uninit(), callback function ljca_auxdev_release calls kfree(auxdev->dev.platform_data) to free the parameter data of the function ljca_new_client_device. The callers of ljca_new_client_device shouldn't call kfree() again in the error handling path to free the platform data. Fix this by cleaning up the redundant kfree() in all callers and adding kfree() the passed in platform_data on errors which happen before auxiliary_device_init() succeeds .
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-415
- Record status
- Analyzed
Affected
- Linux Kernel < 6.7.12
- Linux Kernel < 6.8.3
- Linux Kernel 6.9
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26653.md and follow it. Check whether this project is affected by CVE-2024-26653. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/420babea4f1881a7c4ea22a8e218b8c6895d3f21
- https://git.kernel.org/stable/c/7c9631969287a5366bc8e39cd5abff154b35fb80
- https://git.kernel.org/stable/c/8a9f653cc852677003c23ee8075e3ed8fb4743c9
- https://git.kernel.org/stable/c/420babea4f1881a7c4ea22a8e218b8c6895d3f21
- https://git.kernel.org/stable/c/7c9631969287a5366bc8e39cd5abff154b35fb80
- https://git.kernel.org/stable/c/8a9f653cc852677003c23ee8075e3ed8fb4743c9
References
- https://git.kernel.org/stable/c/420babea4f1881a7c4ea22a8e218b8c6895d3f21
- https://git.kernel.org/stable/c/7c9631969287a5366bc8e39cd5abff154b35fb80
- https://git.kernel.org/stable/c/8a9f653cc852677003c23ee8075e3ed8fb4743c9
- https://git.kernel.org/stable/c/420babea4f1881a7c4ea22a8e218b8c6895d3f21
- https://git.kernel.org/stable/c/7c9631969287a5366bc8e39cd5abff154b35fb80
- https://git.kernel.org/stable/c/8a9f653cc852677003c23ee8075e3ed8fb4743c9