LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43184: rnbd-srv: Zero the rsp buffer before using it

In the Linux kernel, the following vulnerability has been resolved: rnbd-srv: Zero the rsp buffer before using it Before using the data buffer to send back the response message, zero it completely. This prevents any stray bytes to be picked up by the client side when there the message is exchanged between different protocol versions.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux RNBD server may return leftover memory bytes when communicating across different protocol versions. An unauthenticated network client could potentially receive sensitive kernel or process data. The supplied CVSS score is 7.5, reflecting high confidentiality impact without identified integrity or availability impact.

Executive priority

Treat reachable RNBD servers as a high-priority confidentiality issue. Patch promptly where the feature is active or exposed; validate rather than assuming every Linux host is exploitable. Systems without RNBD server use are lower operational priority pending confirmation.

Technical view

The rnbd-srv response buffer was not completely initialized before transmission. During exchanges between different protocol versions, unused response fields could contain stray bytes and disclose memory remotely. The Linux fix zeroes the entire response buffer before constructing and sending the message.

Likely exposure

Exposure is most likely on Linux hosts running the affected RNBD server functionality, particularly where RNBD clients using different protocol versions can reach it. The bundle identifies affected Linux versions but provides ambiguous boundary data, so distribution-specific kernel status must be confirmed.

Exploitation context

The supplied CVSS vector indicates network reachability, low attack complexity, no privileges, and no user interaction. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Absence from KEV does not prove exploitation is impossible.

Researcher notes

The disclosure mechanism is uninitialized response-buffer content exposed during cross-version protocol exchanges. The patch strategy is complete buffer zeroing. The bundle does not identify a CWE, leaked byte count, required message sequence, affected distributions, or confirmed exploitation. Its version list appears boundary-oriented and should not be interpreted as a precise package matrix.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable referenced stable fix.
  • Prioritize reachable RNBD servers handling clients with differing protocol versions.
  • Restrict RNBD access to authorized, trusted networks while updates are pending.
  • Consult the Linux distribution advisory for exact package and branch status.

Validation and detection

  • Inventory hosts running RNBD server functionality and record their kernel packages.
  • Determine whether RNBD endpoints are reachable from untrusted or unauthorized networks.
  • Check each kernel build against distribution guidance and the applicable stable commit.
  • After updating, confirm the running kernel includes the fix and RNBD service remains functional.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-43184 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-43184Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2de6c8de192b9341ffa5e84afe1ce6196d4eef41, 2de6c8de192b9341ffa5e84afe1ce6196d4eef41, 2de6c8de192b9341ffa5e84afe1ce6196d4eef41, 2de6c8de192b9341ffa5e84afe1ce6196d4eef41, 2de6c8de192b9341ffa5e84afe1ce6196d4eef41, 2de6c8de192b9341ffa5e84afe1ce6196d4eef41, 2de6c8de192b9341ffa5e84afe1ce6196d4eef41, 2de6c8de192b9341ffa5e84afe1ce6196d4eef41unaffected
LinuxLinux5.8, 0, 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.