LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53541: mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write

In the Linux kernel, the following vulnerability has been resolved: mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write When the oob buffer length is not in multiple of words, the oob write function does out-of-bounds read on the oob source buffer at the last iteration. Fix that by always checking length limit on the oob buffer read and fill with 0xff when reaching the end of the buffer to the oob registers.

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 flaw in the Broadcom raw NAND driver. Under specific out-of-band write conditions, the kernel could read past the supplied buffer. The public record does not provide CVSS, CWE, impact details, or evidence of active exploitation.

Executive priority

Handle through the kernel patch management process, with priority for embedded or appliance-like Linux systems using Broadcom NAND. Escalate only if vendor guidance shows reachable exposure or higher impact.

Technical view

The brcmnand OOB write path can perform an out-of-bounds read when the OOB buffer length is not word-aligned. The fix bounds each source-buffer read and writes 0xff after the buffer ends.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the Broadcom raw NAND driver present and used. Generic Linux systems without this driver path are less likely exposed, but the source data does not define deployment scope.

Exploitation context

No active exploitation is supported by the provided sources. The record is not in KEV and does not describe exploitability, required privileges, attack vector, or practical impact.

Researcher notes

The evidence is limited to the CVE record and Linux stable commit references. Severity, CWE, exploitability, and operational impact are not supplied, so risk should be validated against actual kernel configuration and hardware use.

Mitigation direction

  • Update to a kernel or vendor build containing the referenced stable fixes.
  • Check Linux distribution or device vendor advisories for backported fixes.
  • Prioritize review of systems using Broadcom NAND hardware or brcmnand.
  • Do not rely on a generic workaround; none is named in the sources.

Validation and detection

  • Inventory Linux kernel versions across affected devices and images.
  • Confirm whether the brcmnand raw NAND driver is built or loaded.
  • Compare vendor kernel changelogs against the referenced stable commits.
  • Verify the OOB write fix bounds reads and pads with 0xff.
  • Document KEV status as not listed in the provided bundle.
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-53541 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
LinuxLinux27c5b17cd1b10564fa36f8f51e4b4b41436ecc32, 27c5b17cd1b10564fa36f8f51e4b4b41436ecc32, 27c5b17cd1b10564fa36f8f51e4b4b41436ecc32, 27c5b17cd1b10564fa36f8f51e4b4b41436ecc32, 27c5b17cd1b10564fa36f8f51e4b4b41436ecc32, 27c5b17cd1b10564fa36f8f51e4b4b41436ecc32, 27c5b17cd1b10564fa36f8f51e4b4b41436ecc32, 27c5b17cd1b10564fa36f8f51e4b4b41436ecc32unaffected
LinuxLinux4.2, 0, 4.14.326, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.54, 6.5.4, 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.