LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23285: drbd: fix null-pointer dereference on local read error

In the Linux kernel, the following vulnerability has been resolved: drbd: fix null-pointer dereference on local read error In drbd_request_endio(), READ_COMPLETED_WITH_ERROR is passed to __req_mod() with a NULL peer_device: __req_mod(req, what, NULL, &m); The READ_COMPLETED_WITH_ERROR handler then unconditionally passes this NULL peer_device to drbd_set_out_of_sync(), which dereferences it, causing a null-pointer dereference. Fix this by obtaining the peer_device via first_peer_device(device), matching how drbd_req_destroy() handles the same situation.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash systems using DRBD when a local read error triggers a bad null pointer path. The public record does not provide CVSS, severity, or exploitation evidence. Business urgency depends on whether DRBD-backed replicated storage is in use on affected kernels.

Executive priority

Treat as targeted operational risk for DRBD storage infrastructure, not a broad internet-facing emergency based on current evidence. Prioritize patch planning for systems where a kernel crash would disrupt availability or recovery objectives.

Technical view

In drbd_request_endio(), READ_COMPLETED_WITH_ERROR calls __req_mod() with a NULL peer_device. The handler passes that NULL value into drbd_set_out_of_sync(), causing a null-pointer dereference. The fix obtains peer_device through first_peer_device(device), matching existing cleanup handling.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with DRBD present and exercised, especially during local read errors. Organizations not using DRBD are likely lower priority, but should still map vendor kernels to the fixed upstream stable commits.

Exploitation context

The bundle marks KEV as false and provides no public exploitation claims. The described impact is a kernel null-pointer dereference, most plausibly a denial-of-service condition. No source here supports remote exploitation, privilege escalation, or weaponized exploit availability.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. No CVSS, CWE, affected CPEs, exploit status, or distro package mapping is provided in the bundle, so validation should focus on component presence and kernel lineage.

Mitigation direction

  • Update to a vendor kernel containing the referenced DRBD fix.
  • Track Linux distribution advisories for exact package versions and backports.
  • Prioritize DRBD-backed storage nodes and clustered replication environments.
  • If DRBD is unnecessary, keep it disabled until systems are updated.

Validation and detection

  • Inventory Linux kernel versions on systems using replicated block storage.
  • Confirm whether DRBD is built, loaded, or actively configured.
  • Map installed kernels to vendor fixes or referenced stable commits.
  • Review kernel logs for DRBD read errors and null-pointer oops events.
Prepared
Confidence
medium
Sources
7

Public sources used

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-23285 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0d11f3cf279c5ad20a41f29242f170ba3c02f2da, 0d11f3cf279c5ad20a41f29242f170ba3c02f2da, 0d11f3cf279c5ad20a41f29242f170ba3c02f2da, 0d11f3cf279c5ad20a41f29242f170ba3c02f2da, 0d11f3cf279c5ad20a41f29242f170ba3c02f2daunaffected
LinuxLinux6.4, 0, 6.6.130, 6.12.77, 6.18.17, 6.19.7, 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.