LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49743: ovl: Use "buf" flexible array for memcpy() destination

In the Linux kernel, the following vulnerability has been resolved: ovl: Use "buf" flexible array for memcpy() destination The "buf" flexible array needs to be the memcpy() destination to avoid false positive run-time warning from the recent FORTIFY_SOURCE hardening: memcpy: detected field-spanning write (size 93) of single field "&fh->fb" at fs/overlayfs/export.c:799 (size 21)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-49743 concerns a Linux kernel overlayfs change that redirects a memcpy() destination to a flexible array member. The provided sources describe it as avoiding a FORTIFY_SOURCE runtime warning, not as an active attack or business-impacting exploit.

Executive priority

Treat as a kernel maintenance item unless your Linux vendor rates it higher. There is no supplied evidence of active exploitation, public exploit use, or confirmed business impact, but kernel fixes should still enter normal patch governance.

Technical view

In fs/overlayfs/export.c, the fix changes the memcpy() destination to the fh->buf flexible array instead of a smaller field, addressing a FORTIFY_SOURCE field-spanning write warning. The bundle provides no CVSS, CWE, crash condition, privilege impact, or exploit path.

Likely exposure

Exposure is limited to Linux kernel versions matching the source record's affected entries and using the relevant overlayfs code path. The bundle does not identify affected distributions, appliances, cloud images, or required configuration beyond Linux kernel overlayfs.

Exploitation context

No active exploitation is supported by the provided evidence. The record is not marked KEV, and the cited description only mentions a FORTIFY_SOURCE runtime warning fix rather than exploitation or weaponized abuse.

Researcher notes

The public bundle is sparse. It frames the issue as correcting a memcpy destination to satisfy FORTIFY_SOURCE hardening. Severity, CWE, exploitability, and impact are not established in the provided sources, so conclusions should remain conservative.

Mitigation direction

  • Check Linux kernel vendor advisories for backported fixes covering CVE-2022-49743.
  • Prioritize kernel updates that include the cited stable overlayfs commits.
  • Track distribution-specific package names and fixed build numbers before deployment.
  • Avoid inventing compensating controls; no source-provided workaround is named.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Confirm whether deployed kernels include one of the cited stable fixes.
  • Review vendor security notices for distribution-specific CVE mapping.
  • Check whether overlayfs is enabled or used on affected systems.
Prepared
Confidence
medium
Sources
6

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-2022-49743 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
5Source 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
LinuxLinuxcbe7fba8edfc8cb8e621599e376f8ac5c224fa72, cbe7fba8edfc8cb8e621599e376f8ac5c224fa72, cbe7fba8edfc8cb8e621599e376f8ac5c224fa72, cbe7fba8edfc8cb8e621599e376f8ac5c224fa72unaffected
LinuxLinux5.5, 0, 5.10.248, 5.15.93, 6.1.11, 6.2affected
Weakness

CWE details

No CWE listed

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