Erroneous KFENCE reports via nofault mishandling
Published Dec 28, 2024 · Updated May 11, 2026
Fault-handling error in affected Linux kernel releases allows local users with /proc/kcore access to trigger erroneous KFENCE reports. On powerpc systems, ___do_page_fault() sends faults from copy_from_kernel_nofault() to KFENCE instead of honoring the nofault exception-table fixup when /proc/kcore crosses an unmapped KFENCE object. Reaching the fault requires root-readable /proc/kcore and an enabled KFENCE allocation; the observed consequence is a false invalid-read or use-after-free diagnostic, not a published memory disclosure.
Summary
What happened
Fault-handling error in affected Linux kernel releases allows local users with /proc/kcore access to trigger erroneous KFENCE reports. On powerpc systems, ___do_page_fault() sends faults from copy_from_kernel_nofault() to KFENCE instead of honoring the nofault exception-table fixup when /proc/kcore crosses an unmapped KFENCE object. Reaching the fault requires root-readable /proc/kcore and an enabled KFENCE allocation; the observed consequence is a false invalid-read or use-after-free diagnostic, not a published memory disclosure.
The record
- CVE
- CVE-2024-56678
- Published
- Dec 28, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 28, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.13
- Affected versionversion=90cbac0e995dd92f7bcf82f74aa50250bf194a4a <06dbbb4d5f7126b6307ab807cbf04ecfc459b933
- Affected versionversion=90cbac0e995dd92f7bcf82f74aa50250bf194a4a <15f78d2c3d1452645bd8b9da909b0ca266f83c43
- Affected versionversion=90cbac0e995dd92f7bcf82f74aa50250bf194a4a <4d2655754e94741b159aa807b72ea85518a65fd5
- Affected versionversion=90cbac0e995dd92f7bcf82f74aa50250bf194a4a <7eaeb7a49b6d16640f9f3c9074c05175d74c710b
- Affected versionversion=90cbac0e995dd92f7bcf82f74aa50250bf194a4a <9ea8d8bf9b625e8ad3be6b0432aecdc549914121
- Affected versionversion=90cbac0e995dd92f7bcf82f74aa50250bf194a4a <e0a470b5733c1fe068d5c58b0bb91ad539604bc6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo