Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54048: RDMA/bnxt_re: Prevent handling any completions after qp destroy

Noroxi assessment

Priority: Monitor (action score 31/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.20% (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 7faa6097694164380ed19600c7a7993d071270b9, b5bbc6551297447d3cca55cf907079e206e9cd82, b79a0e71d6e8692e0b6da05f8aaa7d69191cf7e7.

Low priority for now. Upgrade to Linux Linux 7faa6097694164380ed19600c7a7993d071270b9, b5bbc6551297447d3cca55cf907079e206e9cd82, b79a0e71d6e8692e0b6da05f8aaa7d69191cf7e7 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: RDMA/bnxt_re: Prevent handling any completions after qp destroy HW may generate completions that indicates QP is destroyed. Driver should not be scheduling any more completion handlers for this QP, after the QP is destroyed. Since CQs are active during the QP destroy, driver may still schedule completion handlers. This can cause a race where the destroy_cq and poll_cq running simultaneously. Snippet of kernel panic while doing bnxt_re driver load unload in loop. This indicates a poll after the CQ is freed.  [77786.481636] Call Trace: [77786.481640]  <TASK> [77786.481644]  bnxt_re_poll_cq+0x14a/0x620 [bnxt_re] [77786.481658]  ? kvm_clock_read+0x14/0x30 [77786.481693]  __ib_process_cq+0x57/0x190 [ib_core] [77786.481728]  ib_cq_poll_work+0x26/0x80 [ib_core] [77786.481761]  process_one_work+0x1e5/0x3f0 [77786.481768]  worker_thread+0x50/0x3a0 [77786.481785]  ? __pfx_worker_thread+0x10/0x10 [77786.481790]  kthread+0xe2/0x110 [77786.481794]  ? __pfx_kthread+0x10/0x10 [77786.481797]  ret_from_fork+0x2c/0x50 To avoid this, complete all completion handlers before returning the destroy QP. If free_cq is called soon after destroy_qp, IB stack will cancel the CQ work before invoking the destroy_cq verb and this will prevent any race mentioned.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 24, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

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

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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.11affected
    • 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and later · before b79a0e71d6e8692e0b6da05f8aaa7d69191cf7e7affected · git
    • 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and later · before b8500538b8f5b2cd86b02754c8de83eaa7a2d6baaffected · git
    • 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and later · before 7faa6097694164380ed19600c7a7993d071270b9affected · git
    • 1ac5a404797523cedaf424a3aaa3cf8f9548dff8 and later · before b5bbc6551297447d3cca55cf907079e206e9cd82affected · git
    • before 4.11not affected · semver
    • 5.15.124 and later · up to and including 5.15.*not affected · semver
    • 6.1.43 and later · up to and including 6.1.*not affected · semver
    • 6.4.8 and later · up to and including 6.4.*not affected · semver
    • 6.5 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10

+64

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54043Dec 24, 2025 · iommufd: Do not add the same hwpt to the ioas->hwpt_list twice
    35Monitor
  • ← EarlierCVE-2023-54046Dec 24, 2025 · crypto: essiv - Handle EBUSY correctly
    31Monitor
  • Later →CVE-2023-54062Dec 24, 2025 · ext4: fix invalid free tracking in ext4_xattr_move_to_block()
    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 Linux7faa6097694164380ed19600c7a7993d071270b9Vendor (CNA)
Linux Linuxb5bbc6551297447d3cca55cf907079e206e9cd82Vendor (CNA)
Linux Linuxb79a0e71d6e8692e0b6da05f8aaa7d69191cf7e7Vendor (CNA)
Linux Linuxb8500538b8f5b2cd86b02754c8de83eaa7a2d6baVendor (CNA)
almalinux:bpftool4.18.0-553.171.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.171.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo-common-x86_640:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-devel0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
rocky linux:kernel0:4.18.0-553.171.1.el8_10 · Rocky Linux:8Package registry (OSV)

+1

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 researchers

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records