Linux: Use After Free
CVE-2024-49986 is a high-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions ba0b09a2f327319e252d8f3032019b958c0a5cd9, aac871e493fc8809e60209d9899b1af07e9dbfc8, f08adc5177bd4343df09033f62ab562c09ba7f7d as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.25% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to ba0b09a2f327319e252d8f3032019b958c0a5cd9 or aac871e493fc8809e60209d9899b1af07e9dbfc8 or f08adc5177bd4343df09033f62ab562c09ba7f7d or 73a98cf79e4dbfa3d0c363e826c65aae089b313c, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.118 or 6.6.55 or 6.10.14 or 6.11.3, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 5eba0141206ea521bbcfcf5067c174e825e943dd up to, but not including, ba0b09a2f327319e252d8f3032019b958c0a5cd9; 5eba0141206ea521bbcfcf5067c174e825e943dd up to, but not including, aac871e493fc8809e60209d9899b1af07e9dbfc8; 5eba0141206ea521bbcfcf5067c174e825e943dd up to, but not including, f08adc5177bd4343df09033f62ab562c09ba7f7d; 5eba0141206ea521bbcfcf5067c174e825e943dd up to, but not including, 73a98cf79e4dbfa3d0c363e826c65aae089b313c; 5eba0141206ea521bbcfcf5067c174e825e943dd up to, but not including, 2fae3129c0c08e72b1fe93e61fd8fd203252094a; 5.17 | ba0b09a2f327319e252d8f3032019b958c0a5cd9, aac871e493fc8809e60209d9899b1af07e9dbfc8, f08adc5177bd4343df09033f62ab562c09ba7f7d, 73a98cf79e4dbfa3d0c363e826c65aae089b313c, 2fae3129c0c08e72b1fe93e61fd8fd203252094a |
| Debian | Debian Linux | 11.0 | Not stated |
| Linux | Linux Kernel | 5.17 up to, but not including, 6.1.118; 6.2 up to, but not including, 6.6.55; 6.7 up to, but not including, 6.10.14; 6.11 up to, but not including, 6.11.3; 6.12 | 6.1.118, 6.6.55, 6.10.14, 6.11.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: platform/x86: x86-android-tablets: Fix use after free on platform_device_register() errors x86_android_tablet_remove() frees the pdevs[] array, so it should not be used after calling x86_android_tablet_remove(). When platform_device_register() fails, store the pdevs[x] PTR_ERR() value into the local ret variable before calling x86_android_tablet_remove() to avoid using pdevs[] after it has been freed.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/2fae3129c0c08e72b1fe93e61fd8fd203252094a
- git.kernel.org/stable/c/73a98cf79e4dbfa3d0c363e826c65aae089b313c
- git.kernel.org/stable/c/aac871e493fc8809e60209d9899b1af07e9dbfc8
- git.kernel.org/stable/c/ba0b09a2f327319e252d8f3032019b958c0a5cd9
- git.kernel.org/stable/c/f08adc5177bd4343df09033f62ab562c09ba7f7d
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlMailing List, Third Party Advisory
Recent Use After Free vulnerabilities
- 7.0 High severity
- 7.0 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.