CVE-2024-56678: powerpc/mm/fault: Fix kfence page fault reporting
Noroxi assessment
Priority: Monitor (action score 31/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).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 06dbbb4d5f7126b6307ab807cbf04ecfc459b933, 15f78d2c3d1452645bd8b9da909b0ca266f83c43, 4d2655754e94741b159aa807b72ea85518a65fd5.
Low priority for now. Upgrade to Linux Linux 06dbbb4d5f7126b6307ab807cbf04ecfc459b933, 15f78d2c3d1452645bd8b9da909b0ca266f83c43, 4d2655754e94741b159aa807b72ea85518a65fd5 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: powerpc/mm/fault: Fix kfence page fault reporting copy_from_kernel_nofault() can be called when doing read of /proc/kcore. /proc/kcore can have some unmapped kfence objects which when read via copy_from_kernel_nofault() can cause page faults. Since *_nofault() functions define their own fixup table for handling fault, use that instead of asking kfence to handle such faults. Hence we search the exception tables for the nip which generated the fault. If there is an entry then we let the fixup table handler handle the page fault by returning an error from within ___do_page_fault(). This can be easily triggered if someone tries to do dd from /proc/kcore. eg. dd if=/proc/kcore of=/dev/null bs=1M Some example false negatives: =============================== BUG: KFENCE: invalid read in copy_from_kernel_nofault+0x9c/0x1a0 Invalid read at 0xc0000000fdff0000: copy_from_kernel_nofault+0x9c/0x1a0 0xc00000000665f950 read_kcore_iter+0x57c/0xa04 proc_reg_read_iter+0xe4/0x16c vfs_read+0x320/0x3ec ksys_read+0x90/0x154 system_call_exception+0x120/0x310 system_call_vectored_common+0x15c/0x2ec BUG: KFENCE: use-after-free read in copy_from_kernel_nofault+0x9c/0x1a0 Use-after-free read at 0xc0000000fe050000 (in kfence-#2): copy_from_kernel_nofault+0x9c/0x1a0 0xc00000000665f950 read_kcore_iter+0x57c/0xa04 proc_reg_read_iter+0xe4/0x16c vfs_read+0x320/0x3ec ksys_read+0x90/0x154 system_call_exception+0x120/0x310 system_call_vectored_common+0x15c/0x2ec
- Published
- Dec 28, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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.13affected
- 90cbac0e995dd92f7bcf82f74aa50250bf194a4a and later · before e0a470b5733c1fe068d5c58b0bb91ad539604bc6affected · git
- 90cbac0e995dd92f7bcf82f74aa50250bf194a4a and later · before 4d2655754e94741b159aa807b72ea85518a65fd5affected · git
- 90cbac0e995dd92f7bcf82f74aa50250bf194a4a and later · before 9ea8d8bf9b625e8ad3be6b0432aecdc549914121affected · git
- 90cbac0e995dd92f7bcf82f74aa50250bf194a4a and later · before 7eaeb7a49b6d16640f9f3c9074c05175d74c710baffected · git
- 90cbac0e995dd92f7bcf82f74aa50250bf194a4a and later · before 15f78d2c3d1452645bd8b9da909b0ca266f83c43affected · git
- 90cbac0e995dd92f7bcf82f74aa50250bf194a4a and later · before 06dbbb4d5f7126b6307ab807cbf04ecfc459b933affected · git
- before 5.13not affected · semver
- 5.15.174 and later · up to and including 5.15.*not affected · semver
- 6.1.120 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.13 and later · before 5.15.174
- linux linux kernel5.16 and later · before 6.1.120
- linux linux kernel6.2 and later · before 6.6.64
- linux linux kernel6.7 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
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.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-56676Dec 28, 2024 · thermal: testing: Initialize some variables annoteded with _free()22Monitor
- ← EarlierCVE-2024-56677Dec 28, 2024 · powerpc/fadump: Move fadump_cma_init to setup_arch() after initmem_init()22Monitor
- Later →CVE-2024-56680Dec 28, 2024 · media: intel/ipu6: do not handle interrupts when device is disabled22Monitor
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 | 06dbbb4d5f7126b6307ab807cbf04ecfc459b933 | Vendor (CNA) |
| Linux Linux | 15f78d2c3d1452645bd8b9da909b0ca266f83c43 | Vendor (CNA) |
| Linux Linux | 4d2655754e94741b159aa807b72ea85518a65fd5 | Vendor (CNA) |
| Linux Linux | 7eaeb7a49b6d16640f9f3c9074c05175d74c710b | Vendor (CNA) |
| Linux Linux | 9ea8d8bf9b625e8ad3be6b0432aecdc549914121 | Vendor (CNA) |
| Linux Linux | e0a470b5733c1fe068d5c58b0bb91ad539604bc6 | Vendor (CNA) |
| debian:linux | 6.1.123-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/15f78d2c3d1452645bd8b9da909b0ca266f83c43
- git.kernel.org/stable/c/4d2655754e94741b159aa807b72ea85518a65fd5
- git.kernel.org/stable/c/7eaeb7a49b6d16640f9f3c9074c05175d74c710b
- git.kernel.org/stable/c/9ea8d8bf9b625e8ad3be6b0432aecdc549914121
- git.kernel.org/stable/c/e0a470b5733c1fe068d5c58b0bb91ad539604bc6
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.