Availability loss via leaked coherent DMA memory
Published Dec 29, 2024 · Updated May 11, 2026
Memory leak in the sh7760fb driver in Linux 2.6.27 and later allows local users to reduce availability through failed DMA cleanup. When screen_base or related framebuffer state is not ready, sh7760fb_free_mem() skips the coherent DMA allocation instead of releasing it. Exploitation requires local access and an SH7760 or SH7763 system using this hardware-specific LCDC driver; repeated failures consume DMA memory and can interrupt service.
Summary
What happened
Memory leak in the sh7760fb driver in Linux 2.6.27 and later allows local users to reduce availability through failed DMA cleanup. When screen_base or related framebuffer state is not ready, sh7760fb_free_mem() skips the coherent DMA allocation instead of releasing it. Exploitation requires local access and an SH7760 or SH7763 system using this hardware-specific LCDC driver; repeated failures consume DMA memory and can interrupt service.
The record
- CVE
- CVE-2024-56746
- Published
- Dec 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 29, 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=2.6.27
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <0d3fb3b3e9d66f7b6346e3b90bc0ff48683539ce
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <29216bb390e36daeebef66abaa02d9751330252b
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <3dd9df8e5f34c6fc4217a7498c1fb3c352d4afc2
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <40f4326ed05a3b3537556ff2a844958b9e779a98
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <bad37309c8b8bf1cfc893750df0951a804009ca0
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <d10cd53e5a7fb3b7c6f83d4d9a5ea1d97a3ed9a5
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <d48cbfa90dce506030151915fa3346d67f964af4
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <f4fbd70e15fafe36a7583954ce189aaf5536aeec
- Affected versionversion=4a25e41831ee851c1365d8b41decc22493b18e6d <f89d17ae2ac42931be2a0153fecbf8533280c927
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