LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53722: md: raid1: fix potential OOB in raid1_remove_disk()

In the Linux kernel, the following vulnerability has been resolved: md: raid1: fix potential OOB in raid1_remove_disk() If rddev->raid_disk is greater than mddev->raid_disks, there will be an out-of-bounds in raid1_remove_disk(). We have already found similar reports as follows: 1) commit d17f744e883b ("md-raid10: fix KASAN warning") 2) commit 1ebc2cec0b7d ("dm raid: fix KASAN warning in raid5_remove_disk") Fix this bug by checking whether the "number" variable is valid.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel RAID1 bug that could cause out-of-bounds memory access when removing a disk from an md RAID1 array under an invalid raid_disk value. The source does not provide CVSS, impact details, or active exploitation evidence.

Executive priority

Prioritize normal kernel patch management, with faster handling for production systems using software RAID1. Current evidence does not justify emergency action unless internal exposure is broad or the vendor rates the issue higher.

Technical view

The resolved issue is in md/raid1 raid1_remove_disk(). If rddev->raid_disk exceeds mddev->raid_disks, the function can index out of bounds. Kernel stable fixes add validation of the computed disk number before use, mirroring prior KASAN-warning fixes in related RAID code.

Likely exposure

Exposure is most relevant to Linux systems using md RAID1 or downstream kernels containing the affected RAID1 code. The bundle lists Linux kernel versions and stable commit references, but downstream vendor backports must be checked individually.

Exploitation context

The bundle does not cite public exploitation, KEV listing, exploit code, or a complete impact chain. Treat this as a kernel memory-safety issue requiring patch verification, not as confirmed actively exploited risk.

Researcher notes

The available record is sparse: no CVSS, CWE, privilege requirement, crash details, or exploitability analysis. The strongest facts are the vulnerable code path, out-of-bounds condition, KASAN context, and stable kernel fix references.

Mitigation direction

  • Apply vendor-supported kernel updates containing the referenced stable fixes.
  • Prioritize Linux systems using md RAID1 storage configurations.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Schedule reboots or live-patching according to vendor kernel update requirements.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify hosts using md RAID1 arrays or affected kernel RAID modules.
  • Confirm the relevant stable fix commit or vendor backport is present.
  • Review vendor security advisories for package-specific fixed versions.
Prepared
Confidence
medium
Sources
10

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-2023-53722 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
9Source 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
LinuxLinuxb8321b68d1445f308324517e45fb0a5c2b48e271, b8321b68d1445f308324517e45fb0a5c2b48e271, b8321b68d1445f308324517e45fb0a5c2b48e271, b8321b68d1445f308324517e45fb0a5c2b48e271, b8321b68d1445f308324517e45fb0a5c2b48e271, b8321b68d1445f308324517e45fb0a5c2b48e271, b8321b68d1445f308324517e45fb0a5c2b48e271, b8321b68d1445f308324517e45fb0a5c2b48e271unaffected
LinuxLinux3.3, 0, 4.14.326, 4.19.295, 5.4.257, 5.10.197, 5.15.133, 6.1.55, 6.5.5, 6.6affected
Weakness

CWE details

No CWE listed

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