dbcve.org
Linux KernelOperating system · Linux

CVE-2023-52847

HIGH · 7.0 CVSS v3.1 Published 2024-05-21
Fix available
A fix is available. Upgrade to 4.19.299 / 5.4.261 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: media: bttv: fix use after free error due to btv->timeout timer There may be some a race condition between timer function bttv_irq_timeout and bttv_remove. The timer is setup in probe and there is no timer_delete operation in remove function. When it hit kfree btv, the function might still be invoked, which will cause use after free bug. This bug is found by static analysis, it may be false positive. Fix it by adding del_timer_sync invoking to the remove function. cpu0 cpu1 bttv_probe ->timer_setup ->bttv_set_dma ->mod_timer; bttv_remove ->kfree(btv); ->bttv_irq_timeout ->USE btv

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-362

Two operations that should be atomic can interleave, so an attacker who wins a narrow timing window reaches an inconsistent, exploitable state. These bugs are subtle and easy to miss in review. Fixing them properly means correct locking or atomic operations around the shared resource.

General guidance for the race condition class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.15, < 4.19.299>= 4.20, < 5.4.261>= 5.5, < 5.10.201>= 5.11, < 5.15.139>= 5.16, < 6.1.63>= 6.2, < 6.5.12>= 6.6, < 6.6.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.19.299 / 5.4.261 / 5.10.201 or later
Fixed in 4.19.2995.4.2615.10.201
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 4.19.299+, 5.4.261+, 5.10.201+, or 5.15.139+ depending on your current branch

  1. 1. Identify the current running kernel version using 'uname -r' or 'cat /proc/version'
  2. 2. Determine the appropriate upgrade target based on your current kernel branch: for 4.15-4.18.x upgrade to >=4.19.299, for 4.20-5.4.x upgrade to >=5.4.261, for 5.5-5.10.x upgrade to >=5.10.201, for 5.11-5.14.x upgrade to >=5.15.139
  3. 3. Update the package repository and install the new kernel version using the distribution's package manager (e.g., 'apt update && apt upgrade' for Debian/Ubuntu, 'yum update' for RHEL/CentOS)
  4. 4. Reboot the system to load the new kernel
  5. 5. Verify the new kernel version is running with 'uname -r'
Caveat Kernel upgrades may require rebuild of out-of-tree modules and could introduce compatibility issues with older userspace tools; ensure backups and test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52847 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data