Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52811: scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool

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.25% (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 88984ec4792766df5a9de7a2ff2b5f281f94c7d4, 8bbe784c2ff28d56ca0c548aaf3e584edc77052d, b39f2d10b86d0af353ea339e5815820026bca48f.

Low priority for now. Upgrade to Linux Linux 88984ec4792766df5a9de7a2ff2b5f281f94c7d4, 8bbe784c2ff28d56ca0c548aaf3e584edc77052d, b39f2d10b86d0af353ea339e5815820026bca48f 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: scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool In practice the driver should never send more commands than are allocated to a queue's event pool. In the unlikely event that this happens, the code asserts a BUG_ON, and in the case that the kernel is not configured to crash on panic returns a junk event pointer from the empty event list causing things to spiral from there. This BUG_ON is a historical artifact of the ibmvfc driver first being upstreamed, and it is well known now that the use of BUG_ON is bad practice except in the most unrecoverable scenario. There is nothing about this scenario that prevents the driver from recovering and carrying on. Remove the BUG_ON in question from ibmvfc_get_event() and return a NULL pointer in the case of an empty event pool. Update all call sites to ibmvfc_get_event() to check for a NULL pointer and perfrom the appropriate failure or recovery action.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 16th 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.

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-52811

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

Running WordPress? Scan your site free with WP Lens

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

Running WordPress? Scan your site free with WP Lens

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 5.15.140
  • linux linux kernel5.16 and later · before 6.1.64
  • linux linux kernel6.2 and later · before 6.5.13
  • linux linux kernel6.6 and later · before 6.6.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

    • 2.6.27affected
    • 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 and later · before e1d1f79b1929dce470a5dc9281c574cd58e8c6c0affected · git
    • 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 and later · before 88984ec4792766df5a9de7a2ff2b5f281f94c7d4affected · git
    • 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 and later · before d2af4ef80601224b90630c1ddc7cd2c7c8ab4dd8affected · git
    • 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 and later · before 8bbe784c2ff28d56ca0c548aaf3e584edc77052daffected · git
    • 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 and later · before b39f2d10b86d0af353ea339e5815820026bca48faffected · git
    • before 2.6.27not affected · semver
    • 5.15.140 and later · up to and including 5.15.*not affected · semver
    • 6.1.64 and later · up to and including 6.1.*not affected · semver
    • 6.5.13 and later · up to and including 6.5.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.64-16.1.64-1
Debian:13linuxbefore 6.5.13-16.5.13-1
Red Hat:rhel_eus:8.8::baseosbpftoolbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseosbpftool-debuginfobefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernelbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-abi-stablelistsbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-corebefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debugbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-corebefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-debuginfobefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-develbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modulesbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modules-extrabefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfobefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-develbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-docbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modulesbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modules-extrabefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-toolsbefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-tools-debuginfobefore 0:4.18.0-477.74.1.el8_80:4.18.0-477.74.1.el8_8

+96

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-52809May 21, 2024 · scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup()
    22Monitor
  • ← EarlierCVE-2023-52810May 21, 2024 · fs/jfs: Add check for negative db_l2nbperpage
    31Monitor
  • Later →CVE-2023-52812May 21, 2024 · drm/amd: check num of link levels when update pcie param
    31Monitor

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 Linux88984ec4792766df5a9de7a2ff2b5f281f94c7d4Vendor (CNA)
Linux Linux8bbe784c2ff28d56ca0c548aaf3e584edc77052dVendor (CNA)
Linux Linuxb39f2d10b86d0af353ea339e5815820026bca48fVendor (CNA)
Linux Linuxd2af4ef80601224b90630c1ddc7cd2c7c8ab4dd8Vendor (CNA)
Linux Linuxe1d1f79b1929dce470a5dc9281c574cd58e8c6c0Vendor (CNA)
debian:linux6.1.64-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage 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.

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

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

CVSS vector

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

nvd-secondary

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

  1. Fix✗ → ✓

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

References

All records