LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26973: fat: fix uninitialized field in nostale filehandles

In the Linux kernel, the following vulnerability has been resolved: fat: fix uninitialized field in nostale filehandles When fat_encode_fh_nostale() encodes file handle without a parent it stores only first 10 bytes of the file handle. However the length of the file handle must be a multiple of 4 so the file handle is actually 12 bytes long and the last two bytes remain uninitialized. This is not great at we potentially leak uninitialized information with the handle to userspace. Properly initialize the full handle length.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2024-26973 is a Linux kernel information leak in the FAT filesystem code. In a narrow file-handle case, two bytes that were not initialized could be returned to userspace. This is not listed as actively exploited, and no CVSS score is provided in the sources.

Executive priority

Treat as routine kernel patching unless FAT usage is widespread or the system is a sensitive multi-user host. Business urgency is lower than remotely exploitable kernel flaws, but uninitialized memory leaks should still be removed through standard update cycles.

Technical view

In fat_encode_fh_nostale(), file handles encoded without a parent stored only 10 bytes while the handle length is 12 bytes. The remaining two bytes could contain uninitialized kernel memory and be exposed to userspace. Kernel stable commits initialize the full handle length.

Likely exposure

Exposure is most relevant on Linux systems with affected kernels where FAT filesystems are used and file-handle encoding paths are reachable. The source data lists multiple Linux kernel versions as affected, but distribution backports may change practical exposure.

Exploitation context

The sources describe potential information disclosure to userspace, not privilege escalation or remote code execution. KEV is false, and the provided sources do not report active exploitation or public weaponization.

Researcher notes

The issue is a two-byte uninitialized memory disclosure in FAT nostale filehandle encoding. The record lacks CVSS, CWE, and detailed attack prerequisites. Validate against exact kernel trees or distribution backport metadata rather than relying only on upstream version numbers.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Use distribution security advisories to confirm backported fixes.
  • Prioritize systems using FAT filesystems or products identified by vendor advisories.
  • For appliances, follow the vendor-specific Siemens guidance where applicable.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Check whether FAT filesystems are mounted or used in affected environments.
  • Confirm installed kernels include the referenced stable commits or vendor backports.
  • Review Debian LTS and vendor advisories for package-specific status.
Prepared
Confidence
medium
Sources
8

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-26973 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
3ADP providers
14Source links

SSVC decision data

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2unaffected
LinuxLinux3.10, 0, 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

No CWE listed

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