LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53397: modpost: fix off by one in is_executable_section()

In the Linux kernel, the following vulnerability has been resolved: modpost: fix off by one in is_executable_section() The > comparison should be >= to prevent an out of bounds array access.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-53397 is a Linux kernel issue in modpost, a kernel build component. An off-by-one check can access memory outside an array. The published impact is availability only, requiring local access and low privileges. There is no KEV listing or cited evidence of active exploitation.

Executive priority

Treat this as a routine but real Linux maintenance item. It is not currently evidenced as internet-exploited, but availability impact warrants inclusion in normal kernel patch cycles, especially for shared build systems and multi-user Linux hosts.

Technical view

The flaw is CWE-193 in is_executable_section(), where a greater-than comparison should be greater-than-or-equal to prevent out-of-bounds array access. The CVSS vector is local, low complexity, low privilege, no user interaction, unchanged scope, and high availability impact with no confidentiality or integrity impact.

Likely exposure

Exposure appears limited to affected Linux kernel versions or source/build environments using vulnerable modpost code. The source bundle does not identify affected distributions, cloud services, appliances, or remotely reachable attack surfaces.

Exploitation context

No source in the bundle reports exploitation in the wild, and KEV is false. Based on CVSS, exploitation requires local access and low privileges. The bundle does not provide a proven attack scenario beyond availability impact.

Researcher notes

The evidence is narrow: a kernel stable fix and CVSS metadata. The affected version listing is upstream-oriented and distribution mapping is not supplied. Validate through vendor advisories and package metadata before declaring specific fleet exposure.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Track downstream distribution advisories for exact package versions and backports.
  • Restrict local access to kernel build environments where practical.
  • Avoid processing untrusted kernel/module build inputs on vulnerable systems.
  • Prioritize availability-sensitive build and operations hosts.

Validation and detection

  • Inventory Linux kernel versions and source packages against the affected version data.
  • Check vendor changelogs for CVE-2023-53397 or the modpost fix title.
  • Confirm scanners account for distribution backports, not only upstream version strings.
  • Verify build systems have received updated kernel sources or packages.
  • Review exposure assumptions for systems allowing low-privileged local users.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-193: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-53397 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
9Source links

SSVC decision data

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

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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-53397Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
LinuxLinux52dc0595d540155436d91811f929bdc8afd6a2a1, 52dc0595d540155436d91811f929bdc8afd6a2a1, 52dc0595d540155436d91811f929bdc8afd6a2a1, 52dc0595d540155436d91811f929bdc8afd6a2a1, 52dc0595d540155436d91811f929bdc8afd6a2a1, 52dc0595d540155436d91811f929bdc8afd6a2a1, 52dc0595d540155436d91811f929bdc8afd6a2a1, 52dc0595d540155436d91811f929bdc8afd6a2a1unaffected
LinuxLinux4.1, 0, 4.14.322, 5.4.251, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

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

CWE-193 · source CWE mapping

Off-by-one Error

Off-by-one Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.