Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-54056kheaders: Use array declaration instead of char

Description

In the Linux kernel, the following vulnerability has been resolved: kheaders: Use array declaration instead of char Under CONFIG_FORTIFY_SOURCE, memcpy() will check the size of destination and source buffers. Defining kernel_headers_data as "char" would trip this check. Since these addresses are treated as byte arrays, define them as arrays (as done everywhere else). This was seen with: $ cat /sys/kernel/kheaders.tar.xz >> /dev/null detected buffer overflow in memcpy kernel BUG at lib/string_helpers.c:1027! ... RIP: 0010:fortify_panic+0xf/0x20 [...] Call Trace: <TASK> ikheaders_read+0x45/0x50 [kheaders] kernfs_fop_read_iter+0x1a4/0x2f0 ...

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.23% · top 87% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 43d8ce9d65a54846d378545770991e65838981e0 – < 719459877d58c8aced5845c1e5b98d8d87d09197
    • affected 43d8ce9d65a54846d378545770991e65838981e0 – < fcd2da2e6bf2640a31a2a5b118b50dc3635c707b
    • affected 43d8ce9d65a54846d378545770991e65838981e0 – < 4a07d2d511e2703efd4387891d49e0326f1157f3
    • affected 43d8ce9d65a54846d378545770991e65838981e0 – < b9f6845a492de20679b84bda6b08be347c5819da
    • affected 43d8ce9d65a54846d378545770991e65838981e0 – < d6d1af6b8611801b585c53c0cc63626c8d339e96
    • affected 43d8ce9d65a54846d378545770991e65838981e0 – < 82d2e01b95c439fe55fab5e04fc83387c42d3a48
    • affected 43d8ce9d65a54846d378545770991e65838981e0 – < b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 5.4.243 – ≤ 5.4.*
    • unaffected 5.10.180 – ≤ 5.10.*
    • unaffected 5.15.111 – ≤ 5.15.*
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54056 badge
[![CVE-2023-54056](https://cveledger.app/badge/CVE-2023-54056.svg)](https://cveledger.app/cve/CVE-2023-54056)

Record last updated .