dbcve.org
Linux KernelOperating system · Linux

CVE-2023-52787

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-21
Fix available
A fix is available. Upgrade to 6.1.72 / 6.5.13 or later.
See remediation →
57/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: blk-mq: make sure active queue usage is held for bio_integrity_prep() blk_integrity_unregister() can come if queue usage counter isn't held for one bio with integrity prepared, so this request may be completed with calling profile->complete_fn, then kernel panic. Another constraint is that bio_integrity_prep() needs to be called before bio merge. Fix the issue by: - call bio_integrity_prep() with one queue usage counter grabbed reliably - call bio_integrity_prep() before bio merge

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

A detailed technical summary for this CVE is being prepared.

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:>= 5.16, < 6.1.72>= 6.2, < 6.5.13>= 6.6, < 6.6.3= 6.7

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 6.1.72 / 6.5.13 / 6.6.3 or later
Fixed in 6.1.726.5.136.6.3
Vendor patch git.kernel.org →
Recommended fix High confidence

6.1.73+, 6.5.14+, 6.6.4+, or 6.8+ (choose based on your distribution's kernel support)

  1. 1. Identify the currently running Linux kernel version using 'uname -r'
  2. 2. Determine the appropriate upgrade path based on your distribution's kernel package availability
  3. 3. For production systems, consider upgrading to the latest stable LTS kernel (6.1.x or 6.6.x) rather than the minimum fixed version
  4. 4. Apply the upgrade via your distribution's package manager (e.g., 'apt-get dist-upgrade', 'yum update', or 'dnf upgrade')
  5. 5. Reboot the system into the new kernel
  6. 6. Verify the kernel version after reboot with 'uname -r' to confirm the patched version is running
  7. 7. For custom-built kernels, apply the upstream commit b0077e269f6c152e807fdac90b58caf012cdbaab and rebuild
Caveat Kernel upgrades may require rebuild of out-of-tree kernel modules; ensure driver compatibility before rebooting

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,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52787 — 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-52787 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