Linux: Missing Release of Memory after Effective Lifetime
CVE-2024-27393 is a high-severity missing release of memory after effective lifetime vulnerability in Linux, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4143b9479caa29bb2380f3620dcbe16ea84eb3b1, 7c1250796b6c262b505a46192f4716b8c6a6a8c6, 27aa3e4b3088426b7e34584274ad45b5afaf7629 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.77% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 4143b9479caa29bb2380f3620dcbe16ea84eb3b1 or 7c1250796b6c262b505a46192f4716b8c6a6a8c6 or 27aa3e4b3088426b7e34584274ad45b5afaf7629 or c8b7b2f158d9d4fb89cd2f68244af154f7549bb4, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.154 or 6.1.85 or 6.6.26 or 6.8.5, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 6c5aa6fc4defc2a0977a2c59e4710d50fa1e834c up to, but not including, 4143b9479caa29bb2380f3620dcbe16ea84eb3b1; 6c5aa6fc4defc2a0977a2c59e4710d50fa1e834c up to, but not including, 7c1250796b6c262b505a46192f4716b8c6a6a8c6; 6c5aa6fc4defc2a0977a2c59e4710d50fa1e834c up to, but not including, 27aa3e4b3088426b7e34584274ad45b5afaf7629; 6c5aa6fc4defc2a0977a2c59e4710d50fa1e834c up to, but not including, c8b7b2f158d9d4fb89cd2f68244af154f7549bb4; 6c5aa6fc4defc2a0977a2c59e4710d50fa1e834c up to, but not including, 037965402a010898d34f4e35327d22c0a95cd51f; 5.9 | 4143b9479caa29bb2380f3620dcbe16ea84eb3b1, 7c1250796b6c262b505a46192f4716b8c6a6a8c6, 27aa3e4b3088426b7e34584274ad45b5afaf7629, c8b7b2f158d9d4fb89cd2f68244af154f7549bb4, 037965402a010898d34f4e35327d22c0a95cd51f |
| Linux | Linux Kernel | 5.9 up to, but not including, 5.15.154; 5.16 up to, but not including, 6.1.85; 6.2 up to, but not including, 6.6.26; 6.7 up to, but not including, 6.8.5; 6.9 | 5.15.154, 6.1.85, 6.6.26, 6.8.5 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA |
| CVSS 3.1 | 5.5 | Medium | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: xen-netfront: Add missing skb_mark_for_recycle Notice that skb_mark_for_recycle() is introduced later than fixes tag in commit 6a5bcd84e886 ("page_pool: Allow drivers to hint on SKB recycling"). It is believed that fixes tag were missing a call to page_pool_release_page() between v5.9 to v5.14, after which is should have used skb_mark_for_recycle(). Since v6.6 the call page_pool_release_page() were removed (in commit 535b9c61bdef ("net: page_pool: hide page_pool_release_page()") and remaining callers converted (in commit 6bfef2ec0172 ("Merge branch 'net-page_pool-remove-page_pool_release_page'")). This leak became visible in v6.8 via commit dba1b8a7ab68 ("mm/page_pool: catch page_pool memory leaks").
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Release of Memory after Effective Lifetime
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
How developers prevent this class of flaw
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC). To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
More Missing Release of Memory after Effective Lifetime vulnerabilities (CWE-401)
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/037965402a010898d34f4e35327d22c0a95cd51f
- git.kernel.org/stable/c/27aa3e4b3088426b7e34584274ad45b5afaf7629
- git.kernel.org/stable/c/4143b9479caa29bb2380f3620dcbe16ea84eb3b1
- git.kernel.org/stable/c/7c1250796b6c262b505a46192f4716b8c6a6a8c6
- git.kernel.org/stable/c/c8b7b2f158d9d4fb89cd2f68244af154f7549bb4
Third-party and government advisories
- openwall.com/lists/oss-security/2024/05/08/4Mailing List, Third Party Advisory
- xenbits.xen.org/xsa/advisory-457.htmlThird Party Advisory
Recent Missing Release of Memory after Effective Lifetime vulnerabilities
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.5 High severity
- 7.1 High severity
- 7.5 High severity
Spotted an error? Tell us.