Linux: Use After Free
CVE-2022-49288 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 e7786c445bb67a9a6e64f66ebd6b7215b153ff7d, e14dca613e0a6ddc2bf6e360f16936a9f865205b, 37b12c16beb6f6c1c3c678c1aacbc46525c250f7 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.28% 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 e7786c445bb67a9a6e64f66ebd6b7215b153ff7d or e14dca613e0a6ddc2bf6e360f16936a9f865205b or 37b12c16beb6f6c1c3c678c1aacbc46525c250f7 or b560d670c87d7d40b3cf6949246fa4c7aa65a00a, whichever matches your release line, or a later version.
- Update Linux Kernel to 4.14.279 or 4.19.243 or 5.4.193 or 5.10.109, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, e7786c445bb67a9a6e64f66ebd6b7215b153ff7d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, e14dca613e0a6ddc2bf6e360f16936a9f865205b; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 37b12c16beb6f6c1c3c678c1aacbc46525c250f7; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, b560d670c87d7d40b3cf6949246fa4c7aa65a00a; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 51fce708ab8986a9879ee5da946a2cc120f1036d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, a21d2f323b5a978dedf9ff1d50f101f85e39b3f2; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 69534c48ba8ce552ce383b3dfdb271ffe51820c3; and 1 more ranges | e7786c445bb67a9a6e64f66ebd6b7215b153ff7d, e14dca613e0a6ddc2bf6e360f16936a9f865205b, 37b12c16beb6f6c1c3c678c1aacbc46525c250f7, b560d670c87d7d40b3cf6949246fa4c7aa65a00a, 51fce708ab8986a9879ee5da946a2cc120f1036d, a21d2f323b5a978dedf9ff1d50f101f85e39b3f2 |
| Linux | Linux Kernel | before 4.14.279; 4.15 up to, but not including, 4.19.243; 4.20 up to, but not including, 5.4.193; 5.5 up to, but not including, 5.10.109; 5.11 up to, but not including, 5.15.32; 5.16 up to, but not including, 5.16.18; 5.17 up to, but not including, 5.17.1 | 4.14.279, 4.19.243, 5.4.193, 5.10.109, 5.15.32, 5.16.18 |
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 CISA (ADP).
Official description
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent prealloc proc writes We have no protection against concurrent PCM buffer preallocation changes via proc files, and it may potentially lead to UAF or some weird problem. This patch applies the PCM open_mutex to the proc write operation for avoiding the racy proc writes and the PCM stream open (and further operations).
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: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/37b12c16beb6f6c1c3c678c1aacbc46525c250f7
- git.kernel.org/stable/c/51fce708ab8986a9879ee5da946a2cc120f1036d
- git.kernel.org/stable/c/5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6
- git.kernel.org/stable/c/69534c48ba8ce552ce383b3dfdb271ffe51820c3
- git.kernel.org/stable/c/a21d2f323b5a978dedf9ff1d50f101f85e39b3f2
- git.kernel.org/stable/c/b560d670c87d7d40b3cf6949246fa4c7aa65a00a
- git.kernel.org/stable/c/e14dca613e0a6ddc2bf6e360f16936a9f865205b
- git.kernel.org/stable/c/e7786c445bb67a9a6e64f66ebd6b7215b153ff7d
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.