Linux: Use After Free
CVE-2024-26622 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 a23ac1788e2c828c097119e9a3178f0b7e503fee, 7d930a4da17958f869ef679ee0e4a8729337affc, 3bfe04c1273d30b866f4c7c238331ed3b08e5824 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.24% 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 a23ac1788e2c828c097119e9a3178f0b7e503fee or 7d930a4da17958f869ef679ee0e4a8729337affc or 3bfe04c1273d30b866f4c7c238331ed3b08e5824 or 2caa605079488da9601099fbda460cfc1702839f, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.212 or 5.15.151 or 6.1.81 or 6.6.21, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | bd03a3e4c9a9df0c6b007045fa7fc8889111a478 up to, but not including, a23ac1788e2c828c097119e9a3178f0b7e503fee; bd03a3e4c9a9df0c6b007045fa7fc8889111a478 up to, but not including, 7d930a4da17958f869ef679ee0e4a8729337affc; bd03a3e4c9a9df0c6b007045fa7fc8889111a478 up to, but not including, 3bfe04c1273d30b866f4c7c238331ed3b08e5824; bd03a3e4c9a9df0c6b007045fa7fc8889111a478 up to, but not including, 2caa605079488da9601099fbda460cfc1702839f; bd03a3e4c9a9df0c6b007045fa7fc8889111a478 up to, but not including, 6edefe1b6c29a9932f558a898968a9fcbeec5711; bd03a3e4c9a9df0c6b007045fa7fc8889111a478 up to, but not including, 2f03fc340cac9ea1dc63cbf8c93dd2eb0f227815; 3.1 | a23ac1788e2c828c097119e9a3178f0b7e503fee, 7d930a4da17958f869ef679ee0e4a8729337affc, 3bfe04c1273d30b866f4c7c238331ed3b08e5824, 2caa605079488da9601099fbda460cfc1702839f, 6edefe1b6c29a9932f558a898968a9fcbeec5711, 2f03fc340cac9ea1dc63cbf8c93dd2eb0f227815 |
| Linux | Linux Kernel | 3.1 up to, but not including, 5.10.212; 5.11 up to, but not including, 5.15.151; 5.16 up to, but not including, 6.1.81; 6.2 up to, but not including, 6.6.21; 6.7 up to, but not including, 6.7.9; 6.8 | 5.10.212, 5.15.151, 6.1.81, 6.6.21, 6.7.9 |
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.
Official description
In the Linux kernel, the following vulnerability has been resolved: tomoyo: fix UAF write bug in tomoyo_write_control() Since tomoyo_write_control() updates head->write_buf when write() of long lines is requested, we need to fetch head->write_buf after head->io_sem is held. Otherwise, concurrent write() requests can cause use-after-free-write and double-free problems.
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/2caa605079488da9601099fbda460cfc1702839f
- git.kernel.org/stable/c/2f03fc340cac9ea1dc63cbf8c93dd2eb0f227815
- git.kernel.org/stable/c/3bfe04c1273d30b866f4c7c238331ed3b08e5824
- git.kernel.org/stable/c/6edefe1b6c29a9932f558a898968a9fcbeec5711
- git.kernel.org/stable/c/7d930a4da17958f869ef679ee0e4a8729337affc
- git.kernel.org/stable/c/a23ac1788e2c828c097119e9a3178f0b7e503fee
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
Other references
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.0 High severity
- 8.4 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.