Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54028: RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task"

Noroxi assessment

Priority: Monitor (action score 0/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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 0d938264fcfe4927e54f0e519da05af1d5d720b4, 3236221bb8e4de8e3d0c8385f634064fb26b8e38, b2b1ddc457458fecd1c6f385baa9fbda5f0c63ad.

Low priority for now. Upgrade to Linux Linux 0d938264fcfe4927e54f0e519da05af1d5d720b4, 3236221bb8e4de8e3d0c8385f634064fb26b8e38, b2b1ddc457458fecd1c6f385baa9fbda5f0c63ad 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/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task" In the function rxe_create_qp(), rxe_qp_from_init() is called to initialize qp, internally things like rxe_init_task are not setup until rxe_qp_init_req(). If an error occurred before this point then the unwind will call rxe_cleanup() and eventually to rxe_qp_do_cleanup()/rxe_cleanup_task() which will oops when trying to access the uninitialized spinlock. If rxe_init_task is not executed, rxe_cleanup_task will not be called.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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

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.8affected
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 3236221bb8e4de8e3d0c8385f634064fb26b8e38affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before c8473cd5b301279a41dc75e5afb26b3d5223b6c7affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before 0d938264fcfe4927e54f0e519da05af1d5d720b4affected · git
    • 8700e3e7c4857d28ebaa824509934556da0b3e76 and later · before b2b1ddc457458fecd1c6f385baa9fbda5f0c63adaffected · git
    • before 4.8not affected · semver
    • 6.1.32 and later · up to and including 6.1.*not affected · semver
    • 6.2.15 and later · up to and including 6.2.*not affected · semver
    • 6.3.2 and later · up to and including 6.3.*not affected · semver
    • 6.4 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
Debian:12linuxbefore 6.1.37-16.1.37-1
Debian:13linuxbefore 6.3.7-16.3.7-1

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-54026Dec 24, 2025 · opp: Fix use-after-free in lazy_opp_tables after probe deferral
    31Monitor
  • ← EarlierCVE-2023-54027Dec 24, 2025 · iio: core: Prevent invalid memory access when there is no parent
    0Monitor
  • Later →CVE-2023-54030Dec 24, 2025 · io_uring/net: don't overflow multishot recv
    0Monitor

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 Linux0d938264fcfe4927e54f0e519da05af1d5d720b4Vendor (CNA)
Linux Linux3236221bb8e4de8e3d0c8385f634064fb26b8e38Vendor (CNA)
Linux Linuxb2b1ddc457458fecd1c6f385baa9fbda5f0c63adVendor (CNA)
Linux Linuxc8473cd5b301279a41dc75e5afb26b3d5223b6c7Vendor (CNA)
debian:linux6.1.37-1 · Debian:12Package 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.

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

Show all references (3 more)

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

All records