Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Mar 11, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

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.

Follow CVE-2023-52486

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux 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.

EcosystemPackageAffected rangeFix
AlmaLinux:8kernel-rtbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-debug-kvmbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-kvmbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
AlmaLinux:8kernel-rt-modules-extrabefore 4.18.0-553.16.1.rt7.357.el8_104.18.0-553.16.1.rt7.357.el8_10
Debian:10linuxbefore 4.19.316-14.19.316-1
Debian:10linux-5.10before 5.10.216-1~deb10u15.10.216-1~deb10u1
Debian:11linuxbefore 5.10.216-15.10.216-1
Debian:12linuxbefore 6.1.76-16.1.76-1
Debian:13linuxbefore 6.6.15-16.6.15-1
Red Hat:enterprise_linux:8::nfvkernel-rtbefore 0:4.18.0-553.16.1.rt7.357.el8_100:4.18.0-553.16.1.rt7.357.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-corebefore 0:4.18.0-553.16.1.rt7.357.el8_100:4.18.0-553.16.1.rt7.357.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debugbefore 0:4.18.0-553.16.1.rt7.357.el8_100:4.18.0-553.16.1.rt7.357.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-corebefore 0:4.18.0-553.16.1.rt7.357.el8_100:4.18.0-553.16.1.rt7.357.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-debuginfobefore 0:4.18.0-553.16.1.rt7.357.el8_100:4.18.0-553.16.1.rt7.357.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-develbefore 0:4.18.0-553.16.1.rt7.357.el8_100:4.18.0-553.16.1.rt7.357.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-kvmbefore 0:4.18.0-553.16.1.rt7.357.el8_100:4.18.0-553.16.1.rt7.357.el8_10

+76

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52590Mar 6, 2024 · ocfs2: Avoid touching renamed directory if parent does not change
    22Monitor
  • ← EarlierCVE-2023-52591Mar 6, 2024 · reiserfs: Avoid touching renamed directory if parent does not change
    31Monitor
  • Later →CVE-2023-52487Mar 11, 2024 · net/mlx5e: Fix peer flow lists handling
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux376e21a9e4c2c63ee5d8d3aa74be5082c3882229Vendor (CNA)
Linux Linux62f2e79cf9f4f47cc9dea9cebdf58d9f7b5695e0Vendor (CNA)
Linux Linux9dd334a8245011ace45e53298175c7b659edb3e7Vendor (CNA)
Linux Linuxb4af63da9d94986c529d74499fdfe44289acd551Vendor (CNA)
Linux Linuxbfd0feb1b109cb63b87fdcd00122603787c75a1aVendor (CNA)
Linux Linuxcb4daf271302d71a6b9a7c01bd0b6d76febd8f0cVendor (CNA)
Linux Linuxd7afdf360f4ac142832b098b4de974e867cc063cVendor (CNA)
Linux Linuxf55261469be87c55df13db76dc945f6bcd825105Vendor (CNA)
almalinux:kernel-rt4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-kvm4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-kvm4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.16.1.rt7.357.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.76-1 · Debian:12Package registry (OSV)
debian:linux-5.105.10.216-1~deb10u1 · Debian:10Package registry (OSV)
red hat:bpftool0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage 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.

Finders, 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.

All national notices →

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 Locking

CVSS 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records