ovl: Use "buf" flexible array for memcpy() destination

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

• cpe linux/linux kernelversion unspecified
• vendor Linux Linuxversion unspecified

How to fix CVE-2022-49743

• Recommended remediation

  No required-action text, fix commit, or clear fixed-version range is stored yet.

• Official advisories

  • CIRCL Vulnerability Lookup · vulnerability.circl.lu
  • CVE.org · cve.org
  • FIRST EPSS · first.org
  • NIST NVD · nvd.nist.gov

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Code

The project this record applies to. Exploit listings stay in References.

• Repository · git.kernel.org
• Repository · git.kernel.org
• Repository · git.kernel.org
• Repository · git.kernel.org

Timeline

Detection, updates, and resolution for this record.

1. Mar 27, 2025 · CIRCL Vulnerability Lookup

   Detected

   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)

2. Oct 15, 2026 · CIRCL Vulnerability Lookup

   Updated

   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)

3. Oct 15, 2026 · NIST NVD

   Updated

   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)

Sources

• CIRCL Vulnerability LookupVulnerability recordCVE-2022-49743

  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: dete

  vulnerability.circl.lu
• CVE.orgVulnerability recordCVE-2022-49743

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2022-49743

  30-day exploitation probability 0.4%

  first.org
• NIST NVDVulnerability recordCVE-2022-49743

  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:

  nvd.nist.gov

References

• Reference · git.kernel.org
• Reference · git.kernel.org
• Reference · git.kernel.org
• Reference · git.kernel.org

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.