Linux Kernel up to 6.18.44/7.1.8 ring-buffer rb_allocate_cpu_buffer uninitialized resource

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.43 |
Summary
A vulnerability has been found in Linux Kernel up to 6.18.44/7.1.8 and classified as very critical. This affects the function rb_allocate_cpu_buffer of the component ring-buffer. This manipulation causes uninitialized resource.
The identification of this vulnerability is CVE-2026-74602. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Linux Kernel up to 6.18.44/7.1.8. It has been declared as very critical. Affected by this vulnerability is the function rb_allocate_cpu_buffer of the component ring-buffer. The manipulation with an unknown input leads to a uninitialized resource vulnerability. The CWE definition for the vulnerability is CWE-908. The product uses or accesses a resource that has not been initialized. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer() In rb_allocate_cpu_buffer(), bpage->order was omitted, leaving it as 0. This is an issue for a ring-buffer with subbufs bigger than PAGE_SIZE if when freed: free_buffer_page() relies on this value. Align the value with the actual allocation size (buffer::subbuf_order).
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-74602 since 08/15/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/22/2026).
Upgrading to version 6.18.45 or 7.1.9 eliminates this vulnerability. Applying the patch 2e37f2bf111429fbfa4d985b12df3ba496ca70aa/3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a/6d014e44b68ddd43f71288d2a4dbb1a259869149 is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
- 7.1.8
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Uninitialized resourceCWE: CWE-908
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.18.45/7.1.9
Patch: 2e37f2bf111429fbfa4d985b12df3ba496ca70aa/3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a/6d014e44b68ddd43f71288d2a4dbb1a259869149
Timeline
08/15/2026 CVE reserved08/22/2026 Advisory disclosed
08/22/2026 VulDB entry created
08/22/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-74602 (🔒)
GCVE (CVE): GCVE-0-2026-74602
GCVE (VulDB): GCVE-100-394369
Entry
Created: 08/22/2026 17:52Changes: 08/22/2026 17:52 (59)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.