LiveActive security incident?Get immediate response
CVE Record

CVE-2024-44966: binfmt_flat: Fix corruption when not offsetting data start

In the Linux kernel, the following vulnerability has been resolved: binfmt_flat: Fix corruption when not offsetting data start Commit 04d82a6d0881 ("binfmt_flat: allow not offsetting data start") introduced a RISC-V specific variant of the FLAT format which does not allocate any space for the (obsolete) array of shared library pointers. However, it did not disable the code which initializes the array, resulting in the corruption of sizeof(long) bytes before the DATA segment, generally the end of the TEXT segment. Introduce MAX_SHARED_LIBS_UPDATE which depends on the state of CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET to guard the initialization of the shared library pointer region so that it will only be initialized if space is reserved for it.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel bug can corrupt memory when loading a particular FLAT executable format on specially configured RISC-V systems. A local, low-privileged user may be able to affect confidentiality, integrity, or availability. This is high severity, but the supplied sources do not establish widespread exposure or active exploitation.

Executive priority

Treat this as a high-priority, targeted kernel update rather than an organization-wide emergency. Quickly identify specially configured RISC-V systems, especially those allowing untrusted local users or workloads. Patch confirmed exposures through supported vendor channels; broad Linux fleets without this architecture and configuration are unlikely to be affected.

Technical view

The RISC-V FLAT variant enabled by CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET reserves no shared-library pointer array, yet affected code still initializes that region. This writes sizeof(long) bytes before the DATA segment, generally corrupting the end of TEXT. The cited kernel change guards initialization according to whether space was reserved.

Likely exposure

Exposure appears limited to Linux systems using RISC-V, the FLAT binary loader, and CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET. The bundle lists affected releases between 5.13 and 6.11, including several stable versions, but does not provide sufficiently clear version-range semantics to determine every vulnerable build.

Exploitation context

CVSS 3.1 rates this 7.8: local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. CISA KEV status is false in the supplied bundle, and no cited source establishes active exploitation or a public exploit.

Researcher notes

The flaw was introduced by commit 04d82a6d0881 and concerns an out-of-bounds initialization adjacent to FLAT DATA. The source bundle supplies multiple stable-tree correction commits but ambiguous affected-version data. Validate using architecture, kernel configuration, provenance, and vendor backport status instead of version strings alone.

Mitigation direction

  • Install a vendor-supported kernel containing the cited upstream correction.
  • Confirm the fixed package or build with your Linux distributor's current guidance.
  • Prioritize specially configured RISC-V systems that execute FLAT binaries.
  • Limit untrusted local code execution on potentially affected hosts until remediation.

Validation and detection

  • Identify RISC-V hosts and record their running kernel versions.
  • Check kernel configuration for BINFMT_FLAT and CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET.
  • Compare kernel source or vendor packages with the cited stable fixes.
  • After updating, reboot and verify the corrected kernel is running.
Prepared
Confidence
medium
Sources
8

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-2024-44966 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
2ADP providers
7Source 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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-44966Attack 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
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8, 04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8, 04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8, 04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8, 04d82a6d0881ef1ab1e9f66f10805177ee2fb1e8unaffected
LinuxLinux5.13, 0, 5.15.165, 6.1.106, 6.6.47, 6.10.6, 6.11affected
Weakness

CWE details

No CWE listed

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