Linux Kernel up to 6.1-rc8 dpu_crtc.c dpu_crtc_atomic_check null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.1-rc8. It has been declared as problematic. This affects the function dpu_crtc_atomic_check of the file drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c. Executing a manipulation can lead to null pointer dereference.
This vulnerability is tracked as CVE-2023-3220. No exploit exists.
A patch should be applied to remediate this issue.
Details
A vulnerability has been found in Linux Kernel up to 6.1-rc8 (Operating System) and classified as problematic. This vulnerability affects the function dpu_crtc_atomic_check of the file drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:
An issue was discovered in the Linux kernel through 6.1-rc8. dpu_crtc_atomic_check in drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c lacks check of the return value of kzalloc() and will cause the NULL Pointer Dereference.
The weakness was disclosed 06/21/2023. The advisory is available at git.kernel.org. This vulnerability was named CVE-2023-3220 since 06/13/2023. Technical details are known, but there is no available exploit.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-43898). If you want to get best quality of vulnerability data, you may have to visit 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: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: git.kernel.org
Timeline
06/13/2023 🔍06/21/2023 🔍
06/21/2023 🔍
01/26/2026 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-3220 (🔍)
GCVE (CVE): GCVE-0-2023-3220
GCVE (VulDB): GCVE-100-232042
EUVD: 🔍
Entry
Created: 06/21/2023 07:08Updated: 01/26/2026 19:40
Changes: 06/21/2023 07:08 (42), 07/16/2023 09:50 (11), 01/26/2026 19:40 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.