Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46114: RDMA/rxe: Reject non-8-byte ATOMIC_WRITE payloads

Noroxi assessment

Priority: Monitor (action score 30/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.46% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 105bf79a23b85cf3a761d18a4f3e10ce88526bc1, 1114c87aa6f195cf07da55a27b2122ae26557b26, 539cabb7b2d8ba70f55bba91db55faef11c2a6d7; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 105bf79a23b85cf3a761d18a4f3e10ce88526bc1, 1114c87aa6f195cf07da55a27b2122ae26557b26, 539cabb7b2d8ba70f55bba91db55faef11c2a6d7; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 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: Reject non-8-byte ATOMIC_WRITE payloads atomic_write_reply() at drivers/infiniband/sw/rxe/rxe_resp.c unconditionally dereferences 8 bytes at payload_addr(pkt): value = *(u64 *)payload_addr(pkt); check_rkey() previously accepted an ATOMIC_WRITE request with pktlen == resid == 0 because the length validation only compared pktlen against resid. A remote initiator that sets the RETH length to 0 therefore reaches atomic_write_reply() with a zero-byte logical payload, and the responder reads sizeof(u64) bytes from past the logical end of the packet into skb->head tailroom, then writes those 8 bytes into the attacker's MR via rxe_mr_do_atomic_write(). That is a remote disclosure of 4 bytes of kernel tailroom per probe (the other 4 bytes are the packet's own trailing ICRC). IBA oA19-28 defines ATOMIC_WRITE as exactly 8 bytes. Anything else is protocol-invalid. Hoist a strict length check into check_rkey() so the responder never reaches the unchecked dereference, and keep the existing WRITE-family length logic for the normal RDMA WRITE path. Reproduced on mainline with an unmodified rxe driver: a sustained zero-length ATOMIC_WRITE probe repeatedly leaks adjacent skb head-buffer bytes into the attacker's MR, including recognisable kernel strings and partial kernel-direct-map pointer words. With this patch applied the responder rejects the PDU and the MR stays all-zero.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
May 28, 2026
Updated
Oct 19, 2026
EPSS
0.4% · 40th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.5
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-2026-46114

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.

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 kernel6.2 and later · before 6.6.140
  • linux linux kernel6.7 and later · before 6.12.88
  • linux linux kernel6.13 and later · before 6.18.30
  • linux linux kernel6.19 and later · before 7.0.7
  • linux linux kernel7.1

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

    • 6.2affected
    • 034e285f8b99062a0cf29112e1232154a6a44aa5 and later · before 539cabb7b2d8ba70f55bba91db55faef11c2a6d7affected · git
    • 034e285f8b99062a0cf29112e1232154a6a44aa5 and later · before d415fce3fcde6d7aeea6c25362a395b905811452affected · git
    • 034e285f8b99062a0cf29112e1232154a6a44aa5 and later · before 105bf79a23b85cf3a761d18a4f3e10ce88526bc1affected · git
    • 034e285f8b99062a0cf29112e1232154a6a44aa5 and later · before 7ec1ed4747f5f99f8b797bb438c5efd36079fad5affected · git
    • 034e285f8b99062a0cf29112e1232154a6a44aa5 and later · before 1114c87aa6f195cf07da55a27b2122ae26557b26affected · git
    • before 6.2not affected · semver
    • 6.6.140 and later · up to and including 6.6.*not affected · semver
    • 6.12.88 and later · up to and including 6.12.*not affected · semver
    • 6.18.30 and later · up to and including 6.18.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-develbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-cross-headersbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-debug-develbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.49.1.el9_85.14.0-687.49.1.el9_8

+96

Same product

linux: all records

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-2026-46111May 28, 2026 · Bluetooth: hci_conn: fix potential UAF in create_big_sync
    31Monitor
  • ← EarlierCVE-2026-46113May 28, 2026 · KVM: x86: Fix shadow paging use-after-free due to unexpected GFN
    35Monitor
  • Later →CVE-2026-46115May 28, 2026 · block: add pgmap check to biovec_phys_mergeable
    39Monitor

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 Linux105bf79a23b85cf3a761d18a4f3e10ce88526bc1Vendor (CNA)
Linux Linux1114c87aa6f195cf07da55a27b2122ae26557b26Vendor (CNA)
Linux Linux539cabb7b2d8ba70f55bba91db55faef11c2a6d7Vendor (CNA)
Linux Linux7ec1ed4747f5f99f8b797bb438c5efd36079fad5Vendor (CNA)
Linux Linuxd415fce3fcde6d7aeea6c25362a395b905811452Vendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.49.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.88-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-687.49.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+2

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

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

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 (4 more)

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

All records