LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53285: ext4: add bounds checking in get_max_inline_xattr_value_size()

In the Linux kernel, the following vulnerability has been resolved: ext4: add bounds checking in get_max_inline_xattr_value_size() Normally the extended attributes in the inode body would have been checked when the inode is first opened, but if someone is writing to the block device while the file system is mounted, it's possible for the inode table to get corrupted. Add bounds checking to avoid reading beyond the end of allocated memory if this happens.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-53285 is a Linux ext4 kernel flaw where corrupted inode extended-attribute data could make the kernel read past allocated memory. It requires local access and a condition where a mounted filesystem’s block device is being written or corrupted. Impact is rated high because kernel confidentiality, integrity, and availability are all in scope.

Executive priority

Treat as high priority for Linux fleets with shared-user access, untrusted workloads, or operational patterns involving block-device writes. It is less urgent than a remote code execution issue, but kernel-level impact justifies scheduled remediation through normal kernel patch channels.

Technical view

The ext4 function get_max_inline_xattr_value_size() lacked bounds checking when handling inline extended attributes in an inode body. If inode table contents become corrupted after the inode is opened, the kernel could read beyond allocated memory. Stable Linux commits add bounds checks. The CVSS vector is local, low complexity, low privileges, no user interaction, with high CIA impact.

Likely exposure

Exposure is most relevant to Linux systems using ext4 where local users or privileged processes can influence raw block-device writes while filesystems are mounted. Exact exposure depends on kernel branch, distribution backports, and whether the referenced stable fixes are present.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The scenario is local, not remotely reachable by itself. The vulnerability appears tied to filesystem corruption or unsafe writes to a mounted block device, so practical abuse depends on local access and device-write capability.

Researcher notes

The source bundle identifies stable Linux fixes but does not provide exploit details, CWE mapping, or distro-specific fixed package versions. The affected-version data is broad and branch-oriented, so validation should focus on actual kernel patch state rather than raw version strings alone.

Mitigation direction

  • Update to a vendor kernel containing the referenced ext4 bounds-checking fixes.
  • Follow distribution advisories for backported fixes before relying on upstream version numbers.
  • Restrict raw block-device write access on production systems.
  • Avoid writing directly to mounted filesystem block devices.
  • Prioritize hosts where untrusted local users or workloads exist.

Validation and detection

  • Inventory Linux hosts using ext4 filesystems.
  • Confirm kernel package includes the relevant stable ext4 fix commit or vendor backport.
  • Review local permissions for block devices backing mounted filesystems.
  • Check whether untrusted users or containers can reach device-write paths.
  • Monitor vendor security advisories for branch-specific fixed versions.
Prepared
Confidence
medium
Sources
11

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-53285 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.8 (3.1)
Known Exploited
No
Published

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

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
1ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-53285Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947, 67cf5b09a46f72e048501b84996f2f77bc42e947unaffected
LinuxLinux3.8, 0, 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16, 6.3.3, 6.4affected
Weakness

CWE details

No CWE listed

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