CVE-2023-54056: kheaders: Use array declaration instead of char
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 4a07d2d511e2703efd4387891d49e0326f1157f3, 719459877d58c8aced5845c1e5b98d8d87d09197, 82d2e01b95c439fe55fab5e04fc83387c42d3a48.
Low priority for now. Upgrade to Linux Linux 4a07d2d511e2703efd4387891d49e0326f1157f3, 719459877d58c8aced5845c1e5b98d8d87d09197, 82d2e01b95c439fe55fab5e04fc83387c42d3a48 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 ...
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.2affected
- 43d8ce9d65a54846d378545770991e65838981e0 and later · before 719459877d58c8aced5845c1e5b98d8d87d09197affected · git
- 43d8ce9d65a54846d378545770991e65838981e0 and later · before fcd2da2e6bf2640a31a2a5b118b50dc3635c707baffected · git
- 43d8ce9d65a54846d378545770991e65838981e0 and later · before 4a07d2d511e2703efd4387891d49e0326f1157f3affected · git
- 43d8ce9d65a54846d378545770991e65838981e0 and later · before b9f6845a492de20679b84bda6b08be347c5819daaffected · git
- 43d8ce9d65a54846d378545770991e65838981e0 and later · before d6d1af6b8611801b585c53c0cc63626c8d339e96affected · git
- 43d8ce9d65a54846d378545770991e65838981e0 and later · before 82d2e01b95c439fe55fab5e04fc83387c42d3a48affected · git
- 43d8ce9d65a54846d378545770991e65838981e0 and later · before b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fbaffected · git
- before 5.2not affected · semver
- 5.4.243 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54053Dec 24, 2025 · wifi: iwlwifi: pcie: fix possible NULL pointer dereference0Monitor
- ← EarlierCVE-2023-54055Dec 24, 2025 · RDMA/irdma: Fix memory leak of PBLE objects0Monitor
- Later →CVE-2023-54057Dec 24, 2025 · iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4a07d2d511e2703efd4387891d49e0326f1157f3 | Vendor (CNA) |
| Linux Linux | 719459877d58c8aced5845c1e5b98d8d87d09197 | Vendor (CNA) |
| Linux Linux | 82d2e01b95c439fe55fab5e04fc83387c42d3a48 | Vendor (CNA) |
| Linux Linux | b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb | Vendor (CNA) |
| Linux Linux | b9f6845a492de20679b84bda6b08be347c5819da | Vendor (CNA) |
| Linux Linux | d6d1af6b8611801b585c53c0cc63626c8d339e96 | Vendor (CNA) |
| Linux Linux | fcd2da2e6bf2640a31a2a5b118b50dc3635c707b | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/719459877d58c8aced5845c1e5b98d8d87d09197
- git.kernel.org/stable/c/82d2e01b95c439fe55fab5e04fc83387c42d3a48
- git.kernel.org/stable/c/b69edab47f1da8edd8e7bfdf8c70f51a2a5d89fb
- git.kernel.org/stable/c/b9f6845a492de20679b84bda6b08be347c5819da
- git.kernel.org/stable/c/d6d1af6b8611801b585c53c0cc63626c8d339e96
- git.kernel.org/stable/c/fcd2da2e6bf2640a31a2a5b118b50dc3635c707b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.