Linux Kernel up to 6.3.x relayfs kernel/relay.c relay_file_read_start_pos out-of-bounds

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.3.x. It has been rated as problematic. Affected by this issue is the function relay_file_read_start_pos of the file kernel/relay.c of the component relayfs. The manipulation leads to out-of-bounds.
This vulnerability is traded as CVE-2023-3268. An attack has to be approached locally. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability was found in Linux Kernel up to 6.3.x (Operating System). It has been rated as critical. This issue affects the function relay_file_read_start_pos of the file kernel/relay.c of the component relayfs. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability.
The weakness was shared 06/16/2023. The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2023-3268 since 06/15/2023. Technical details are known, but no exploit is available.
Upgrading to version 6.4-rc1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-43944). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.6
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔍
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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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.4-rc1
Timeline
06/15/2023 🔍06/16/2023 🔍
06/16/2023 🔍
01/26/2026 🔍
Sources
Vendor: kernel.orgAdvisory: bugzilla.redhat.com
Status: Confirmed
CVE: CVE-2023-3268 (🔍)
GCVE (CVE): GCVE-0-2023-3268
GCVE (VulDB): GCVE-100-231749
EUVD: 🔍
Entry
Created: 06/16/2023 14:35Updated: 01/26/2026 19:51
Changes: 06/16/2023 14:35 (42), 07/14/2023 13:11 (1), 07/14/2023 13:16 (11), 01/26/2026 19:51 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.