CVE-2023-52486: drm: Don't unref the same fb many times by mistake due to deadlock handling
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.23% (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 376e21a9e4c2c63ee5d8d3aa74be5082c3882229, 62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0, 9dd334a8245011ace45e53298175c7b659edb3e7.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 376e21a9e4c2c63ee5d8d3aa74be5082c3882229, 62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0, 9dd334a8245011ace45e53298175c7b659edb3e7 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: Don't unref the same fb many times by mistake due to deadlock handling If we get a deadlock after the fb lookup in drm_mode_page_flip_ioctl() we proceed to unref the fb and then retry the whole thing from the top. But we forget to reset the fb pointer back to NULL, and so if we then get another error during the retry, before the fb lookup, we proceed the unref the same fb again without having gotten another reference. The end result is that the fb will (eventually) end up being freed while it's still in use. Reset fb to NULL once we've unreffed it to avoid doing it again until we've done another fb lookup. This turned out to be pretty easy to hit on a DG2 when doing async flips (and CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y). The first symptom I saw that drm_closefb() simply got stuck in a busy loop while walking the framebuffer list. Fortunately I was able to convince it to oops instead, and from there it was easier to track down the culprit.
- Published
- Mar 11, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-667
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.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 kernelbefore 4.19.307
- linux linux kernel4.20 and later · before 5.4.269
- linux linux kernel5.5 and later · before 5.10.210
- linux linux kernel5.11 and later · before 5.15.149
- linux linux kernel5.16 and later · before 6.1.76
- linux linux kernel6.2 and later · before 6.6.15
- linux linux kernel6.7 and later · before 6.7.3
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
- 4.12affected
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before 376e21a9e4c2c63ee5d8d3aa74be5082c3882229affected · git
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before 9dd334a8245011ace45e53298175c7b659edb3e7affected · git
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before f55261469be87c55df13db76dc945f6bcd825105affected · git
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before b4af63da9d94986c529d74499fdfe44289acd551affected · git
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before 62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0affected · git
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before d7afdf360f4ac142832b098b4de974e867cc063caffected · git
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before bfd0feb1b109cb63b87fdcd00122603787c75a1aaffected · git
- 29dc0d1de18239cf3ef8bab578b8321ed340d81c and later · before cb4daf271302d71a6b9a7c01bd0b6d76febd8f0caffected · git
- before 4.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-kvm | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-kvm | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| AlmaLinux:8 | kernel-rt-modules-extra | before 4.18.0-553.16.1.rt7.357.el8_10 | 4.18.0-553.16.1.rt7.357.el8_10 |
| Debian:10 | linux | before 4.19.316-1 | 4.19.316-1 |
| Debian:10 | linux-5.10 | before 5.10.216-1~deb10u1 | 5.10.216-1~deb10u1 |
| Debian:11 | linux | before 5.10.216-1 | 5.10.216-1 |
| Debian:12 | linux | before 6.1.76-1 | 6.1.76-1 |
| Debian:13 | linux | before 6.6.15-1 | 6.6.15-1 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt | before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-core | before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug | before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-core | before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-debuginfo | before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-devel | before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
| Red Hat:enterprise_linux:8::nfv | kernel-rt-debug-kvm | before 0:4.18.0-553.16.1.rt7.357.el8_10 | 0:4.18.0-553.16.1.rt7.357.el8_10 |
+76
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-2023-52590Mar 6, 2024 · ocfs2: Avoid touching renamed directory if parent does not change22Monitor
- ← EarlierCVE-2023-52591Mar 6, 2024 · reiserfs: Avoid touching renamed directory if parent does not change31Monitor
- Later →CVE-2023-52487Mar 11, 2024 · net/mlx5e: Fix peer flow lists handling22Monitor
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 | 376e21a9e4c2c63ee5d8d3aa74be5082c3882229 | Vendor (CNA) |
| Linux Linux | 62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0 | Vendor (CNA) |
| Linux Linux | 9dd334a8245011ace45e53298175c7b659edb3e7 | Vendor (CNA) |
| Linux Linux | b4af63da9d94986c529d74499fdfe44289acd551 | Vendor (CNA) |
| Linux Linux | bfd0feb1b109cb63b87fdcd00122603787c75a1a | Vendor (CNA) |
| Linux Linux | cb4daf271302d71a6b9a7c01bd0b6d76febd8f0c | Vendor (CNA) |
| Linux Linux | d7afdf360f4ac142832b098b4de974e867cc063c | Vendor (CNA) |
| Linux Linux | f55261469be87c55df13db76dc945f6bcd825105 | Vendor (CNA) |
| almalinux:kernel-rt | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-kvm | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-kvm | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.76-1 · Debian:12 | Package registry (OSV) |
| debian:linux-5.10 | 5.10.216-1~deb10u1 · Debian:10 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
+5
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
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-667 · Improper LockingCVSS 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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0
- git.kernel.org/stable/c/9dd334a8245011ace45e53298175c7b659edb3e7
- git.kernel.org/stable/c/b4af63da9d94986c529d74499fdfe44289acd551
- git.kernel.org/stable/c/bfd0feb1b109cb63b87fdcd00122603787c75a1a
- git.kernel.org/stable/c/cb4daf271302d71a6b9a7c01bd0b6d76febd8f0c
- git.kernel.org/stable/c/d7afdf360f4ac142832b098b4de974e867cc063c
- git.kernel.org/stable/c/f55261469be87c55df13db76dc945f6bcd825105
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.