CVE-2023-52661: drm/tegra: rgb: Fix missing clk_put() in the error handling paths of tegra_dc_rgb_probe()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2388c36e028fff7f8ffd515681a14c6c2c07fea7, 45c8034db47842b25a3ab6139d71e13b4e67b9b3, 5c8dc26e31b8b410ad1895e0d314def50c76eed0; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.
Low priority for now. Upgrade to Linux Linux 2388c36e028fff7f8ffd515681a14c6c2c07fea7, 45c8034db47842b25a3ab6139d71e13b4e67b9b3, 5c8dc26e31b8b410ad1895e0d314def50c76eed0; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: drm/tegra: rgb: Fix missing clk_put() in the error handling paths of tegra_dc_rgb_probe() If clk_get_sys(..., "pll_d2_out0") fails, the clk_get_sys() call must be undone. Add the missing clk_put and a new 'put_pll_d_out0' label in the error handling path, and use it.
- Published
- May 17, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.17 and later · before 6.1.83
- linux linux kernel6.2 and later · before 6.6.23
- linux linux kernel6.7 and later · before 6.7.11
- linux linux kernel6.8 and later · before 6.8.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.17affected
- 527bf2adf012785636a89a1c6f7c5a62f259e1a9 and later · before 5c8dc26e31b8b410ad1895e0d314def50c76eed0affected · git
- 0c921b6d4ba06bc899fd84d3ce1c1afd3d00bc1c and later · before f3f407ccbe84a34de9be3195d22cdd5969f3fd9faffected · git
- 0c921b6d4ba06bc899fd84d3ce1c1afd3d00bc1c and later · before 845322a9c06dd1dcf35b6c4e3af89684297c23ccaffected · git
- 0c921b6d4ba06bc899fd84d3ce1c1afd3d00bc1c and later · before 2388c36e028fff7f8ffd515681a14c6c2c07fea7affected · git
- 0c921b6d4ba06bc899fd84d3ce1c1afd3d00bc1c and later · before fa74e4f5d0821829545b9f7034a0e577c205c101affected · git
- 0c921b6d4ba06bc899fd84d3ce1c1afd3d00bc1c and later · before 45c8034db47842b25a3ab6139d71e13b4e67b9b3affected · git
- before 5.17not affected · semver
- 6.1.83 and later · up to and including 6.1.*not affected · semver
- 6.6.23 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.7.12-1 | 6.7.12-1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0-RT_Update_5 | before 1-1.1 | 1-1.1 |
| SUSE:Linux Micro 6.0 | kernel-rt | before 6.4.0-25.1 | 6.4.0-25.1 |
| SUSE:Linux Micro 6.0 | kernel-source-rt | before 6.4.0-25.1 | 6.4.0-25.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-35793May 17, 2024 · debugfs: fix wait/cancellation handling during remove22Monitor
- ← EarlierCVE-2024-35794May 17, 2024 · dm-raid: really frozen sync_thread during suspend22Monitor
- Later →CVE-2023-52662May 17, 2024 · drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2388c36e028fff7f8ffd515681a14c6c2c07fea7 | Vendor (CNA) |
| Linux Linux | 45c8034db47842b25a3ab6139d71e13b4e67b9b3 | Vendor (CNA) |
| Linux Linux | 5c8dc26e31b8b410ad1895e0d314def50c76eed0 | Vendor (CNA) |
| Linux Linux | 845322a9c06dd1dcf35b6c4e3af89684297c23cc | Vendor (CNA) |
| Linux Linux | f3f407ccbe84a34de9be3195d22cdd5969f3fd9f | Vendor (CNA) |
| Linux Linux | fa74e4f5d0821829545b9f7034a0e577c205c101 | Vendor (CNA) |
| azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 | 6.6.35.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 | 6.6.35.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_5 | 1-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-25.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-25.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/45c8034db47842b25a3ab6139d71e13b4e67b9b3
- git.kernel.org/stable/c/5c8dc26e31b8b410ad1895e0d314def50c76eed0
- git.kernel.org/stable/c/845322a9c06dd1dcf35b6c4e3af89684297c23cc
- git.kernel.org/stable/c/f3f407ccbe84a34de9be3195d22cdd5969f3fd9f
- git.kernel.org/stable/c/fa74e4f5d0821829545b9f7034a0e577c205c101
Vendor advisories and official records. Exploit/PoC links are deliberately left out.